There has been a constant demand for the ability to include issues from different projects in the release notes. With the recent enhancements, that is now possible. Before, the JQL in templates did not include the project parameter & ARN would implicitly apply project filter based on project association. Now, the JQL in templates include project parameter explicitly. If you want to fetch issues from other projects just update the project filter accordingly.
For example:
Older approach: JQL{issueType=story and fixVersion='[versionName]'}
New approach: JQL{project=[projectId] and issueType=story and fixVersion='[versionName]'} - In this query, [projectId] will be replaced by the project id in whose context ARN pages were opened.
If you'd like to fetch data from specific project: JQL{project="PROJ" and issueType=story and fixVersion='[versionName]'} - In this query, irrespective of the project from whose context ARN pages are opened results will be retrieved from the specific project 'PROJ'.
...
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 -
| Code Block |
|---|
project='AR' and issueType=story and fixVersion="[versionName]" |
| Code Block |
|---|
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 -
| Code Block |
|---|
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 TemplatesOn this page | ||||||||
|---|---|---|---|---|---|---|---|---|
|
| Iframe | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
