All ideas
Sort by:
Trending
Status:
Showing 9123
20
VOTE
Ability to prevent promotion of ideas to a specific record type
Currently, when promoting an idea, you can promote it to an Initiative, Master Feature and Feature.
It would be useful if you could restrict this for some Ideas Portals. For example, if you managed all large initiatives via one portal, you would ...
6
Future consideration
4
VOTE
Limit "Capacity planning for teams" field on board to only teams with a value entered in the estimate
Who would benefit? Users creating advanced estimates and visualizing their teams on Feature/Epic cards when using default teams. What impact would it make? This would make it easier to quickly note which records are expected to be worked on by whi...
0
Future consideration
18
VOTE
Set the release start date and have the release phases adjust to that date.
Currently when we set the Release Start date it does not adjust the dates for the Release phases in the Release template used. It will be helpful, if we set the Release start date then the Releases phases dates are adjusted based on the Start date.
0
Future consideration
11
VOTE
Allow nesting of rollup releases
Rollup releases are very useful in organizations with complex and nested product lines and products. A top level product may have a V2.0 which is a rollup of three subsystems, a perfect use case of a rollup release. If each of the subsystems, in t...
3
Future consideration
30
VOTE
Improve Gitlab Integration
Every time an issue is updated in Aha, the user must remember to click on Actions and send the update to Gitlab. This manual step is different than making all other edits in Aha that automatically save and makes it easy for things to become unsync...
5
Future consideration
1
VOTE
Simplify the process of adding an existing record to the prioritization view
What is the challenge? The prioritization view is a great tool for scoring and ranking important work. Adding new records to this view is straightforward with a single button but adding already existing record is not easy. You need to filter or se...
0
Future consideration
1
VOTE
Create record from notification
What is the challenge? Users may need to take action based on notifications, but manually creating related records can be time-consuming What is the impact? Saves time by streamlining record creation directly from notifications Describe your idea ...
0
Future consideration
1
VOTE
Ability to sync Jira's "Team" bidirectionally
What is the challenge? Out-of-the-box Jira field values cannot be synced, causing the inability to bidirectionally sync that field between Aha and Jira. What is the impact? Aha is meant to be the singular solution for Product teams to set their st...
0
Planning to implement
1
VOTE
1
VOTE
Issue Count Limit for Unranked Epics (Prioritization View)
What is the challenge? We frequently run into issues with the epic prioritization view. On a workspace line level, we have more than 100 unranked epics across 3-4 workspaces. Whenever we run into this issue, the view does not even show the workspa...
0
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved