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 parser modes, time macros etc. This page gives an overview of what is mapped how from.
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 |
---|---|---|---|
General mode | The whole parser expression (which has been migrated like described on this and the subsequent pages) has to be enclosed by %{ } | ||
General mode | The whole parser expression (which has been migrated like described on this and the subsequent pages) has to be enclosed by %{ } | ||
General mode | The whole parser expression (which has been migrated like described on this and the subsequent pages has to be enclosed by %{ } | ||
General mode | The whole parser expression (which has been migrated like described on this and the subsequent pages) has to be enclosed by %{ } | ||
General mode | To be verified: Should work with %{issuesFromJQL("<server parser expression>")} Double quotes within the server parser expression have to be replaced by single quotes | ||
General mode | Replace {{{ and }}} by %{ and } |
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.
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.
JWT DC offers Time Macros for accessing date and time values like {SUNDAY} for the number of this day in the week (=7). The notion is a "macro", i.e. those keywords are enclosed in {}. In the JWTCloud expression parser, they are noted as constants without curly brackets.
JWT DC | Mapping | JWT Cloud |
---|---|---|
{SECOND} {MINUTE} {HOUR} {DAY} {WEEK} {MONTH} {YEAR} | SECOND MINUTE HOUR DAY WEEK MONTH YEAR | |
{SUNDAY} {MONDAY} {TUESDAY} {WEDNESDAY} {THURSDAY} {FRIDAY} {SATURDAY} | SUNDAY MONDAY TUESDAY WEDNESDAY THURSDAY FRIDAY SATURDAY | |
{JANUARY} {FEBRUARY} {MARCH} {APRIL} {MAY} {JUNE} {JULY} {AUGUST} {SEPTEMBER} {OCTOBER} {NOVEMBER} {DECEMBER} | JANUARY FEBRUARY MARCH APRIL MAY JUNE JULY AUGUST SEPTEMBER OCTOBER NOVEMBER DECEMBER |
The JWT DC expression parser offers a couple of time zones which can be used as time zone parameter for the parser functions described in Dates, times and time zones.
tbd: List the respective time zones (hm, really all?); maybe mention that "SERVER_LOCAL" will be implemented. And find a nice wording for "In the cloud environment we don't have something like in "Server", so those constants (which means "SERVER_LOCAL") are not provided as language. Nor does USER_LANG exist in the cloud parser. (only RUN_AS_LANG is valid which also exists in the server)"
JWT DC | Mapping | JWT Cloud |
---|---|---|
LOCAL | - | |
RUN_AS_LOCAL | RUN_AS_LOCAL | |
SERVER_LOCAL | - |
tbd: List the respective languages (hm, really all?); maybe mention that "SERVER_LANG" willbe implemented. And find a nice wording for "In the cloud environment we don't have something like in "Server", so those constants (which means "SERVER_LANBG") are not provided as language. Nor does USER_LANG exist in the cloud parser. (only RUN_AS_LANG is valid which also exists in the server)"
JWT DC | Mapping | JWT Cloud |
---|---|---|
RUN_AS_LANG | RUN_AS_LANG | |
SERVER_LANG | - | |
USER_LANG | - |
If you still have questions, feel free to refer to our support team.