Get started

Use case library

JWT expression editor

JWT expression parser functions

JWT remote actions

Cloud migration hub

Additional product info

The JWT Cloud expression parser differs from the JWT DC expression parser; therefore, the migrating parser expressions is often a complex task.

Besides field codes and parser functions, additional mappings of parsing modes, time macros, etc., apply. This page provides an overview of what is mapped and how.

Parsing modes

The parser in JWT DC offers different modes, which can be mapped to the modes provided by the JWT Cloud expression parser. 

JWT DC

Mapping

JWT Cloud

Notes

Basic text mode

(tick)

General mode

Replace the field codes by the ones provided in JWT Cloud, for details see Migrate field codes.

Advanced text mode

(tick)General mode

The whole parser expression  (which has been migrated as described in Migrate field codes and Migrate JWT parser functions) has to be enclosed by %{ }

If you use the "+" operator with a numeric value as the first operator in the expression, it has to be converted to a text using toString() or if using a numeric field code, change it to a text filed code.

Examples

JWT DCJWT Cloud
{issue.cf10004} +1
%{toString({issue.cf10004}) +1}
%{%{issue.cf10004} +1}
"This is a concatenated value "+{issue.cf10004} +1
%{"This is a concatenated value "+{issue.cf10004} +1}

Logical mode

(tick)

Logical mode

For differences between JWT DC and JWT Cloud logical mode, see Migrate logical expressions

Numeric mode

(tick)General modeThe whole parser expression (which has been migrated as described in Migrate field codes and Migrate JWT parser functions) has to be enclosed by %{ }

Text list mode

(tick)General modeThe whole parser expression (which has been migrated as described in Migrate field codes and Migrate JWT parser functions) has to be enclosed by %{ }

Issue list mode

(tick)General modeThe whole parser expression (which has been migrated as described in Migrate field codes and Migrate JWT parser functions) has to be enclosed by %{ }

JQL mode

(tick)General mode

The field codes which are used in the JQL query have to be migrated according to Migrate field codes. The whole expression has to be placed inside %{issuesFromJQL()}, re-writing the JWT DC expression as an addition of strings, such that the field codes will be evaluated before executing the JQL.

Example

JWT DCJWT Cloud
issuetype = "%{issue.issueType}" AND project = "%{00019}"
%{issuesFromJQL("issuetype = '" + %{issue.issueType} + "' AND project = '" + %{issue.project.name} + "'")}

Mixed mode

(tick)General modeReplace {{{ and }}} by %{ and } (and migrate the fields and functions as described in Migrate field codes and Migrate JWT parser functions)
List operators

The list operators APPEND, EXCEPT, INTERSECT and UNION available in JWT DC have no direct equivalent in JWT Cloud. However, you can use the expression parser functions append(), except(), intersect() and union() instead.

Field codes

Most of the field codes known in JWT DC are also available in JWT Cloud - see Migrate field codes.

Parser functions

Many of the parser functions known in JWT DC are also available in JWT Cloud - see Migrate JWT parser functions. 

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