All ideas
Sort by:
Trending
Status:
Showing 9172
25
VOTE
Add Burndown Chart for Initiatives
We're adopting a more flexible release strategy that is feature/initiative driven, not time boxed. It would be great to be able to generate a burndown chart for an initiative (even better: overlay several initiatives) so we can project/monitor our...
1
Future consideration
8
VOTE
Allow anyone who has access to view a report the ability to schedule delivery
Today, only the creator of a report can schedule a report for delivery. We want to avoid having multiple copies of every report out there and we’d like to see the functionality updated to allow anyone who has access to view a report the ability to...
0
Future consideration
7
VOTE
4
VOTE
Ability to Pull Estimates onto the Prioritization Report
Who would benefit? Any client, but especially those practicing SAFe What impact would it make? Make it very clear which features can be pulled into a PI and which won't, based on capacity, so negotiations can commence! How should it work? On the C...
2
Already exists
4
VOTE
Add delivery risk check for missing initial estimate
We use the initial estimate field for early product planning. While the "No detailed estimate" field helps for our detailed planning stage, we want similar functionality that checks for missing initial estimates to support our earlier planning.
0
Future consideration
4
VOTE
Add Parking Lot Releases and Features to Feature Roadmap and Release Gantt
Who would benefit? What impact would it make? I want to track upstream (pre dev) work in product and UX's lane to track true status end to end for our work. How should it work? When going into the features roadmap view I am trying to see my parkin...
0
Future consideration
28
VOTE
More visualization options for strategy diagram
The circular diagrams in the strategy section(Vision & Diagram) do not visualize well on today's browsers and monitors. Text is too small, data overflows. A more simple Left to right hierarchy would be more understandable, sharable and viewable.
9
Future consideration
4
VOTE
Support milestones in the release retrospective report
The release retro report currently uses only a single (pseudo) milestone: when development started. Some teams want to measure changes in the release relative to several milestones within a release, such as a beta launch, or code freeze.
0
Future consideration
3
VOTE
Improve Aha! Support of Using Microsoft Dictation
Who would benefit? Users with accessibility needs and using dictation tools. What impact would it make? But improving the use of Aha! features when using Microsoft Dictation. How should it work? Currently when using attempting to us Microsoft Dict...
0
Future consideration
4
VOTE
Manage who receives email requesting document reviewer edit access
Who would benefit? Workspace owners who are currently receiving all requests to edit a document from a reviewer. What impact would it make? The request to edit a document will be reviewed and approved more quickly with less noise to owners that do...
0
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved