Background
Sometimes one actual release can consist of multiple versions in Jira. In this case as well, ARN covers the ground for you. It finally boils down to how you write your JQL.Normally, ARN supports [versionId] & [versionName] variables. But when you need to generate release notes from multiple versions they are not sufficient. For such templates, you can use version variables as - [versionId1], [versionId2], [versionId3]…. & [versionName1], [versionName2], [versionName3]……so onteams release software at the end of every sprint, or they may just want to generate the release notes generated from a sprint. ARN has got your back here as well.
Recently, ARN added support for [sprintId] & [sprintName] variables. You can use these inputs variables in the JQL & the app will let you select sprint/s instead of versions.
Example
This is how to form your JQLs in ARN templates -
Code Block |
---|
project=[projectId] and issueType=story and fixVersionSprint in= ("[versionId1]","[versionId2]","[versionId3]")sprintId] |
Code Block |
---|
project=[projectId] and issueType=bugstory and fixVersionSprint >= "[versionId1]" and fixVersion < "[versionId2]" |
Now depending on the versions you pick and their sequence, release notes will be generated.
Depending on how many version variables your templates are using, accordingly ARN will ask for as many version inputs from you. Please note that [versionId] is treated as [versionId0].Now at the time of release notes generation, ARN will ask you for a sprint & not a version.
You can also generate release notes in ARN from multiple sprints. Just append the variables with 1, 2 & so on (i.e. [sprintId], [sprintId1], [sprintId2] etc)
Note |
---|
ImportantOnly way to provide multiple versions Sprint IDs or names to a rule is when executing the rule manually or via with the webhook. In case of version release - only released version will be passed to the templates In case of scheduled N days before release - only 'about to release' version will be passed to the templates In case of scheduled at interval - no version will be passed to the templatesSprint completed trigger. If the number of versions Sprints provided to the template are more or less than version sprint variables in the template, generated results may not match your expectations.
|
If you want to use ARN without relying on 'versions', simply use the JQLs without any version variables & then make use of triggers that are independent of Jira versions - such as Manual, Scheduled at interval.