Aha wants to replicate the concept of epics as master features and features as stories. However, they treat them as separate entities which makes really hard to report a list of ‘features’ together (including master feature). For instance, JIRA ca...

We use tags on Features and Requirements for grouping items across product lines and between 2 products that connect but are separate applications. We currently use a non-Aha product as a digital whiteboard that allows tags which means double-work...

When clicking on the "Ship it" button for a release, the Ship Release modal appears with the list of unfinished features and provides you with the opportunity to specify which future release you wish to move them to. However, if you click on the R...

What is the challenge? Identify the item in the list that is been presented in the side panel. What is the impact? Easier to find the select item in the list and to check the next one after going to another tab. Describe your idea

What is the challenge? Having many presentations, it would be useful to have the possibility to arrange them into folders, similarly to what is possible with reports What is the impact? In the presentations view, folders can be created and present...

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.

We produce a number of reports to key stakeholders which has information entirley pulled and automated from Aha. This is great for a number of reasons, but largley because it re-enforces the value that Aha is bringing us. Another upside is that th...

It would be great if we could see the description of the idea when posting it through slack (or Workplace). Additionally, if we could vote through the thumbnail/preview, that would be awesome (not sure if this is possible though). Thanks!

Who would benefit? Admins of accounts with ADO integrations What impact would it make? When an ADO integration is created, a user with the correct permissions must enter their token to authenticate the integration. However, the token owner's name ...

Currently when an Aha! Roadmaps record is assigned to a Develop team that gives anyone with contributor permissions in the Develop team access to edit any field on the record (even those in the Roadmaps layout). I'd like a way to control this more...