Features
Sort by:
Trending
Filter by:
Status
Showing 1178 of 9718
3
VOTE
Checkbox to select all should only select the current page
I had a filter with 200 items, 50 per page, and selecting the "all" checkbox selected all 200, not just the 50 on the current page. This goes against web UI from the other most common webforms, such as Microsoft, google, (hotmail and gmail), Jira,...
2
Will not implement
2
VOTE
When creating a new Feature in Aha! and pushing the data to Jira: Aha! should have a way to handle sending data to Jira fields which are: a) required b) Autocomplete Renderer so the Epic can be created and not rejected by Jira
I created a new feature in Aha! When I attempted to send the changes from Aha! to Jira, expecting a new Epic to be created in Jira, I got the following error: The following required fields could not be set on the epic: Fix Version/s. Please check ...
8
Already exists
2
VOTE
Security per Feature or per Release
To enable consultants and freelancers to also provide estimates and work using Aha!, please implement more fine-grained security features to add user and choose from a list of features they are allowed to see and contribute. This is critical to en...
3
Unlikely to implement
3
VOTE
1
VOTE
Support embedding notes inside epic and feature descriptions
While we can reference a note as a link in an epic or feature, we cannot directly embed a note as a live object. This functionality would help us use notes in a more collaborative way and to drive key feature definitions via those notes, rather th...
0
Future consideration
1
VOTE
Multiple fields as import Key
When importing data to the Aha system, there are other id's that we use as keys such as Wave ID's etc. The goal is to be able to use other fields as ID keys so the system can identify the same key in the import data and update the system according...
0
Future consideration
1
VOTE
Features Board - allow columns to be wider
When I'm looking at 1 or 2 releases, and 1 or 2 parking lots on the Features Board page - there's still a lot of white/unused space in the middle. At the same time, some of the feature names are wrapping, which means I can't see as many cards on t...
0
Future consideration
2
VOTE
Improve "Move requirement to another feature" dialog to help quicker find the required feature
Currently, if I need to move a requirement from one feature to another, I need to remember my destination feature name, and even then there could be several with the same names. Would be good to see and be able to search by more context, for examp...
0
Will not implement
2
VOTE
Seat assignment permission should be separated from billing
Assigning and un-assigning seats is weekly task as we have product and dev members joining and leaving.
Upgrade subscription is quarterly or longer term task as it depends on budget. In my opinion the first task should not require billing permissi...
0
Already exists
2
VOTE
Behavior of bulk edit product permission "to none" is not consistent with "from none"
When bulk edit product permission to viewer or product owner for example, product line permission of "none user" will change to the new value accordingly while other users will keep their their individually assigned permissions. This is ...
0
Unlikely to implement
© 2025 Aha! Labs Inc.•All rights reserved