Page History

Logical expressions in JWT Cloud are built the same as in JWT DC. In addition to the basic differences in field codes and expression parser functions, there are a few other minor differences that are explained on this page.

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

That means that in JWT DC it is possible to write expressions like 

%{issue.components} any in %{parent.components}

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

The following fields are considered multi-valued fields:

• Affects version/s
• Attachments
• Available target statuses
• Available transitions
• Component/s
• Component/s leads
• Fix version/s
• Labels
• Keys of linked issues
• Keys of sub-tasks
• Watchers
• Custom fields
  • Select List (Multiple choice)
  • Checkboxes
  • Labels
  • User picker (multiple users)
  • Group picker (multiple groups)
  • Version picker (multiple versions)

Examples

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

toStringList(%{issue.versions}) none in toStringList(%{issue.fixVersions})

 %{issue.labels} any in ["Backend", "Frontend"] 

toStringList(%{issue.labels}) any in ["Backend", "Frontend"]

In JWT DC, some case-ignoring operators are available (for details please see the respective part in the description of JWT DC's Logical mode). They are not available in JWT CLoud.

As a work around you can use the functions toUpperCase() / toLowerCase() for both operands and use the respective case sensitive operator. If an operand is a list, it first has to be converted to a text first using toString().

Examples

"HELLO" =~ "Hello"

toUpperCase("HELLO") = toUpperCase("Hello")

%{issue.labels} ~~ ["Backend","Database"]

toStringList(toLowerCase(%issue.labels})) ~ toStringList(toLowerCase(toString(["Backend","Database"])))