Releases
Sort by:
Trending
Status:
Future consideration
Showing 229
18
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
96
VOTE
Support release templates for rollup releases
When using master releases, it is not possible to select the release template for the sub-releases to be created. Which means the workflow to date looks like this:
Create a master release
Resist the temptation to select the products in the produc...
12
Future consideration
8
VOTE
Capacity planning for roll-up releases
What is the challenge? Some teams manage launches across large portfolios. Roll-up releases help to organize these at the workspace line level. Currently capacity planning is not possible for roll-up releases. What is the impact? It is not possibl...
1
Future consideration
63
VOTE
Expand/Collapse Release View to include Requirements
It's critical for our teams to see Features AND Requirements on the Release (Overview/Details View). You should be able to continue expanding down the hierarchy from Epic > Release > Feature > Requirement all within the Gantt.
8
Future consideration
8
VOTE
Add features to release templates
What is the challenge? Often, teams will create release templates when they have repeatable projects that follow similar steps. But release templates just include phases and todos. Many teams have more complex template needs for their project work...
1
Future consideration
1
VOTE
AI-generated release notes: Remove limitation of the generation of release notes (currently only creates output for 30 features)
What is the challenge?
Releases commonly contain more than 30 features
What is the impact?
Release notes generated with AI need to be run multiple times to cover all relevant records
Describe your idea
Remove the limitation of 30 fea...
0
Future consideration
13
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
6
VOTE
Have todo custom fields be a part of release templates
What is the challenge? Same as this idea, but for todos - https://big.ideas.aha.io/ideas/A-I-16116 There is now support for custom fields on todos, but these cannot be set within a release phase template. For teams using Aha! for project managemen...
1
Future consideration
2
VOTE
Allow parking lot releases to be roll up versions
What is the challenge? When reporting on Parking Lot releases with standard releases and utilizing the rollup for reporting, the parking lot column does not have any headings What is the impact? Reporting for our Sales team is confusing as there i...
0
Future consideration
37
VOTE
© 2024 Aha! Labs Inc.•All rights reserved