Need ability to track capacity (under / over allocations for time and pts) actuals for engineers, team, sprint, Releases, etc. This is based on the estimates for the requirement / feature within the sprint / release assigned to the engineer within...
Clark Milner
about 3 years ago
in Sprints
0
Future consideration
Enable Goal progress to update based on to-do's completed
The progress bar can be updated based on to-dos completed for releases and features ("Calculate based on to-dos completed"). I'd love this option to be available for goal progress as well. Use Case: A product management team is tracking milestones...
Meridith P
almost 4 years ago
in Strategy
1
Future consideration
For those of us who live in Aha!, a desktop app would be very helpful.
A simple Electron app (or like) would be great, just to get the window out of all the browser tabs.
Guest
over 6 years ago
in Application
3
Unlikely to implement
If someone adds a manual flag to an Epic, could they then have specific options to select from for the comment instead of typing it out? This would be in a drop-down format. This could help with tracking risks that aren't delivery risks, such as f...
Guest
over 1 year ago
in Epic
1
Future consideration
Ability to bulk color row content in pivot reports
Instead of having to color each individual cell in a row the same color in a pivot table, I would like to ability to give that entire row a color so that any features/user stories /entries within that row all have the same color. Right now each in...
Rachelle S
almost 2 years ago
in Reports
0
Future consideration
Do not count "will not implement" requirements in feature effort estimate
What is the challenge? If a requirement is listed as "will not implement" the detailed estimate is still counted in the feature effort calculation What is the impact? Currently need to manually adjust requirements to 0, in ADO if we mark the user ...
Guest
8 months ago
in Features
0
Future consideration
What is the challenge? We are tracking our PMs for adherence to ideas review but have run into issues being able to discern when they are reviewing items based on the available timestamps What is the impact? The inability to track changes does not...
Jerimiah Rudden
8 months ago
in API
0
Future consideration
I would like to be able to organize custom fields by moving them to other "tabs" on Feature tickets.
What is the challenge? I have too many custom fields on one page when opening a Feature What is the impact? It takes me too long to scroll through the Feature to find the field I need Describe your idea I need to be able to organize custom fields ...
Add "Requirement" option in work request drop-down
While creating dependency on another workspace, the aha record needs to be tagged at requirement level. It would be great to see that option considering the high usage of work request related to requirements.
Isha Khurana
almost 2 years ago
in To-dos
0
Future consideration
The first_name and last_name claims required by Aha! are not OIDC conformant, leading to duplicate information in previously conformant JWT tokens. This increases the size of tokens. This can also make it harder to use a common token for Aha! and ...
Guest
over 4 years ago
in User management
2
Unlikely to implement