Releases

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

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

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

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.

We use the phases and gantt chart for the high-level planning, and individual to-dos under each phase for the non-functional tasks. It would be great to have one report that expands all the phases and to-dos so all the planning is visible, as oppo...

Once we have created a release and scoped all the items into it, it would be helpful if we could "soft lock" the features in that release. A soft lock could be an option on each release with a toggle and a message. Once the toggle is ON and a new ...

It's not possible to see feature list in shipped release at all. Searching for features doesn't bring it up either. If this tools comes to replace PRD/ERD - deleting any record of implemented features is not a good idea.

If I need to move a Release Phase & all it's To-Dos/Features into another Release instead, I have to recreate everything. Would be nice to just drag & drop the Phase into another Release in the Gantt view.

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.

We create new products and releases for those products. Over time it may become apparent that the product, in fact, needs to be split up into additional products. Then, the releases must be moved. Each release contains phases and milestones with d...