Releases
Sort by:
Trending
Status:
Showing 483
16
VOTE
Prioritization Board for Releases
What is the challenge?
Our organization regularly conducts prioritization exercises for the projects (releases) we have in the development pipeline, which provides guidance to our R&D team for planning future work. There is no prioritization...
1
Future consideration
9
VOTE
Update release phase selection dialog to handle multiple phases with same name
What is the challenge?
Cannot identify a release phase associated with specific release where there are multiple phases with same name
What is the impact?
Is extremely painful selecting a release phase. Often becomes an exercise of trial a...
0
Future consideration
71
VOTE
Support PI planning and Program Boards in Aha! Roadmaps
Aha! Develop has excellent support for SAFe in its program increment, sprint planning and program board functionality. Teams who are doing PI planning in Aha! Roadmaps with their engineering teams in other development tools are not able to benefit...
1
Future consideration
1
VOTE
Automation: Allow Automations for Release Phase and Release Phase To-Do objects
What is the challenge?
In order to track Release Checklists in Aha as to-dos by cross-functional team members needs automations to decrease amount of updates and auto assign appropriate owners.
What is the impact?
Cross-functional team mem...
0
Future consideration
1
VOTE
2
VOTE
Map Roll-Up Release Details to Sub-Releases
What is the challenge?
Currently, only the "parent" Roll-Up Release's Name, Internal and External Release Dates map to "children" Sub-Releases.
What is the impact?
Once Sub-Releases are added, user has to manually update their Status, Rele...
0
Future consideration
1
VOTE
Automation: Add Action to update Custom Field
What is the challenge?
When dates (ex: Release dates) change, it has a cascading impact to other functions. Allowing automation to update custom fields would help manage the impact.
What is the impact?
Without the automation, users are ask...
0
Future consideration
108
VOTE
Set capacity per team per release
Capacity for teams is currently available to set up at a 'global' level - number of hours per day per week. It would be helpful for teams that are planning releases with multiple teams, to be able to set a capacity for each team per release. Once ...
3
Future consideration
14
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...
2
Future consideration
36
VOTE
Support roll-up releases in retrospective report
The release retrospective report gives good insight to an individual release. I would like to see the same information for a roll-up release. This allows me to understand the delivery of large-scale projects across my organization.
4
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved