Releases

When reviewing the feature burndown (Progress), I would like to see a listing of features completed, upscoped, downscoped in a list form rather then having to hover over the segments on the chart. While hovering is a great feature, it does not all...

Today the Date Range fields are not available on the Create Record Layout for Releases. We want to be able to Create a Roll-up Release at the Line level and at the same time create the Sub-Releases automatically with the same Date Range and we can...

We would like to be able to 'lock down' some fields unless there is approval to change them. For example, Release date (or due date) Budget Designated people in the company would be required to approve any changes to these fields. Along with this,...

What is the challenge? When drafting release notes, there is a limit of ~12k words across all the record names and descriptions. If I try to draft release notes with too many words, I have to start the process first, and then it eventually fails. ...

When we manage our roadmaps, managing the release date is most critical to our customers and partners. It would be very helpful to have reusable external watch lists (like already exciting on releases and other areas) and send them an email when t...

There is already a similar thing to downgrade a feature to an idea. The justification is this - We create an idea for a feature Once we understand it enough to decide if we are going ahead with it, we will commit resource to properly planning it ...

Who would benefit? Our dev management team What impact would it make? Would provide much better insights into why a release went off track. Currently the "Records Added" section lists Epics & Features added after dev started. In our case, it's...

As an enterprise SaaS software provider, we need to manage releases in two key categories, major and minor, so that we can monitor the iterative delivery of our minor releases as a part of our major, less frequent, releases and provide clarity to ...

Sometimes we created a release when we meant to create an initiative. Rather than manually creating the initiatives and deleting the release, it would be nice to use the "Convert to" tool to convert them automatically.

We need a burndown at the master release level. We have multiple product groups working together and we need to see a burndown for all of the work combined.