...
The following configuration parameters are available for the table:
...
Name of the section. A section with the same name will be added to the release notes.
Columns to be shown in the table. User can select the majority standard and custom Jira fields. See details in the chapter below.
Section description. If the text is specified - it will be added as a plain text after the section name.
List of available JQL variables. In order to build flexible JQL which will use data from the selected version or package the user can inject variables to JQL query. List of available variables depends on the template type
Version specific variables
Version name
Start date
Release date
Version JQL (precompiled JQL which can help to extract the content of real or virtual version)
Project key (
Not applicable for virtual version)User name
Current date
Current timestamp
Package specific variables
Start date
Release date
Version JQL (precompiled JQL which can help to extract the content of package)
Please note that “Versions in package” variable is not supported since October 2020
User name
Current date
Current timestamp
JQL query to extract an issue list.
Group by. In the past we allowed grouping issues by Epics only in JQL tables. Now you can do it by most of single-, multi-select fields, epics, components, labels, etc.
...
Render section if result is empty. If the option is enabled the section will be rendered if JQL will return 0 rows. Otherwise, the section will not be rendered at all.
...
If this option is enabled all the issue will be grouped by respected Jira Epics.
...
...
Show epic key if grouping by epic is enabled
...
Layout - table or card
| Note |
|---|
Please note that old variables to extract all version or package content (fixVersion={version.name},fixVersion IN ({package.versions})) do not from October 2020. Please use {version.jql} or {package.jql} instead of fixVersion={version.name} or ,fixVersion IN ({package.versions}) respectively. This is the change we had to do to introduce virtual versions and align between fixVersions and Virtual versions. Thanks for understanding. |
...
The later is only available for Key and Summary fields. You want see a major difference when you generate notes, but when uploading to Confluence we will render it as Confluence standard issues status macross representing key, summary and up-to-date status.
As a side effect of this render type you will get a mention in your Jira issue about release notes generated in Confluence.
Calculated fields
We also provide a couple of additional "CALCULATED" fields to outline
...