All ideas
Sort by:
Trending
Status:
Showing 9100
9
VOTE
Ability to adjust report element hierarchy
In pivot and/or list reports, I often have the original report correct but then need to adjust what is the master record and/or how the elements are related. I also have had this issue with custom roadmaps. Right now, I have to take snapshots of t...
0
Future consideration
8
VOTE
custom layout templates based on fields other than status
Would be great to be able to change the layouts based on the "type" field or a custom field setting. We have some fields that are only relevant based on a specific classification of work and it would be great to be able to provide a specific UI ba...
2
Future consideration
12
VOTE
Configure AHA! to support GSuite - sheets, slides, docs, etc.
We are a company that uses GSuite, this would allow us to pull data into our collaborative space and manipulate reports to personalize further than what AHA! current allows. Currently the inability to use AHA with GSuite causes delays and setbacks...
0
Future consideration
22
VOTE
Allow scorecards to be inherited from the product line
We have a lot of sub-products in our company, but we'd like to use the same general scorecard, linked to our general product goals, for all of them. It seems that currently scorecards need to be configured for each and every product, which isn't e...
1
Unlikely to implement
2
VOTE
Link all attachments in an idea to the promoted feature.
What is the challenge? Users have the ability to add attachments multiple places based on an idea layout. What is the impact? Because promoting to a feature doesn't pull all attachments, it either requires reviewing both the feature and the idea, ...
1
Already exists
12
VOTE
Efficient removal of scenarios from capacity planning for teams
After having completed planning with the use of various scenarios (with capacity planning for teams), I would have narrowed down my optimal scenario and would want to remove or archive scenarios that are no longer needed. Currently to delete a sce...
0
Future consideration
15
VOTE
JIRA integration needed at the portfolio and product family levels.
We use initiatives at all levels within Aha and need to be able to integrate those with JIRA for additional capacity reporting. If initiatives are available to be entered on those levels, it would be useful to have the integration setup available ...
2
Future consideration
7
VOTE
Fix field population in Aha/Jira integrations to only rely on email address or other specific data
Today when the Aha/Jira integration runs it looks up users in Jira based on email, then failing to find a match it checks first name, then last name. Jira returns results for these and Aha will select the first return. The problem is that if we ha...
1
Future consideration
24
VOTE
20
VOTE
to-dos in a release template should inherit the phase or milestone dates
The release template concept is great, but the ability to assign tasks to these things is what helps get the work actually done. You can put a to-do into the release template, but when a release is instantiated on that template, all the to-dos hav...
4
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved