Support Project & Release for Release Burnup/down rather than "filter for release"

[Former user]

Pull for “Fix Versions” from a Project, rather than having to specify a “filter for Release” in the Release Burnup/down gadget.

Modification of the gadget would be:

‌

1. Populate a selector for Projects that the person has visibility into.

   1. Upon selection of a Project, load the releases (Fix Versions) defined within that project
   2. Populate a “Releases” drop-down from that Project.

2. Upon selection of “Release” from the Releases drop-down…

   1. Pull the dates, if any, defined within the Release, and pre-populate the date range to define the timeline of the burn-up/down.
   2. Still permit the user to modify those dates themselves.

‌

This would make the Releases Gadget incredibly more powerful and useful.

It might also be useful to scan and later display the “Number of issues” within a release that remain un-estimated.

[Danut M [StonikByte]]

Hi Marcelo,

Thanks for posting.

I like the suggestion but what you describe can be easily achieved with the existing functionality:

1. create a filter that includes the items from the fix version (like fixVersion = “1.0.0“)
2. configure the gadget to use this filter and set as Start/End the dates of the release defined in Jira

Also, you could use the Issue Formula Gadget to display the number of un-estimated issues in the release.

1. create a filter that includes the items from the fix version (like fixVersion = “1.0.0“ AND “Story Points” IS EMPTY )
2. configure the Issue Formula Gadget to use this filter and to make the COUNT of the issues from the filter.

‌

Considering the above, we do not plan to implement this enhancement soon.

Danut

‌

[Former user]

That’s a shame to hear.

‌

My recommendations were to specifically preclude having to create filters.

The suggestions were made in light of the fact that Atlassian just recently sunset their own release burnup gadget, that included both of the features I described.

Doing what you suggest is exactly what I’m currently doing, and it is precisely what I’m suggesting against having to do. Having to create filters for every single release is tedious, especially since the releases can be queried within a project, and could be used to populate a drop-down, and the gadget could perform the query itself.

I figured this might drive more customers to StronikBytes door, especially if Atlassian continues to make their gadgets less and less useful out of the box.