What is the challenge? Automations are awesome. Being able to have a series of to-dos that pre-populate help ensure consistency. BUT. To-dos created by Aha! automations are a bit of a black hole. No one is notified when the assignee completes OR a...

What is the challenge? Some users are creating ideas directly within Aha! Roadmaps when we expect those ideas to be created on our Aha! Ideas Portal. What is the impact? By allowing users to create ideas within Aha! Roadmaps, they circumvent the C...

What is the challenge? We use data based on team status changes (timestamps) in Aha Develop for some custom calculations, e.g. in custom List reports. This works very nicely for features which exist only in an Aha Develop Team. However, features w...

What is the challenge? When trying to reproduce the reports shown in Aha's online support documentation I sometimes struggle with how to configure the data fields. This is a particular challenge with pivot tables, but happens with all reports. How...

The default behaviour of how the TFS/VSTS integration sends time Estimates in minutes is very limiting. I don't know any agile team that would be estimating Features or Requirements down to minutes, so it doesn't make sense for the integration to ...

Currently, when a feature or epic is created in Jira and pulled over to Aha! via the integration webhook, the created by user defaults to the Aha! user who is the webhook "run as" user. Even if there is mapping setup to map the Jira "Reporter" to ...

I should be able to assign a workflow for the phases and milestones for a given release. I should be able to update the status for each of my phases or milestones so that I can visually see the progress of the release in the Releases > Roadmap.

Quick vier progress in features board.

Currently the "logged hours" component in Aha reports displays the hours logged against the parent feature or requirement mapped to JIRA. ie; If Aha requirements are mapped to JIRA stories, then Aha pulls in the hours logged against all mapped JI...

The hierarchy report is very useful, however it could be improved by making requirements data available also.