Page History
| Page properties | ||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||
|
| UI Text Box | ||||
|---|---|---|---|---|
| ||||
The issue list parsing mode, just like the JQL mode, lets you define a target selection of issues. It is being used in Post functions and Automation actions, that allow you to create or updated multiple issues. The output has to be a valid issue list as defined in the Data types section. All JWT expression parser functions, that return an issue list can be used. Additionally issue lists can be constructed using functions like issueKeysToIssueList(). |
Example expressions
| Parser expression | Description | |||||||
|---|---|---|---|---|---|---|---|---|
| This example returns a list of all sub-tasks of the current issue. | |||||||
| This example returns: blue |
| UI Text Box | ||
|---|---|---|
| ||
Make sure to read all about working with Lists as they come with many extremely useful JWT expression parser functions. List functions can also be used in the Advanced text mode. The difference is, that the output will be a flat text instead of an issue list. The main advantage over the advanced text mode is, that you can use the returned elements of the issue list as Seeds. |
| Excerpt Include | ||||||
|---|---|---|---|---|---|---|
|
| Excerpt Include | ||||||
|---|---|---|---|---|---|---|
|
| Page properties | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||
|
