Introduction to JQL section

This section plays a crucial role in ARN templates. JQL dictates the appearance of your content and determines the data to be included in release notes and reports. It serves as the central hub for all information intended for end users.

There are three tabs on Add/Edit JQL section pop-up -

• Section

• Fields

• Layout

Section

In the section tab you will find below fields to define the content that will be posted in the release notes.

• Title - This text will be shown as a section header in the generated email or page.

• Description - This fields can contain the description of your given JQL section.

• JQL - This field is where you add the JQL to fetch the relevant issues to your release notes

• Hide section (checkbox) - Check if you wish to hide the JQL section when given JQL does not return any Jira issues

• Message - When the checkbox is unchecked, write a message that needs to be displayed when no issues are returned from the given JQL.

Fields

This tab is to display what all Jira issue fields/custom fields that are to be added to your release notes. If the Table layout is selected then these fields are added as columns. In the case of the sequential layout, selected fields will be listed in the sequence you have added them.

As shown in the below image, icon in front of each selected field would show some extra settings for the field like header style, Entry Style, display as link or text, etc.

Open

Read how to Save release notes without Jira fields using issue properties.

Custom CSS

Introduction

To further customise the release notes that ARN generates, it is possible to configure custom CSS within different templates.

How to

Open any one of the above-mentioned template types & click on any JQL section to open it in Edit mode or start to Create a new one. Make sure the layout/format is set to Table.

Custom CSS can be applied for any of the selected columns, listed in the left-hand section of the Fields tab. Click on the gear icon beside any column name & it will reveal a couple of free text fields where custom CSS can be added.

Open

Header styles refer to the styling applied to the table header for that specific column whereas Entry styles CSS attributes are applied to all the data points generated within that column.

If the JQL section data is grouped by a specific column, it is possible to apply custom CSS to that data as well. Just click on the Gear icon beside Group by option. It shows the custom CSS options.

Layout

Table layout

This layout is fairly straightforward & does not need any additional configurations. All the fields that are selected (from Feilds tab as shown in the above image), will be displayed as table columns from left to right. Below is a sample screenshot of the generated release notes in tabular format.

In this example you can see coulmn in the table like Priority, Key, Status, Issue type, and Summary. At the left top corner of tble notice the Task issue type icon which means the table is grouped by the issue type. This way using different customisation you can define the way of displaying issues from the given release.

Sequential layout

Selecting equential layout presents the selected fields (from the Fields tab) in a sequenced format. The desired layout needs to be designed within the area highlighted below.

Here, the design is simply a sequence of available variables. These variables are displayed based on what fields you have chosen on the Fields tab.

Any fields that you have selected to be used, can be arranged in any order you wish. For every field that is configured under Fields tab on the left, there will be two variables on the right. One that will fetch the field value & other to fetch its display label. e.g. for Priority field, there are two variables - {priority} & {priorityLabel}.

Required condition is, you have to add fields & their configurations before they can be used in the Layout section. The layout created will be repeated for every issue that is returned by your section JQL. For example, layout in the above screenshot will generate data that looks like the below screenshot.

In below image check the check box called Hide field label variable when the field value is empty. If this is checked, and if the JQL does not fetch any data in the field value against a particular issue, then it hides the field variable and you can make sure that the release notes do not look like an incomplete piece of information.

Configuring Group-By Behavior in JQL Sections

Introduction

Grouping issues in JQL sections using a specific Jira field is now more versatile with this grouping behavior with the help of “Group-by” fields. This functionality enables users to choose how issues are grouped—either by combinations of values or by each unique value. This ensures that issues with multiple values can appear under multiple groups, providing greater flexibility and control.

The ‘Group by’ setting gives users the choice between these two grouping methods -

• By combination of values:

  • Groups issues based on unique combinations of values in the 'Group-by' field.

• By individual values:

  • Groups issues by each unique value in the ‘Group-by”’ field, repeating issues in multiple groups if necessary.

Example

Below is the list of issues with a custom field called 'Component'. The user wants to group the issues by these components.

Base on the selected grouping option/behavior the final output will be created as below

By Combination of Values

By Individual Values

Notes

• This setting applies to both first-level and second-level “Group-by” fields.

• The “By combination of values” setting preserves the current grouping logic, ensuring no changes to existing outputs.

• The “By individual values” option replicates the grouping behavior already available on the issue listing page in the RPR app.

• If you want those groups to appear in a certain order (ascending or descending), then you should include the group-by field (Components field in this case) in the Order by clause of the JQL as shown in below image.

Orphan elements

• Now if there are any Jira issues where the value of the Components field is blank, such issues are called orphans.

  • By default, the orphan issues are placed at the bottom of the group.

  • However, you can choose to place them at the top of the group.

  • Navigate to the field customization menu of the concerned group by field to choose where the orphan issues should be placed.

Introduction

The JQL functionality in MS PowerPoint operates uniquely compared to other templates such as Email and HTML.

Below, we elaborate on the process of incorporating a JQL section for creating release notes and reports in MS PowerPoint format.

The JQL section in MS PowerPoint template has three tabs -

• Section

• Fields

• Available variables

Section

This tab contains only JQL that will fetch Jira issues and their details to your release notes or reports.

Fields

This tab is to display what all Jira issue fields/custom fields that are to be added to your release notes and reports. This will generate a sequential layout by default in PowerPoint slides, selected fields will be listed in the sequence you have added them.

As shown in the below image, icon in front of each selected field would show some extra settings listed below -

• Display as text -

  • If checked, value will be displayed as text

  • In case of Description field, if this setting is checked, value of this field will be displayed as text ignoring any media files and links in the content fetched from the Jira issue content. Currently MS PopwerPoint template does not support images from the Jira issue content.

• Hide field label variable when the field value is empty -

  • When checked, if the field value is empty, the field label variable shall also be kept empty in the sequential layout.

Available variables

• All the Jira issue variables and custom field variables that you have added from the Fields tab are displayed in this tab. So it becomes easy to track all the variables you need to add to the slide that you want to upload in MS PowerPoint template editor.

Introduction

The JQL functionality in MS Teams template operates uniquely compared to other templates such as Email,HTML, etc.

Below, we elaborate on the process of incorporating a JQL section for creating release notes and reports in MS Teams template.

The JQL section in MS Teams template has three tabs -

• Section

• Fields

• Layout

Section

In the section tab you will find below fields to define the content that will be posted in the release notes.

• Title - This text will be shown as a section header of the Jira issue list fetched using the given JQL section.

• Description - This fields can contain the description of your given JQL section.

• JQL - This field is where you add the JQL to fetch the relevant issues to your release notes

• Hide section (checkbox) - Check if you wish to hide the JQL section when given JQL does not return any Jira issues

  • Message - When the checkbox is unchecked, write a message that needs to be displayed when no issues are returned from the given JQL.

Fields

This tab is to display what all Jira issue fields/custom fields that are to be added to your release notes and reports. These fields be added as columns if you are using a table layout or selected fields will be listed in the sequence you have designed in the layout tab when sequential layout is selected.

As shown in the below image, icon in front of each selected field would show some extra settings -

• Display as text -

  • If checked, value will be displayed as text

  • In case of Description field, if this setting is checked, the value of this field will be displayed as text ignoring any media files and links in the content fetched from the Jira issue content.

• Hide field label variable when the field value is empty -

  • When checked, if the field value is empty, the field label variable shall also be kept empty in the sequential layout.

Layout

Table layout

This layout is fairly straightforward & does not need any additional configurations. All the fields that are selected in Feilds tab (as shown in the above image), will be displayed as table columns from left to right.

Sequestial layout

Selecting equential layout presents the selected fields (from the Fields tab) in a sequenced format. The desired layout needs to be designed within the area highlighted below.

In above image, the design is simply a sequence of Key, Priority, and Status fields from Jira issues, . These fields are displayed based on what fields you have chosen on the Fields tab.

Any fields that you have selected to be used, can be arranged in any order you wish. For every field that is configured under Fields tab on the left, there will be two variables on the right. One that will fetch the field value & other to fetch its display label. e.g. for the Priority field, there are two variables - {priority} & {priorityLabel}.

Required condition is, you have to add fields & their configurations before they can be used in the Layout section. The layout created will be repeated for every issue that is returned by your section JQL. For example, layout in the above screenshot will generate data that looks like the below screenshot.