Migrate JWT Parser expressions

The JWT Cloud expression parser differs from the JWT DC expression parser, so the migration of parser expression is often a complex task. You have to care not only for finding the corresponding field codes and parser functions but also for mapping parsing modes, time macros etc. This page gives an overview of what is mapped 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

General mode

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

Advanced text mode

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 numerivc field code, change it to a text filed code.

Examples

JWT DC	JWT 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

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

Numeric mode

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 %{ }

Text list mode

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 %{ }

Issue list mode

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 %{ }

JQL mode

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 DC	JWT Cloud
issuetype = "%{issue.issueType}" AND project = "%{00019}"	%{issuesFromJQL("issuetype = '" + %{issue.issueType} + "' AND project = '" + %{issue.project.name} + "'")}

Mixed mode

General mode

Replace {{{ and }}} by %{ and } (and migrate the fields and functions as described in Migrate field codes and Migrate JWT Parser functions)

List operators

In JWT DC, you can use the list operators APPEND, EXCEPT, INTERSECT and UNION. They are not available in JWT Cloud. But as described in Operators, you can use the functions append(), except(), intersect() and union() instead.

Field codes

Most of the field codes known in JWT DC are also available in JWT Cloud. For a list with detailed mapping information, see Migrate field codes.

Parser functions

Many of the parser functions known in JWT DC are also available in JWT Cloud. For a list with detailed mapping information, see Migrate JWT Parser functions.

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

Content

Space Tools

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