Other great Kanban-style boards (e.g., Trello, GitHub Projects) allow scrolling the individual columns which makes moving an item from one long list to a specific position in another long list much easier. I'd like to see this on the Feature board...

Problem Statement: The current permissions/licensing structure of Aha is cost prohibitive for companies with larger business review teams who need update feature descriptions prior to development (i.e. moving features through stage-gate prior to a...

Allow account holders to customize the Aha! application main navigation color scheme (active and hover state background colors) to match corporate branding. Currently they are stuck as the default Aha! blues - which look great if you don't change ...

We often collaborate with multiple stakeholders at our customer when building requirements for ideas. Currently, private comments are only visible to the creator of the idea and internal users. Other users at the same customer Organization lose vi...

Currently most reports can be scheduled. However, there is no way to schedule the user activity report at this time. We need to be able to schedule activity reports so we can better utilize our licenses and assign to users who need access.

Challenge When adding features in a story map, you usually add them top-to-bottom. if you later visit the feature board, the features will be in the opposite order -- the most recently added at the top, instead of the bottom. This feels very confu...

It would be useful because there isn't a legend that shows the color coded status states and for some it is easier to see the written status as opposed to knowing which status is which color. Gives the ability for me to see what status my tickets ...

Currently when you convert a record (ex. Feature to Master Feature), all record links are severed. It makes sense to sever the link to parent/child records, but links like "relates to" and "depends on" would still be relevant even if the record is...

In addition to the "re-rank features by" status within the individual releases, there should be the ability to set a DEFAULT ranking of features within a release for all releases, for example, by status, so that all new releases added would have t...

Aha allows for the creation of Custom Fields as "record relationships" with many objects, but doesn't include relationship to Teams. As we start using Demand/Capacity, creating relationships with Teams would be very valuable to allow for flexibili...