Releases
Sort by:
Trending
Status:
Unlikely to implement
Showing 471
13
VOTE
Calculate Release Date Range from Epics
What is the challenge? There are teams who only use Epics in their workspaces, but the date range of Releases can only be calculated from Features. Moreover, there are no automation rules or integration mapping options to automatically update the ...
3
Future consideration
2
VOTE
Automatically create releases on a set schedule (weekly/monthly/quarterly)
What is the challenge? Creating new releases manually is cumbersome. Often we need to create releases from templates on a consistent weekly or monthly basis. It would be nice to be able to automate this. What is the impact? It's more work to do it...
0
Future consideration
6
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...
0
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
17
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
3
VOTE
Ability to add automation to move a work item to a different release based upon a field
What is the challenge? There are times that certain records can move to a different release based upon the selection of a predefined choice field and do not require analysis and decisions. What is the impact? Inability to set up automation to do t...
1
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
95
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
59
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.
7
Future consideration
5
VOTE
Create a release when accepting a work request
What is the challenge? Today, work requests cannot be accepted as a release record. In my use case, I am coordinating cross-product initiatives at my company line. I want to request work from my GTM team who works in a separate GTM workspace for t...
0
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved