All ideas
Sort by:
Trending
Status:
Showing 8939
4
VOTE
When using Import Records, not retaining parent/child relationship (AzDo Integration)
Who would benefit? Aha users when setting up a new workspace What impact would it make? Improves ability to only bring in needed records How should it work? After setting up integration mappings with parent/child relationships, have import records...
1
Future consideration
4
VOTE
Whiteboard - Miro Card Functionality
Who would benefit? Users in planning phases, not yet ready to commit future work to a Feature/Epic yet. What impact would it make? More information and context to a whiteboard item to determine where it should be planned. How should it work? Curre...
2
Future consideration
23
VOTE
Support Decimals for "Total People" Field Used in Team Capacity Planning
As a user of the Team Capacity Planning feature set, I would like to enter decimal values in the Total People field for each Team, so that the true capacity for each team (e.g. 1.5 FTE) is precisely accounted in capacity assessments. Fractional te...
2
Future consideration
42
VOTE
Complete Auto Import Functionality -- not just children of existing linked records
This is regarding the JIRA integration feature:
Automatically Import New Records:
Records will be imported automatically to Aha! from Jira. This applies to records which are created as children of previously linked initiatives, releases, master...
5
Future consideration
20
VOTE
Ability to change roadmap font and styles at an individual cell level
A key use case for roadmaps is to share and present your plans with Executives, Clients, and other cross-functional teams. The automated generation of the roadmap is a great feature of Aha!, but if you cannot adjust the font for presentation purpo...
5
Future consideration
45
VOTE
Favorite/star/pin workspaces & lines
My org's hierarchy is huge; and to reduce the amount of administration all user have the ability to (at least) see everything. It would be great if I could "favorite" or "star" or "pin" products and lines from the hierarchy so that I can always ge...
6
Future consideration
15
VOTE
Allow removal of product value score column from prioritization view
Use case: there are times when I need to prioritize my list based on a custom scorecard that we've added as a custom field. It becomes hard to do this because I can't hide, remove or re-arrange the order of the product value score column.
3
Future consideration
9
VOTE
Move Ideas to top of Research Tab
When viewing the research tab, the first thing I want to see are the ideas related to my record. Ideas are the most likely research item I will have associated with my features and will often drive the creation of the assets I would add to the "co...
0
Future consideration
8
VOTE
Make priority limit line dynamic on prioritization views
I would like to specify the metrics that automatically set the priority limit line on the prioritization view. For example, if I know that my estimate limit for a list of records is 100d, I would like the priority line to dynamically set/adjust ba...
2
Future consideration
67
VOTE
Handle multiple FixVersions in JIRA
An Aha! feature can only be associated with a single release, however it is common for development teams to associate multiple fix versions with a issue in JIRA.
Currently, the Aha! feature will overwrite the fix versions in JIRA if the fix ver...
15
Future consideration