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 expression) Condition and Scripted (Jira expression) 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
The following are the limitations while using Jira expressions in the Conditions and Validators of JMWE:
- The expression's length is limited to 1,000 characters or 100 syntactic elements
Limitations on the number of linked issues that will be taken into accountlimitations elements of the returned list: Some lists are limited to 50 elements in the final result. This will effect:
- Linked Issues
- Comments on an issue
- All Standard and Custom Multi-valued field (For example, Affects Version/s, Attachment, Custom field of Checkboxes type )
Limitations inside the Jira expressions written by users:
no error reporting yetNo 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. You can see the error only when you test the Jira expression against an issue in the Jira expressions editor. Do we need an example here?- no reliable evaluation of the "cost" of Jira expressions: Need to discuss