When I'm viewing the progress of an active release via the retrospective report, I want to see any open dependencies for features in the release so I can proactively work to address them.

Would like the ability to see who has made changes and when to a dashboard. I have just returned returned to a dashboard and despite the permissions being set to View, changes have been made and I can't see who made the changes.

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

In the Aha knowledge portal there should be a list of everything a user who is granted "owner" permissions can do. Currently one has to navigate between several lists- such as the one for ideas and roadmaps. Automations, however, isn't a feature o...

When creating an idea, we have a custom multi-select field. I was able to tab to it and select as expected with 'space' however I was not able to tab out. When using keyboard it is expected that tabbing brings you to the next field instead of sele...

We use Features as user stories that get individually worked within a release (development iteration). However, almost all of our Features roll up to Epics (which then roll up to Initiatives). The current format doesn't allow for the organization ...

Reviewers and Viewers cannot export data from the reports pages, it would be nice if we could create a presentation for them and then share it with them. This would allow full users of Aha! to control what was published and when but give reviewers...

What is the challenge? We have to export each report on a dashboard separately, leaving us with multiple exports and a manual effort to condense them all into one workbook. What is the impact? Time consuming when dashboards have lots of reports De...

What is the challenge? When adding records to a prioritization view, sometimes I search for a record that has already been added to the list. What is the impact? I spend several minutes futzing with filters and looking at my record metadata to try...

It would be useful to be able to create filters to prevent certain records from being sent to Azure, JIRA, or other integrations. For many workflows, there may be "raw" working records in a release backlog that are not ready to go to engineering t...