Currently the release notes of a version is comprised from all the JIRA issues with the "Fix version" value of the release notes version. This list does not take into account the state/phase of the issues, just the "Fix version" value.
For example, today the release notes includes issues that are in "rejected" or "closed", which means those issues will not be included in the release. (they were rejected or could'nt be repreduced, and therefore should not appear in the release note).
I'm looking for a way to tell JIRA to include only the issues that were really integrated into the release.
One simple way (but manual) to do that is to remove the "fix version" value from each issue that was "rejected" or "closed"
Anyone can think of a more efficeint way to solve this?
This page should help you:
Creating a Custom Release Notes Template Containing Release Comments
Sure, the title is all about adding "Release Comments" to your Release Notes. But read on... step 4 explains how to filter the notes.
As an optional extra, you can filter the release notes based on various issue properties to see if they match your criteria. For example, to print only issues that have a resolution of Fixed and a Status, put an
#if statement around the code that creates a bullet point for the issue...
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs