All ideas
Sort by:
Trending
Status:
Future consideration
Showing 5832
32
VOTE
Automation rule that adds a new row to a custom table
In my use case we have a custom table on releases to track changes to the release date. I would like to set up an automation rule so that "when the release is updated and the date field changes to anything" then "add a row to the custom table with...
2
Future consideration
2
VOTE
Ability to easily update Personal Access Tokens in Integrations
What is the challenge?
We have approx 110 workspaces. Previously, I was able to renew the personal access token so that I didn't have to create a new one and update all 110 workspaces. There has been a change and now I must create a new one ever...
0
Future consideration
38
VOTE
Estimate in allocation percentage
I want the ability to estimate in allocation percentages. For example: I'm planning 2H 2020 feature planning I want to say that 50% of Sally's time is dedicated to a specific initiative. I want to create that initiative, give it a date range of 2H...
2
Future consideration
51
VOTE
Make admin access multi-level by organization/product line
We have multiple organizations/Business Units/Groups with their own product line in the hierarchy. We would like to be able to make them admin of just that area so that they can make the customizations they need without negatively impacting produc...
7
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
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
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
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
© 2025 Aha! Labs Inc.•All rights reserved