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
Retrospective should ignore records that were moved in with "Will not implement" status
Who would benefit? Product Owners and Project Managers What impact would it make? This would reduce the list of records shown as "incomplete" when the records were added to the release after already been assigned "Will not implement" How should it...
Add field to capture date of "last change" on internal and external release date
Changes in release dates need to be communicated to several stakeholders. If there was a "last changed date" field for both the external and internal release dates, a report could be generated to show all release dates that have changed in say the...
Ryan Bradley
over 2 years ago
in Releases
1
Future consideration
I added a custom field to Releases for Project Type and created a filter for it on my Feature Board; however, when I select the Project Type I want to see on the Feature Board, it still shows all of the Releases for the product, regardless of Proj...
Brooke Watson
over 6 years ago
in Releases
5
Unlikely to implement
Notify Roadmap Stakeholders if an upcoming release is over/underplanned
What is the challenge? In our company, many stakeholders steer the contents of our product roadmap. It would be great if those stakeholders could be automatically informed if an upcoming release is over/underplanned. What is the impact? Better pla...
I love having To-dos on release phases as a sort of checklist (and, well, task list). But, usually only say one of the 5 or more to-dos can actually be done at any given time. I'd like to be able to set a start date for to-dos so that they don't a...
Guest
over 7 years ago
in Releases
6
Future consideration
Aha! Scorecard on Release apply to Master Features and Features
Title. Allow an "Aha! Score" which is applied at the "release" level to allow apply and synchronize to the "linked" Master Features / Features for Product Workspaces.
Guest
almost 4 years ago
in Releases
2
Future consideration
Correlate and sync release phases with jira sprints (or releases)
Right now the aha release phases just seem like an informational overlay with no connection to the features themselves or their JIRA equivalents. So when work gets estimated in jira or progresses these timelines don't change. I have to keep them i...
Snap Kitchen
almost 9 years ago
in Releases
3
Unlikely to implement
Milestones do not currently have a status associated with them. They are just there. This works great for future dates, but when the date passes there is no way to know if the milestone is complete or has been met. It would be great if there was a...
Gary Goz
almost 4 years ago
in Releases
2
Future consideration
Allow sub-releases to have independent release dates from a Rollup Release date
We're operating in a CI/CD environment, and prefer to release "releases" (especially API's) as soon as they clear integration and performance testing. Forcing all of the sub-releases in a Master Release to inherit that release date is not meeting ...
Guest
over 8 years ago
in Releases
11
Unlikely to implement