What is the challenge? I was actually trying to figure out a way to do this with a custom setup and noticed the prioritization screens for Features and Ideas. We need it for releases! What is the impact? Other than the order of the gantt chart and...
Bob W
9 months ago
in Releases
0
Future consideration
Dates of release phases and milestones are auto populated whenever release phase templates are applied to releases. This is not a expected behavior, as most of the time dates are not confirmed yet when a release is created. This is confusing given...
Hank Liu
over 1 year ago
in Releases
0
Future consideration
Allow for consistent formatting when using AI to draft release notes
What is the challenge? We have multiple products and multiple releases happening over time. Each time a product owner creates a release note the formatting usually is different. What is the impact? The product owner then has to manually update the...
Guest
9 months ago
in Releases
0
Future consideration
What is the challenge? Not able to move feature to next release What is the impact? Feature that have not been completed are shipped with the release Describe your idea When using a fixed workflow approval to ship a release, you should not be prev...
Stuart Blair
9 months ago
in Releases
1
Future consideration
to-dos in a release template should inherit the phase or milestone dates
The release template concept is great, but the ability to assign tasks to these things is what helps get the work actually done. You can put a to-do into the release template, but when a release is instantiated on that template, all the to-dos hav...
Guest
over 7 years ago
in Releases
4
Future consideration
The views for Releases are inconsistent. The details view, Gantt and Features board all place them in a different order and they don’t behave in the same was as other records. For example, in the Details view with the cards on the left, I can’t re...
Lindsay Zandy
over 2 years ago
in Releases
2
Future consideration
Using SAFE terminology, I have epics (master features) that relate to multiple program increments (releases).
I'd like to be able to assign a master feature to more than one release at a time.
Guest
over 5 years ago
in Releases
0
Unlikely to implement
Add Workspaces linked record options under related
We have our workspaces broken down by teams. Sometimes a team may need to make changes to an area of the program that is owned by another team. We need a way to document this. It would be great if under the related section - Linked Records, we had...
Brett Wilmeth
over 1 year ago
in Releases
1
Future consideration
Having flexibility around Release Dates being either inherited from Rollup release or manually populated
We rely on Rollup releases quite a bit, however, from team's Feature board perspective it's often helpful to track "product" releases info, especially dates and be able to expose those accordingly. At this point, since we're using Roll up releases...
Olga Basman
over 3 years ago
in Releases
2
Future consideration
Burn *Up* charts for Sprints, Releases, Epics, and Features
My company would find it useful to have Burn *Up* charts that show how the effort completed is tracking against the scope of a release / master feature / feature For more on the requirements for a Burn Up chart and why it is more useful than a Bur...
Mark D
over 7 years ago
in Releases / Sprints
2
Future consideration