This week's point release continues to build on Agility's new approach available for teams to plan releases in a more flexible way. The old approach to release planning is now called "Increment Planning" to avoid confusion. However, if you have localized your instance the localization will remain unchanged.
Release Planning 2.0 removes the dependency on a planning level. In the past to create a release you had to consume a planning level. This works fine for clearly defined planning trees such as release trains in an ART. However, if you have teams from the across the planning tree this is more difficult. Release planning 2.0 provides users with the ability to relate items to a release within a value stream from across the planning tree.
Find out more using the link below to our documentation!
Link to Release Planning 2.0