All ideas
Sort by:
Trending
Status:
Showing 8940
13
VOTE
Show more context for added/removed records in retrospective report
I want to understand more about the records that are added to or removed from a release: When was it removed? Where was it moved to? What is its current status? I would like to see this information in the retrospective report
1
Future consideration
12
VOTE
Dependency roadmap as a standard view
Who would benefit? Users that: need to track upstream work they are dependent on need to understand downstream work that is dependent on their work need to easily identify delivery risks based on dependencies What impact would it make? A roadmap i...
0
Future consideration
7
VOTE
Multi-language support in KBs
What is the challenge? Non-English speaking users need to access content in a KB. Currently a separate KB must be generated in each applicable language. How would you solve it? Provide KB translation. What impact would it make? Allow non-English s...
3
Future consideration
8
VOTE
Ability to Configure Epic View as Default for all workspace views (Board / Prioritization)
Who would benefit? Enterprises who maintain Epic only or use Epic as primary record type. What impact would it make? Reduce confusion. The teams are currently directed to feature view on the board and prioritization view by default. Per Aha concie...
0
Future consideration
1
VOTE
Add a "Create Roadmap" button to the features priorisation page
What is the challenge? I spent a lot of time carefully ranking my features, which works well. Then i have to go and build a roadmap and add all the filters to get it to show the data. What is the impact? It slows me down and I have to repeat steps...
0
Future consideration
2
VOTE
Portal Report extracts are not possible
What is the challenge? A portal user can use a published report on the portal to analyse ideas. This is a visual report only and users may want to process the data or distribute the data to managers that are not portal users What is the impact? Tw...
1
Unlikely to implement
2
VOTE
Assign Work Requests by Product Areas
What is the challenge? Currently, Work Requests can only be assigned to workspaces with permission admins, rather than specific product areas. This limitation creates a few notable concerns: Bottlenecks in the approval process Increased workload f...
0
Future consideration
2
VOTE
Show pivot table column even if nothing in there
What is the challenge? Want to use pivot table view as a progress tracker (similar to Kanban) What is the impact? More teams and more collaborative ritual can be done inside Aha Describe your idea We have a custom field marking 5 stages of UX desi...
2
Future consideration
10
VOTE
Allow Release Date (internal) and Release End date (date range) to sync
Who would benefit? The Release date (internal) drives many of the OOTB reporting functionality in Aha! so it must be maintained and accurate for reporting to be accurate. For many teams, the end date of the release and the Release date (internal) ...
1
Future consideration
8
VOTE
Better Email Update Notifications
Who would benefit? All users who are subscribed or watching features in Aha! and utilize email notifications What impact would it make? More informative notifications directly in the email without extra clicks or searching in the history of the fe...
0
Future consideration