On this page
JWT is capable of processing various types of lists, including text, number and issue lists. This page contains valuable information about working with lists.
The list data type is an ordered list of elements. Those elements have a certain data type (text or number).
It is possible to:
- access individual elements (e.g. using the function nthElement()),
- create lists out of virtual fields (e.g. using toStringList()) or
- use the list functions presented on this page to work with lists.
Fixed values
A list can be written in literal as a comma separated list of texts in double quotes written inside brackets.
| Expression | Description |
|---|---|
[] #All lists are enclosed in brackets. | An empty list. |
["Blue", "Green", "Yellow", "Orange", "Red"] | A text list with five elements. |
[1,2,3] | A number list with three elements. |
[1, {issue.subtasks.count}, {issue.links.count}]
| A number list with three elements using field codes and JWT expression parser functions. To achieve this, the following virtual field codes: |
toStringList(%{issue.components})
| A text list with all components of the current issue. Fields codes of multi-valued fields, such as components, labels, etc. by default return a text with a comma separated list of values. If you want to individually process these elements, you need to convert the text into a text list using toStringList(). Learn more about Converting data types. |
Reading values from issue lists
Most of the times, lists are being defined or returned using field codes or JWT expression parser functions. In order to read or retrieve values from an issue list, functions such as fieldValue() must be used.
| Expression | Description |
|---|---|
fieldValue(%{issue.assignee}, subtasks())
| A list of all assignees of the current issues's sub-tasks. The list may contain duplicate user names. To achieve this, the following functions were used: |
distinct(fieldValue(%{issue.assignee}, subtasks()))
| A list of all distinct assignees of the current issues's sub-tasks. The list only contains unique user names. To achieve this, the following functions were used: |
fieldValue(%{issue.priority}, linkedIssues("blocks, is cloned by"))
| A list of priorities of those issues linked to current issue through issue link types "blocks" and "is cloned by". To achieve this, the following functions were used: |
distinct(fieldValue(%{issue.components}, issuesUnderEpic()))
| A list with distinct components of all issues which are linked to same epic as the current issue. To achieve this, the following functions were used: |
Number list (only) functions
The following list contains all the available functions that work with number lists only.
| Function |
|---|
| No content found. |
Issue list (only) functions
The following list contains all the available functions that work with issue lists only.
| Function |
|---|
| No content found. |
If you still have questions, feel free to refer to our support team.
