Get started

Use case library

JWT expression editor

JWT expression parser functions

JWT remote actions

Cloud migration hub

Additional product info

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

Compare with Current View Page History

« Previous Version 2 Next »


Logical expression in JWT Cloud are built the same as in JWT DC. However, besides the general differences concerning field codes (see Migrate field codes) and parser functions (see Migrate JWT Parser functions) there are also slight differences in the logical parsing mode. They are explained below.


Multi-valued fields

In JWT DC so-called multi-valued fields are treated as lists (and not as simple text) when using the following logical operators :

  • ~, !~
  • in, not in
  • any in
  • none in
  • =~, !=~
  • ~~, !~~
  • in~, not in~
  • any in~
  • none in~

That means that it is possible to write expressions like 

%{issue.versions} in %{issue.fixVersions}

In JWT Cloud, this notion is not available. An expression dealing with such a multi-valued field has to be migrated by embedding the field code in the function toStringList (or toNumberList, respectively).

The following fields are considered multi-valued fields:


Migration of multi-valued fields in logical expression: Apply the respective function which builds a list depending on the operand: