|
Jira expressions in JMWE for Jira Cloud are used to insert information in
You can insert issue, transition and current user information into the conditions using Jira expressions.
To learn more about Jira expressions:
Jira Cloud enforces the following stringent limitations while using Jira expressions. This section explains them in context to JMWE. For more information, see the official Jira expressions documentation.
Limitations inside the Jira expressions written by users: The expression can execute at most 10 expensive operations (expensive operations are those that load additional data, such as entity properties, comments, or custom fields). For example, A condition that checks for a version 1.0
on every issue linked to the current issue.
issue.links.every(link => link.outwardIssue.versions.every(ver => (ver.name == "1.0"))) |
Evaluation will fail if there are more than 10 linked issues.
No error reporting: If a Jira expression evaluation returns an error, the error is not reported/logged anywhere. Since any non-boolean value, including an error, will be considered as false
the condition will fail. However, you can see the error when you test the Jira expression against an issue in the Jira expressions editor. For example: When you write a condition to check that the linked issue has the multi-select custom field has the value "Database" selected:
linkedIssue.customfield_10401.any(it => it.value == "Database") |
the condition when tested will return the following error:
You need to instead use the "some" property to check that the specific value is selected.
linkedIssue.customfield_10401.some(it => it.value == "Database") |