My votes
Sort by:
Trending
Filter by:
Status
Showing 9125 of 9125
3
VOTE
allow epics and features to be independently defined, then attached to a release
currently, you must define a release first, and though you could use placeholders releases, you can’t create epic’s without having them be in a release……seems unnecessarily restrictive, why can’t Epics be created independently of release, then ass...
0
Future consideration
4
VOTE
Sort list reports by fields not visible
It would be helpful to be able to sort by columns that are not necessarily included as a column in the list report. This functionality is available in other report types as noted in https://blog.aha.io/better-product-management-analytics/
0
Unlikely to implement
4
VOTE
Allow multiple primary record types (i.e. Features & Master Features) in list reports
I want to show a list of all features and some of those features have master features. It is redundant (especially for those with share the report with) for the children features to seemingly appear multiple times. This would be most useful for fe...
4
Unlikely to implement
6
VOTE
Feature Board - Scroll Individual Columns
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...
0
Unlikely to implement
6
VOTE
Need a permissions ability between Reviewer and Contributor for features description editing
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...
1
Unlikely to implement
2
VOTE
Custom fields should support read-only for public portal with edit for internal portal
We have an idea review process for one of our Ideas portals that uses several custom fields. Two of these fields are used for the outcome (go/no-go and reason for decision). These fields can only be updated in the internal portal by users with pai...
0
Future consideration
2
VOTE
6
VOTE
Add the Status label to Release Roadmap on Features included in the Roadmap
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 ...
1
Will not implement
5
VOTE
Provide a way for users to set A4 as the default report size (rather than letter)
The current report page size default in Aha is letter. Although the page size can be changed manually, this is an extra and unnecessary step each time a printable report is generated and is already becoming tiresome.
1
Future consideration
3
VOTE
Simplify the process of finding and fixing duplicate organizations
Today, it's quite onerous to find and fix duplicate organizations. We'd like Aha to help identify potential duplicates (either the names are similar enough, or they have the same email domains). Once identified, we'd like bulk merge capabilities (...
1
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved