To Do comments are buried....we would like our users to place all comments on the main feature card to eliminate confusion.

Why I want to see this for Not started records: I want to see how long something has been sitting in the prioritized backlog without any movement If something was assigned to someone but is sitting in not started, I want to see how long it's been ...

As a user, when creating a new Aha Initiative or Feature, I would like the ability to choose whether the Aha Initiative/Feature/Requirement should be mapped as a JIRA Epic, User Story, or Requirement, so that I can have more flexibility when creat...

I find this calculation the most accurate one and I want to place it in the highest hierarchy (company parent line) so that it can be inherited to all the workspaces in my account. Today, this option is available only in workspace level. Which mea...

Add Description fields as a filter option in reports. MVP options "is blank" "Is not blank" so we can find object records where the description is not filled in.

This idea encompasses a big picture echoed in a number of idea requests. The To-Do' feature in Aha! really seems to be an afterthought compared to the other record types in Aha! such as Goals, Initiatives, Features etc. Specifically To-Do's don...

What is the challenge? I spent a lot of time carefully ranking my features, which works well. Then i have to go and build a roadmap and add all the filters to get it to show the data. What is the impact? It slows me down and I have to repeat steps...

Today, the ProductRole attribute can be included in SSO configuration (for some identity providers) in conjunction with the ProductPrefix attribute when provisioning users. It would be useful for Enterprise+ users to also have another attribute fo...

After a certain period of time, it is no longer helpful to see a release that has been shipped. It should be possible to "archive" a release so that it no longer is visible in dropdowns, the release list, or the feature board.

We create features and their requirements before assigning to a team to execute the work. We would like automation to auto-assign any existing requirements to the same team if a team is set at the feature level.