how to automate a dashboard that shows all fixes done in a particular release?

[Ahmed Alghamdi]

the way we are setting up jira, we have major release (that goes to store) and we have normal releases (which happens every couple of days almost).

every normal release we do, we tag the fix version related to them and push it for internal QA. once we are ready to go live-customers (every 2 weeks) with a major release, we ask QA to do regression on all fix versions of the normal releases (sometimes we have 10 builds - more or less)

the issue is, we keep on manually searching for all those fix versions to be able to extract the full list of issues between each major release

is there anyway we can automate this process? so we get a list of major releases including the fixes between them including all builds?

[David Berclaz _Apwide_]

Hi @Ahmed Alghamdi

If you want to go one step further, you can implement what we called a "Dynamic Release Notes" when I worked at Nestlé.

A Dynamic Release Note is the dream of all QA teams: a Release Note that gives a list of Jira issues that can be tested at the very moment.

It's updated automatically with new deployments, when Test Environments are DOWN or UP again, and when issues are resolved. Watch this video for more info:

https://vimeo.com/423883416

Let me know if you have any questions.

Cheers,

David

[yurikudin]

Hi Ahmed,

I would suggest you using Release Management Add on for this. (Cloud version is also available)

Let me simulate your case in the add on:

1. Create Release with the major version 0.1

2. Plan scope for your version

You can also create a workflow for the version and entire release, but in our case let's use the basic one.

When you would like to plan a hotfix or external build  - you could create a new version for it and add it to the release. All the issues which have to be done in the scope of the hotfix  - will be assigned to this ner version

In the add on you can see the scope of an entire release (core version + all hotfixes) or scope of only core version or one/many hotfixes. There is a lot of flexibility there. 

Also, track the hotfixes progress at hight level on the kanban board;

The cherry on top:

There is an option to track where each version and hotfix is deployed. This will simplify the work of your testing team.

Also, you are able to bound hotfixes roadmap

You can play with the add on here: https://dev.releasemanagement.app/secure/release-management.board.jspa?id=206#timeline

User demo, password demo

[Bill Sheboy]

Hi @Ahmed Alghamdi 

With out-of-the-box JIRA, you could create a filter and subscribe to it.  Here is the how-to for server version: https://confluence.atlassian.com/jira064/receiving-search-results-via-email-720416706.html

If you have an add-on, like the automation rules, you could also make a more customized report.  There are probably other marketplace add-ons to do this also.

Best regards,

Bill

[Ahmed Alghamdi]

Thanks a lot Bill, i may have not made my question clear

i dont need email subscription.

rather, i'd like a filter that updates automatically every release to show all the fix versions including in that active release.

for example if we work on builds 0.1.01 - 0.1.02 - 0.1.03 then we decide to release to customer a major release of 0.2.0 to store. this builds will include all prior internal builds  (0.1.01 - 0.1.02 - 0.1.03)

can we automate a dashboard to always show all issues that were fixed in all builds up to major releases 

[Bill Sheboy]

Hi @Ahmed Alghamdi 

Thank you for clarifying.  There may be a marketplace add-on to enhance version handling, as what you are asking for doesn't exist in JIRA.

Do you assume each build will be in the next major release...and after that major release deploys, you repeat?

If so, you could try this:

• Add a custom field for the major release version
• Add an automation rule to automatically set the custom field, calculating it from the FixVersion.  (This works if your release naming is consistent, like in your example.)
• Make a filter to show and order items by the major release version
• Show that filter on a dashboard

If you do not want to have 2 version/release fields, you could instead put 2 values in the FixVersion field: the build version and the major release version.  That would complicate the filter/dashboard work.