Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Background

Different teams plan their projects differently. Many teams want release notes to be generated across different Jira projects. It is possible to address this scenario with proper use of JQL queries.

Solution

There are two ways you can get issues from different Jira projects.

  • Creating different JQL sections for different projects

  • Using project identifiers in the same JQL section

Creating different JQL sections for different projects

In this case you will create different JQL sections for each project.

For example, if I wanted to generate release notes to include stories from two Jira projects. Here’s what corresponding JQLs would look like -

project='AR' and issueType=story and fixVersion="[versionName]"
project='UD' and issueType=story and fixVersion="[versionName]"

Using project identifiers in the same JQL section

In this case you will tweak the JQL in the single section that you have in the template.

For example, if I wanted to generate release notes to include stories from two Jira projects. Here’s what corresponding JQL would look like -

project in ('AR', 'UD') and issueType=story and fixVersion="[versionName]"

Trick

JQLs above use fixVersion = “[versionName]” and not fixVersion = “[versionId]”

For the desired result in ARN, versions in both the projects should have same name. e.g. if both projects have version named V1.0 the query will work as expected but not if the version names are different such as V1.0 - android and V1.0 - iOS

Need to generate release notes from different projects that have different version names? Follow below link -

Using Multiple Versions in ARN Templates

On this page



Request support 👨‍💻

Leave us a review (green star)


  • No labels