Releases

What is the challenge? I would like to have an option to automatically nest all the features in a release, under a release phase "development". Currently there is no automation so each feature needs to be added manually. What is the impact? More ...

What is the challenge? Aha! date fields currently expect exact calendar dates, even when teams only know timing at a broader planning level such as fiscal week, month, quarter, or year. To represent those plans, users have to manually choose artif...

What is the challenge? Phases tab of Releases is not customizable and provides very limited value. Name and date don't provide meaningful insight into the phases. Going into each individual phase for more information is inefficient. What is the i...

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...

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 ...

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...

What is the challenge? Product managers working in the features board cannot easily tell whether a workspace release is attached to a roll-up release. That relationship is available if someone clicks into the release, but in practice many users ...

What is the challenge? If a release template exists it is automatically set as the default release template within your workspace. There is no way to set the default to not use a release template, without creating a blank release phase templat...

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...

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.