Skip to Main Content
ADD A NEW IDEA

Releases

Showing 89

As the "Owner" of a release, I would like to be able to close it so no new features can be added.

As releases are usually bounded by e.g. development capacity, or certain themes (marketing message) it should be possible to close a release if capacity is reached. Closing means that the "owner" of the release can indicate that no more features c...
Guest almost 9 years ago in Releases 0 Unlikely to implement

Make it harder to accidentally delete release phase dependencies in "release detailed" view

I am constantly clicking the red x and deleting release phase dependencies when I go to change the length of a phase. I have no idea how many times I've done this, basically 90% of the time that I adjust the length of a release phase. There were a...
Eva Humphrey almost 9 years ago in Releases 0 Unlikely to implement

Release Phase - Send to TFS

Be able to send just the features and requirements over to Visual Studio TFS for a Release Phase. Currently we can only send over the Features and requirements for the entire release, or feature by feature. Having the ability to do it per phase...
Guest almost 9 years ago in Releases 0 Unlikely to implement

It should be possible to "block" release dates

Playing with gantt chart can cause a lot of problems, especially when moving releases/stages/features using mouse - it will be great to have a chance to block dates. In my opinion it should not be possible to change "scheduled" and "shipped" relea...
Guest almost 9 years ago in Releases 1 Unlikely to implement

Allow NON-Product Owners to generate Pull Requests over Release, Feature or Strategy fields

In a distributed team, not always the Product Owner (Product Manager) is in charge of all the aspects of a release or a feature. A typical example would be dates, where a Service Manager owns the date changes. In this situation, and when we do not...
Pablo Antolín about 9 years ago in Releases 0 Unlikely to implement

Disable notifications

On occasions, I have had to change the status of a release back to open and then close it again. This resends the release to everyone subscribed. I would like to be able to disable sending a notifications for this type of maintenance.
Rob Bedeaux about 9 years ago in Releases 1 Unlikely to implement

Have a Release Workflow Custom Status trigger the Send to JIRA action

In the end I just want to be able to manage the Send to JIRA trigger action via either my Features Workflow or my Releases Workflow. Send to Dev to me equates to send to JIRA. I will want to make sure my status is updated throughout, so I will alw...
Guest about 9 years ago in Releases 2 Unlikely to implement

Track any feature changes after release has moved to specific status

After a release has moved to a status of 'Committed' for example, we would like for any watchers (or other subscription) of the release to have an email or view that lists any changes with features moving in and out of the release. As a nice to ha...
Guest about 9 years ago in Releases 0 Unlikely to implement

Provide tools for Change Control

Once development on a release is underway, things happen. Change Control should encompass approvals and permissions to edit dates and schedule, and rollback. Here are some requirements: 1. A product owner (or an "uber product owner", e.g. the VP o...
Guest over 9 years ago in Releases 1 Unlikely to implement

Add ability to hide the release section on the initiatives view

It doesn't make sense to show the release view on the initiatives because it pertains to the overall release features not the related features for that initiative.
J. Mile over 9 years ago in Releases 2 Unlikely to implement