We have shipped releases where all the features were marked ready to ship and thought they were all shipped, only to discover later they were still in a "ready to ship" state, which adversely affected our reporting.

We have quite a few schedules and currently its a very painful process to update the schedules for each team member one by one.

The backlog page on the dev team site adds extra steps that are unneeded, it takes 3 steps to put it on the board. As a Kanban team we don't want to have to go through all these steps just to show something in a ready column. However if you turn o...

Improve the Overview page Add the description Overview table page so that I can remind myself what the view/report etc was about. I create a fair view of these and have to view each items info- clicks and and navigation that is time consuming The ...

As a Canadian organization it is difficult that the worksheet fields do not currently support Canadian currency. Having this implemented would be very beneficial for us.

We are using record links on pivot reports to show the dependencies on a roadmap. The default color setup while customizing a pivot report provides the option to select record links. It would be helpful if the default color can be set by record li...

I was trying to set up a new release template with phases to match our typical release management steps but ran into difficulty because the Aha! release phases are set up mainly to occur sequentially / in-series, but our list of items for a releas...

Enables better collaboration

As a user of Jira, we update the Fix Version of Epics. This does not reflect in Aha! in the Release unless we also add some data in another field such as description. This is very frustrating for users of Jira and Aha! as they should be able to up...

If a feature is going to be worked on during mulitple sprints or releases it would be nice to have it appear in both releases so we can track overall effort, and have it appear on roadmaps spanning releases.