You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

On this page

Introduction

The Expression Parser Test page provides the capability to test/evaluate JWT expressions against existing issues.

Besides the issue key to evaluate, you can choose one of the five different parser modes described below.

The Expression Parser Test page does not support all field codes  Field codes for transitional fields e.g. Transition comment, are not supported.

Issue key

All issue related expressions will be evaluated against the issue selected.

Parsing mode

The chosen parsing mode determines the parser functionality and any data returned by the evaluation.

parsing mode determines how the JWT expression parser interprets an expression. 

The available parsing modes depend on the context you are using the expression in. As an example, only the Logical mode is available if you configure a conditional execution in a workflow post function or that you can only use the Numeric mode if you want to set a number field using a parser expression.

Available parsing modes

Most functions will accept text values so casting values to text is a very powerful function

Additionally, you can directly transform a field value to text using the following syntax: %{...somefield}

You can write your text in basic text mode, and then switch to advanced text mode using Automatic parsing mode converter.

The text to be parsed will be automatically rewritten as a text expression. Now, you can simply make the modifications you require, making use of text formatting functions, or inserting math or time expressions where needed.

To update issue fields the parsing result will be cast to the expected value e.g. a user name will be cast to a user to update a user field like the assignee field.


If you still have questions, feel free to refer to our support team.


If you still have questions, feel free to refer to our support team.