Application

What is the challenge? Today, when searching on the features > board view Aha! only applies search to what is on the screen. When parking lots are being used and they have not all loaded yet they are not included in the original search results....

What is the challenge? paid_seat field is not properly returned for the new "Knowledge" license What is the impact? We cannot rely on API data alone and need to find workarounds in this case to properly reflect the users license information Descri...

What is the challenge? There are occasional persistent bugs with whiteboards: text boxes cannot be deleted or resized. The bugs do not necessarily disappear after refreshing the page. What is the impact? Continuous troubleshooting. Describe your i...

What is the challenge? Roadmaps do not present well in Presentation mode, (see attachment What is the impact? Maintaining a PowerPoint and Aha! version of the Product Roadmap risks lack of synchronisation and is time consuming Describe your idea A...

Who would benefit? Enterprises who maintain Epic only or use Epic as primary record type. What impact would it make? Reduce confusion. The teams are currently directed to feature view on the board and prioritization view by default. Per Aha concie...

When an Idea is submitted an admin can choose if the idea is visible in the portal it was created and/or other portals within the workspace.

Instead of listing features within the same epic in alphabetical order, it would be helpful to be able to rank features within epics, not only releases.

In Aha! Develop, having the possibility to log time entries approval would be great. Doing so, it could have a whole dimension of cost tracking as well and budgeting. Combined with time planning capacity per employee would top it all.

Hi there! love Aha! its an awesome tool, however we are having problems with timetracking, would it be possible to have something like Tempo in Jira? thanks and hope this makes it through!

I have certain fields that need to be filled in before moving to the next status in my workflow. The data for these fields is not known in the previous statuses, so it can't be set as a required field before the record reaches a certain status. Th...