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 - 

projectissueType=[projectId]story and Sprint = [sprintId]

issueType=story and Sprint fixVersion in ("[versionId1]","[versionId2]","[versionId3]")= [sprintName]

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). For Eg. -

project=[projectId] and issueType=bugstory and fixVersionsprint >in ("[versionId1sprintId1]" and fixVersion < ,"[versionId2sprintId2]"

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].

Image Removed

,"[sprintId3]")

Image Added