I want to suggest for Aha to allow a way for people to create distribution groups that can be used when creating To-Dos Example, opposed to me adding a person name one by one, can I create a group to include all of those names?

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...

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...

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...

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...

It would be good to be able to change the colours assigned to a status. As far as I can tell these are system defined but I would like to able to define my own to make the cards for a feature a different colour in story maps and other views.

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...

User flow: Ideas, search, then export that list as .csv (would be ideal to do this without saving a view)

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"....

When building out initiatives, master features and features created are defaulting to the nearest term planned release. Even if this release is not linked to that initiative. This is causing master features and features to be inadvertently assigne...