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...
Guest
about 10 years ago
in Releases
12
Future consideration
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...
Madeleine Black
over 2 years ago
in Releases
1
Future consideration
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.
Guest
almost 7 years ago
in Releases
8
Future consideration
Show a release report, listing all to-do's nested under the phases
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...
Paul Derbyshire
almost 11 years ago
in Releases
7
Future consideration
Ability to move Release Phases from one Release to another
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.
Guest
over 6 years ago
in Releases
4
Future consideration
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.
Jeff Tucker
about 2 years ago
in Releases
4
Future consideration
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...
Guest
about 11 years ago
in Releases
7
Future consideration
This functionality is available for every other record type, user expectation is that it you would also be able to track progress across all Releases within the Master Release. This is a request from our Senior Leadership team as well to track por...
Guest
over 5 years ago
in Releases
3
Future consideration