I'm posting a lot of idea requests about Organizations, and there's no obvious category for them. ;)

Currently the custom fields that are relationships to other Aha! records (e.g., workspace field) allow users to choose one or more workspaces. In many of our use cases, we need to limit the choice to one and only one record. In such situations, gi...

The default view for Goals and Initiatives is the quadrant / scoring view; it would be nice to be able to default (at either the Account or User level) to the Detail view which is far more useful.

We use the Saved Views for the Feature List as a prioritized Single List of Work for different team members. However, when we update the order of Features, the list doesn't auto-update for them. They have to refresh the page. This can be problem...

Who would benefit? product managers What impact would it make? make the my work section more clean for ideas How should it work? the ideas are promoted to backlog they should not appear in the idea section anymore.

Who would benefit? Teams using non-product workspaces What impact would it make? Avoid confusion due to different terms used How should it work? The navigation item for release should match the default terminology if the terminology wasn't customi...

With a digital first mindset on the rise and more tools like Slack being used for asynchronous communications and collaboration, the ability to create workflows from within Slack to be able to submit an Idea or create an epic or feature would impr...

Using the strategic roadmap, we would like to be able to expand each initiative to view its child features, while viewing only the releases assigned to this specific workspace. As it stands, this roadmap view shows us every linked release across e...

When reports initially display, the columns auto expand to the widest - at times, this can exceed even the onscreen browser width. By default, have a set width to avoid this issue. Also, allow the column headers to wrap where the column headers li...

Who would benefit? users of approvals in workflows What impact would it make? add flexibility to select approvers by feature instead of generalizing and expecting that all features in a workspace have the same approver(s) How should it work? A use...