Section | |||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Jira expressions in JMWE for JIRA Cloud
Jira expressions in JMWE for Jira Cloud are used to insert information in
- Linked Issues Condition and Linked Issues Validator to check on each linked issue
- Scripted (Jira expressionBuild-your-own (scripted) Condition and Scripted (Jira expressionBuild-your-own (scripted) Validator to input a Jira expression to be evaluated
- Validator scope to control the execution of the validator in Linked Issues Validator and Linked Issues Status Validator
You can insert issue, transition and current user information into the conditions using Jira expressions.
Scripting features in Jira expressions
...
Limitations of Jira expressions
...
Limitations on the number of linked issues that will be taken into account
...
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.
- The expression's length is limited to 1,000 characters or 100 syntactic elements.
Limitations inside the Jira expressions written by users
...
no error reporting yet
...
: 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.Code Block issue.links.every(link => link.outwardIssue.versions.every(ver => (ver.name == "1.0")))
Evaluation will fail if there are more than 10 linked issues.