Releases

Why is it useful, who would benefit from it, how should it work?

The Release Portfolio is a good start on providing the ability to visually schedule resources, but it lacks some simple and extremely useful features: Simple leveling. There should be a way to assign resources to each feature, and level the sched...

only csv available

We typically work on development for 3 weeks, have the release in beta for 1 week and then push it to production. Currently the push to Beta and Prod is handled manually by communication and calendar notifications. As all the phases are defined i...

We are an agile software company that releases on a cycle of 3 sprints, each 2 weeks long. We can set our release capacity based on the # of development hours to determine about how many features we can commit to, but we also need to plan how many...

Just a suggestion but in the 'Release Portfolio' view it would be great to have a collapse all/view all button that would open all sub phases (and features) to a releases rather than selecting to open/collapse all individually especially when feat...

I have many post-release activities that I'd like hang off the release date, which does move now and then

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

We would like to be able to extract some insights from our Aha data. For each release: How many points over capacity are we? After the first sprint in a 2-sprint release is completed, are we half way done with story points? How many features do w...

When I'm relating releases back to product strategy, I would like to create a relationship to Product Line initiatives, so I don't have to re-create the same initiatives for all products in a product family.