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.
Jeff Tucker
12 months ago
in Capacity planning
0
Future consideration
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...
Karla Johnson
12 months ago
in Releases
0
Future consideration
Sometimes users realize that their initiatives are actually way bigger than what their company deems acceptable size for initiatives. It should be very easy to convert an initiative to a goal. If that initiative includes Epics (Master features), t...
Guest
almost 6 years ago
in Strategy
0
Future consideration
Providing a template would help our users work in Aha! rather than creating one outside and uploading it. Our users need a bit more help than the Vision Description in the Strategy section.
Guest
about 1 year ago
in Strategy
0
Future consideration
The new Gantt chart is much larger vertically than the old one. Is there a way for me to reduce the height of each row? I can no longer see all of my release on a single screen
Guest
over 4 years ago
in Application
4
Future consideration
Allow workspace owner to grant additional permissions when access is given at the line level
What is the challenge? When users have been given access at a line level, workspace owners below that line cannot give them additional access (i.e. if someone is a reviewer at the line level a workspace owner in that line cannot make them a contri...
Julia Pence
6 months ago
in Account settings
0
Future consideration
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.
Jeff Tucker
12 months ago
in Reports
0
Future consideration
When creating a pivot report across a number of products the Vision components are not available from the object list. My use case is that I would like to consuct a review of the assembled vision components across a number of products within a pro...
Paul Dickie
over 5 years ago
in Strategy
1
Future consideration
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...
Julie Price
12 months ago
in Notes / Whiteboards
0
Future consideration