All ideas
Sort by:
Trending
Status:
Future consideration
Showing 5849
5
VOTE
Remove irrelevant goals and initiatives when adding them to epics or features
What is the challenge? When adding an initiative or a goal to an epic or feature I'm presented with a list which includes items from other workspaces and/or items which are already achieved What is the impact? This makes it harder to find a releva...
3
Future consideration
5
VOTE
4
VOTE
Display customized terminology on settings screens
What is the challenge? Today customized terminology displays on user facing screens within Aha! but not on settings screens. What is the impact? This makes it hard for users to ensure they are adjusting the right settings for each record type. Des...
0
Future consideration
11
VOTE
Epic progress doesn't update when it has children in different projects
Who would benefit? Customer using Jira epics to manage work in multiple projects What impact would it make? They would be able to see their progress in Aha! correctly How should it work? If you have an epic in Project A, and it has multiple childr...
2
Future consideration
1
VOTE
View Only Permission between Roadmaps and Develop
What is the challenge?
Currently, it’s not possible to allow users to assign work to a team while preventing them from updating the team’s status.
What is the impact?
This inadvertently allows someone from another workspace to modify the s...
0
Future consideration
9
VOTE
Allow @mention in Note field
What is the challenge? We use the 'Note' field throughout our record types, including Goals, Initiatives, Features, Requirements, etc. While we can use To-Dos, it would be easier for many of our use cases to @mention someone directly in the field ...
2
Future consideration
9
VOTE
Promoting an idea should copy the creator's information to the feature
What is the challenge? Currently, the "Created By" field on the idea card in Aha! displays only the name of the user who submitted the idea. However, this information is lost when the idea is promoted to a feature/epic, making it difficult to trac...
1
Future consideration
17
VOTE
Allow to define the scope of tags/choice list custom field values (account vs. workspace)
It should be possible to define whether the values of choice list and tags custom fields (predefined or editable) are shared at account level (current behavior) or limited to workspace level such that workspaces can share a configuration but have ...
2
Future consideration
30
VOTE
Sync status updates between Features and their associated Releases
Currently when any feature changed their status from Backlog to In Progress, the associated Release should be manually updated to reflect the changes. There is a functionality to sync status updates between epics and their associated features, and...
2
Future consideration
10
VOTE
Display capacity line on Releases when looking at Epics board view
What is the challenge? When viewing the Epics on a board view, a capacity line does not appear even when "Epics" or "Features and epics" are used for the calculation. What is the impact? When estimation is done at the epic level, and epics are use...
0
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved