Page History
UI Text Box | ||||
---|---|---|---|---|
| ||||
This function returns the result of a given Jira expression as a text. list with all substrings matching a given regular expression.In case a number, a list or a logical value is returned by the Jira expression, the returned text of the function jiraExpression() can be converted accordingly, e.g. with toStringList(). It unfolds its power when combined with JWT functionality which is not available in Jira expressions and vice versa. |
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
findPattern(text, regexjiraExpression(expression) #Output: Text list |
UI Expand | ||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||
|
UI Expand | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
Parameters used in this function
|
UI Expand | ||||||
---|---|---|---|---|---|---|
| ||||||
This function returns a
|
UI Text Box | ||||
---|---|---|---|---|
| ||||
Variant where you can additionally define a list of issues which can be used within the Jira expression given as the first parameter. You can access these issues through an injected context called issues. |
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
jiraExpression(expression, issueList) #Output: Text |
UI Expand | ||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||
|
UI Expand | ||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||
Parameters used in this function
|
UI Expand | ||||||
---|---|---|---|---|---|---|
| ||||||
This function returns a a
|
UI Text Box | ||||
---|---|---|---|---|
| ||||
Variant where you can additionally define a string of Issue keys which can be used within the Jira expression given as the first parameter. You can access these issues through an injected context called issues. |
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
jiraExpression(expression, issueKeys) #Output: Text |
UI Expand | |||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| If you want to ignore the case, have a look at the findPatternIgnoreCase() function.|||||||||||||||||||||
This example returns an ordered list of the unique component names of all sub-tasks of the issues listed in the second parameter, e.g. Backend, Frontend, UI You have to use flatten because sub-tasks of a list of issues are returned as a multi list in a Jira expression. Since the function returns a text, it is converted to a text list using toStringList(). |
UI Expand | |||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||
Parameters used in this function
|
UI Expand | ||||||
---|---|---|---|---|---|---|
| ||||||
This function returns a
|
Use cases and examples
Page properties report | ||||||
---|---|---|---|---|---|---|
|
Page properties | ||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||
|
Page properties | ||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||
|