Need the ability to list features on multiple product release targets
We have a number of products that depend on features from other products.
We desperately need to be able to visualize the dependency inline on my product gantt view.
It could be partially transparent to show the difference between a "local" fe...
George Champlin-Scharff
over 6 years ago
in Releases
1
Future consideration
We'd like to estimate and plan releases based on velocity (rate of story point completion) rather than capacity (static value).
This would enable more dynamic calculation of release capacity given a target release date and velocit(ies) over the d...
We would like to see a kanban type board view for releases. The columns of the board would be used to represent status, and the cards themselves would be the release objects. This view is already available for Features, and we would like this styl...
Guest
over 5 years ago
in Releases
5
Future consideration
Add sub-releases for more than 10 linked products when creating a Master Release
When adding a master release for a large product hierarchy, the 10 item limit is an impediment, and the UI for adding releases 1 at a time afterwards is klunky
Guest
over 7 years ago
in Releases
0
Future consideration
We want to use release statuses to show if a release has a locked in launch date or is still in discovery/scoping. Currently we change the release status and it doesn't show anywhere. So what we have done to work around that is add an icon that sa...
Guest
over 5 years ago
in Releases
0
Unlikely to implement
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
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
about 7 years ago
in Releases
4
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
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