All ideas
Sort by:
Trending
Status:
Showing 9214
1
VOTE
91
VOTE
Don't remove lane in feature board view once shipped
Currently when you ship a release the lane disappears from the feature board view. It would be great if instead of disappearing all together the lane was simply greyed out or marked as shipped. The feature board view is where we look to see what w...
27
Unlikely to implement
21
VOTE
Priority limit line on subsequent pages of Prioritization view
Love the new prioritization lines introduced last week. However, they can only be placed on the first page. We have a need to also place them on the subsequent pages, as we have that many features to keep track of. We're hoping to use these to als...
3
Future consideration
8
VOTE
Add option for line jumps to whiteboards
Many shapes I use within whiteboards have connector lines. Many of those diagrams have lines that cross-over. It would be helpful to have line jumps so that there isn't confusion about where the lines are intended to go. For example, process diagr...
0
Future consideration
13
VOTE
Provide additional formatting controls to the Now, Next, Later Roadmap view, similar to Pivot Chart functionality
Who would benefit? Any user who is using the Now, Next, Later roadmap, or those who are creating their own version with a Pivot table. What impact would it make? It would allow users to more fully customize Now, Next, Later roadmap view to tailor ...
3
Future consideration
5
VOTE
Display release progress bar on epic/features board
What is the challenge? When working on the epics/feature board, I need to see the release progress for each without needing to click on the release name to see the progress. We have multiple releases that are in progress at any given time and this...
0
Future consideration
6
VOTE
Add ability to set selected users for Slack notifications from Aha!
What is the challenge? Currently, the newest Aha! Slack integration does not allow you to set specific users to trigger a notification to Slack from Aha! in the way the previous version supported. What is the impact? You cannot filter down activit...
5
Future consideration
57
VOTE
Jira Integration of custom calculated field
We have a Jira project that supports multiple engineering teams. Each team has their own release schedule. We need a way populate fixversions in jira with team specific values. The creation of a custom field that combines "product prefix-release n...
3
Future consideration
2
VOTE
The "Show In Portal" Column On The "Statuses And Workflows" Screen Should Allow A User To Set ANY Status Value To "Hidden By Default" Just Like You Do For "Shipped"
What is the challenge? Ideas that are in certain statuses, such as "Will Not Do", unnecessarily clutter the portal, are not useful to most portal users most of the time and make it difficult for users to find the ideas they are looking for. What i...
0
Future consideration
4
VOTE
Child records eligible to import to multiple workspaces are automatically importing to the workspace where the parent record is integrated to
What is the challenge? If I am using an integration template to manage multiple Jira projects which can have parent/child records spanning multiple Aha! Workspaces (many to many relationship), If I add a child record from one Jira project to an in...
0
Likely to implement
© 2025 Aha! Labs Inc.•All rights reserved