ADD A NEW IDEA

All ideas

Showing 8737 of 8737

Allow User Story Maps to Span more than one product

User Story maps should be able to show Master Features and Features from multiple products. We have complex products that have to work together in order to deliver usable solutions. Any step that the user does (install, configure, receive certain ...
Julia Doyle almost 5 years ago in User story map 11 Future consideration

Add Key Results to Hierarchy Report

Who would benefit? Teams using OKRs that choose to associate work with Key Results rather than the Objectives What impact would it make? More logical display of strategy through the new OKR records in the Hierarchy report How should it work? Abili...
Justin Woods 4 months ago in Reports 0 Future consideration

Don't notify me when others complete a to-do I was assigned

When I am assigned a to-do along with many other people at my company, I do not want to receive notifications every time another person a my company completes the same to-do. Perhaps the owner of the to-do can get these, but not the assignees. It ...
Tracy Singleton over 4 years ago in Comments / Notifications 1 Future consideration
161 VOTE

Add "Save View" feature to the "Features Board" page

The filters on the Feature Board are critical. I want to be able to Save Views that capture the various filters that have been applied
Guest over 9 years ago in Features 23 Future consideration

Integrate with Miro

Hi, would you consider integration with Miro, formerly RealTime Board? This is a great diagraming app, and has a good Jira integration which I was going to use in a convoluted way by pushing from Jira to Aha to get visibility back in Aha. In reali...
Guest almost 5 years ago in User story map / Wanted 10 Future consideration

Auto refresh features board after updates

What is the challenge? anti pattern to a quick workflow What is the impact? things take a lot longer and you second guess yourself Describe your idea automatically refresh boards after I update an item
Guest about 1 month ago in Features 0 Future consideration

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...
Hank Liu 4 months ago in Epic 0 Future consideration

Customize the "Key results" table on the Related tab

Who would benefit? Everyone tracking OKRs in Aha! Roadmaps What impact would it make? Allow me to customize the key result data displayed on my records How should it work? Ability to customize the "Key results" table on the Related tab
Nathaniel Collum 4 months ago in Strategy 1 Future consideration

Automatically Update Records Converted in Jira

What is the challenge? Often times our Engineering counters in will convert stories/Spikes/Tasks to Epics in Jira What is the impact? We're not always told when these conversions happen and often have to do duplicate work to go into Aha! and conve...
Guest 22 days ago in Jira 0 Future consideration

Report owner being able to generate webpage view regardless of which workspace it is saved

What is the challenge? A template created by ProductOps is intended to be duplicated by PMs to use and modify, but for some reason if the duplicated report was accidentally saved in a different workspace (without anyone knowing and no visibility/a...
Puppy Tsai 22 days ago in Reports 0 Future consideration