I don't want to unship/ship releases to edit and align the phases with future releases if changed.

As a Product Manager, I would like be able to capture feature estimates without having the release capacity feature. I don't track capacity at the release level -- at least not in the way Aha! seems to work today. I manage my capacity across all p...

My Kanban is reasonably complex and I'd really like to get more of it in the available screen width, to do that I'd need to make the columns narrower.

Use Case: We have Enterprise Layouts / Workflows / Scorecards that we would like to lock so that only a 'Collaborator' or Full Account Admin could unlock before updating / deleting Examples: We have a Scorecard that is the default that we do not w...

For recurring status meeting reports, need the ability to provide some commentary on the latest status. These notes are updated regularly, but need to retain the history of previous status notes. A custom notes field that is regularly updated does...

Currently, if an account has SSO enabled and a new user logs in they will be auto provisioned in the account. This causes issues with Premium subscriptions as they cannot have unpaid users in the account. The result is that the new user is provisi...

Enables user to manage releases by moving Epics between releases on the Epics Board and automation automatically updates (and synchronizes) due date to the release's due date.

The Starter Roadmap is a fantastic tool for quickly inputting and organizing goals, initiatives, releases, features, and overall plans. Depending on how complex one's roadmap is, however, manually having to vertically organize and re-sort these it...

When creating and modifying Personas in Aha!, there is an ability to create/modify custom fields on the Persona via the "Manage fields" menu link. When I click on that link, I am navigated to the Custom fields screen within the Account settings. I...

We really like the feature details view in the app, with the tabs down the left hand side. I often wish I could just share that view with the client, because it still gives you the context that the feature you are looking at belongs to a bigger pi...