All ideas
Sort by:
Trending
Status:
Showing 8770
1
VOTE
Notify Roadmap Stakeholders if an upcoming release is over/underplanned
What is the challenge? In our company, many stakeholders steer the contents of our product roadmap. It would be great if those stakeholders could be automatically informed if an upcoming release is over/underplanned. What is the impact? Better pla...
1
Already exists
1
VOTE
Support extension fields in Aha! Roadmaps
What is the challenge? Currently, as a product person I spent most of my time in Roadmaps. There, we also review the releases together with engineers. However, I can't see things like GitHub PRs and Figma designs because those are extension fields...
0
Future consideration
4
VOTE
Update Now, Then, Later Roadmap to Remove Old Features
What is the challenge? Now, Then, Later Roadmap doesn't auto-hide "old" features, capabilities, etc. that are no longer relevant. It only allows you to enable a "rolling" X days from now or older. While you can subsequently add a "feature due date...
0
Future consideration
7
VOTE
Edit the documents in a KB outside of the existing parent line
What is the challenge? Currently when you create a knowledge base , you select the root document to publish. Any child notes nested underneath it are included as well. There is a need to edit the documents in a KB in a broader way. How would you s...
0
Likely to implement
188
VOTE
6
VOTE
ability to reference other fields within Aha record when using Draft with Ai
What is the challenge? When using draft with AI and basing the prompt on data that is already within Aha, it is necessary to have multiple windows or documents open in order to provide the prompt with the key points. What is the impact? The abilit...
2
Future consideration
5
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
16
VOTE
Improve handling in retrospective report when a completed record is added to a release
Sometimes work is completed outside of a planned release. When I pull that completed work into an active release, the release retrospective report treats it as incomplete work. Ideally, the scope of the release would not change and the newly-added...
2
Future consideration
148
VOTE
Sync record's workspace, goal, initiative, epic, and release (name and link) to Jira
The use case is so that those working primarily in JIRA can understand “why” they are being asked to deliver “what” has been requested.
In the screenshot attached, it shows a section of the JIRA issue interface. It then shows a tab created specifi...
8
Future consideration
8
VOTE
Roadmap history: Show when delivery risk flags were raised or removed
Who would benefit? Product teams tracking delivery risks What impact would it make? Teams often need to understand not just what records are currently at risk, but when the risk was raised (and by whom, when relevant) and when the risk was mitigat...
0
Future consideration