We highly recommended to test your expression before publishing the workflow.

5 steps to test your expression


Type in your expression or select one of the built-in examples.


Click on the Run button 


Select an issue you want to test your expression with.


Confirm your selection by clicking on Run


Check the resulting output or analyze the errors.



Before running your expression against a certain issue, it's recommended to check if the syntax is correct.

The syntax check button shows if the current expression in the input field is syntactically correct or not . The background check runs at least one second after the last input, but you can also push the Syntax button for instant results.



By clicking on the Run button, a test expression panel is displayed under your expression. To test your expression, do the following:

  1. Select an issue that you want to test your expression with (as the current issue).
  2. Click on Run




Even if the syntax of the expression is correct, it may happen that the expression result is erroneous, e.g. when fields are empty.

In the example below the value of the custom number field "cf10041" is returning a value which is not valid parameter for the function substring().


Depending on the Parsing modes and the expression itself, different Data types are being returned as a result of the expression.

Expressions written in the General mode will return texts.


Expressions written in the Logical mode will return a boolean value of true or false.


Expressions written in the Jira expression mode will return objects based on Data types (Jira expressions).



When composing complex expressions, e.g. in Logical mode or the Jira expression mode, where you compare values we recommended to:


Create individual expressions for the operands of the comparison.


Test each expression separately within the selected Parsing modes.


Merge the individual expressions and test the complete expression