Unable to find a way to count the number of releases on a Dashboard Graph. Is this possible?

Greg McCarthy

As the title suggests I'm looking for a way to count the number of releases (versions) and display it in a graph.

For example Lets say we were talking about version 1.1 which had 1.1.0, 1.1.1 and 1.1.2 as released versions I would like to be able to count that there were 3 "point" releases. Is this something that is possible? I've had a good look through dashboard widgets etc but can't seem to find a way to capture this metric.

Any and all help would be greatly appreciated.

Earl McCutcheon

Hello @Greg McCarthy ,

Thanks for reaching out, currently there is not a built-in method for grouping releases in a way that would allow for monitoring all issues under a variable sub-release.  But looking at the tags you have here noted that you are looking for a solution on the Premium license Advanced roadmaps may be the solution you are looking for.  

Check out the following thread that goes into this in a bit more detail:

• https://community.atlassian.com/t5/Jira-Software-questions/Why-is-the-version-report-gadget-being-retired/qaq-p/1732861

And the documentation for versions in Advanced roadmaps mentioned in the thread can be found here:

• https://support.atlassian.com/jira-software-cloud/docs/manage-releases-in-advanced-roadmaps/

Alternatively, you could look into using Automation rules to populate a custom field with a combined marker,  then use that custom field in a filter statistics gadget. 

This would take a bit of set up and trial and error to fine tune the value to fit your exact needs as well as some maintenance over time as new versions are added but As an extremely basic example, you could create a rule that any time the value for fix version is changed, create a variable that takes the left 3 values of the string and populated these values into your custom field used in the gadget.   A quick test would be like the following noting i'm just updating the description for the test but you would want to use a custom text field with this approach:

and as an example of the output, the description is set to 1.0, 1.1 when the fixVersion is set to 1.0.2 and 1.1.1. then using a JQL for "your_custom_field is not empty" used in an issue statistics gadget could get the count using the custom field as one of the field metrics

Hope this helps get you on the right track.

Regards,
Earl