Add the possibility to link individual steps of a User Map. The individual steps can be referenced from various parts of the platform, e.g. Description field of Releases, Strategic Models, etc.

Currently the "Create related idea" functionality is allowed for Epics and Features, but not Initiatives. However, Ideas can be promoted to Initiatives, Epics or Features. It is not clear why the relationship between Initiatives and Ideas is allow...

When running through the trial of Aha! It's common for customers to add trial data and configurations to evaluate the tool. Upon transitioning to the paid account we had to manually delete everything and had no option to start with a fresh clean a...

Requirements can be imported as part of the feature import from CSV routine. The requirement comment field is not included in the possible fields. Aha! users need to be able to keep track of the comments that are being imported and so at the momen...

Surface the timestamp for all To-Do and Approval tasks so you can: View the date and time within the approval task without having to scroll through the history. Include the date and time when displaying the information within a report. Have the ab...

It's a huge waste of time—not to mention a major source of errors, omissions, and frustration—to have to manually click every single thing I want to be part of a roadmap, table, report, etc. "Select all" and "Selection section" options, and their ...

In User Stories --> Details view Order by Status does not sort in the correct order for example, the status is ordered by : Development Design QA Analysis Shipped When Sorted. User Stories --> List does sort by the correct order on St...

This artifically inflates the number of ideas we need to work through, and does not give us an accurate picture of the number of suggestions we have.

When creating integrations to Jira (master features and features to Epics and stories, within in several Jira board in the same instance) the first created epic in Jira should be the only epic created. Not one per integration/Board. At it is set u...

The ability to trigger automations based on who (or who is not) updating an item would be useful. For example, sending email on Idea update only if not updated by specific users (such as those in the team processing ideas)