All ideas
Sort by:
Trending
Status:
Future consideration
Showing 5652
1
VOTE
Allow TFS integration to map bidirectionally for fields that are not in a built-in System.State.
Currently, the TFS integration does not support mapping arbitrary string fields to the Aha! workflow status field in a bi-directional way. Only the built-in System.State field in TFS can be mapped bidirectionally.
2
Future consideration
1
VOTE
1
VOTE
1
VOTE
Allow scorecard at release level
Right now custom scorecards can be assigned only at the workspace lvl, which does not really allow for changing priorities and weightings. Worse, if we do change any fundamental portion of a scorecard, it will mass update everything in that worksp...
0
Future consideration
1
VOTE
Reporting on release phases/milestones comment field should only show the entered comment
When reporting release phase (or milestone) comment, the user who entered the comment and the date the comment was entered is included. Desire to see ONLY the comment in reports and NOT the "log" associated with the comment. Perhaps a second field...
0
Future consideration
1
VOTE
Watch changes in a workspace, but Releases OR Features only, not everything.
Currently I can watch at a workspace level, but it is overwhelming with the number of features being added. I would like to only be notified for changes happening on release timeline (phases and milestones). I don't really care about new or modifi...
1
Future consideration
1
VOTE
Progress Bar Update for Features to Match Releases
You are currently able to up date Releases to calculate Feature progress as 'Features' or 'Features Complete'. You should have this same option for Feature>Requirements. I understand that there is the option to calculate from Story Points but n...
3
Future consideration
1
VOTE
Automate the creation of a todo task when you add a new user to Aha!
Currently as suggested we are raising a todo task to maintain PII consent for every new user added in AHA ! Currently this is a manual process. If we are able to add a rule in the new automate functionality it would help a lot as number of user jo...
1
Future consideration
1
VOTE
Administrative knob to switch off or disable "Copy feature" capability
Generally "copying" things helps and reduce repetitive activities. However, "copying" feature entries without care and attention leaves too much room for errors or mis-representing information if not properly groomed, for example, removal or adjus...
0
Future consideration
1
VOTE
Update a master feature status to Will not do should ask to update child features
Overview: When moving a master feature/activity on the workflow board, it would be nice to have the associated children update as well. Challenge: Sometimes I want to move a master feature with multiple child features to a status of "Will not do"....
0
Future consideration
© 2024 Aha! Labs Inc.•All rights reserved