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...
Guest
about 8 years ago
in Releases / Sprints
2
Likely to implement
What is the challenge? Based on the popularity of these 2 ideas, there is a pretty big need to more easily find shipped releases. https://big.ideas.aha.io/ideas/APP-I-5819 https://big.ideas.aha.io/ideas/AFPR-I-7541 The difficulty exists because it...
Max Robbins
10 months ago
in Releases
0
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
almost 8 years ago
in Releases
4
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
about 6 years ago
in Releases
0
Unlikely to implement
I should be able to copy a release, Feature assignments, To Do assignments and Due dates from one release to another. I currently have 10 releases with all the same people assigned and with the same To Do dates. But the copy function is limited an...
Guest
almost 3 years ago
in Releases
0
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 9 years ago
in Releases
11
Unlikely to implement
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...
Guest
almost 4 years ago
in Releases
2
Future consideration
I'm not sure why it's not possible to have features in release templates. Phases and milestones are nice, but features are what actually have the status. This would be especially powerful for recurring releases. For example, I'm manually creating ...
Guest
about 4 years ago
in Releases
2
Unlikely to implement
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
about 8 years ago
in Releases
6
Future consideration
It should be possible to import releases on a product line level. Any level of workspace hierarchy which supports the creation of any records should also support the bulk import of these records via csv.
Guest
over 3 years ago
in Releases
0
Future consideration