On this page
Parser
Modes
The parser in JWT server/DC offers a couple of different modes, which can be mapped to the modes provided by the JWT Cloud expression parser.
Server mode | Cloud mode | Notes
|
|---|---|---|
| General mode | The whole transpiled parser expression (described on this and the subsequent pages) has to be enclosed by %{ } | |
| General mode | The whole transpiled parser expression (described on this and the subsequent pages) has to be enclosed by %{ } | |
| General mode | The whole transpiled parser expression (described on this and the subsequent pages) has to be enclosed by %{ } | |
| General mode | The whole transpiled parser expression (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 } |
General remarks to Dates, times, and time zones:
Server | Cloud | Notes
|
|---|---|---|
{SECOND} {MINUTE} {HOUR} {DAY} {WEEK} {MONTH} {YEAR} | SECOND | MINUTE | HOUR | DAY | WEEK | MONTH | YEAR | The server notion is a "macro", i.e. those keywords are enclosed in {}. In the JWT for Jira Cloud expression parser, they are noted as constants without curly brackets. But for sure they have to appear within %{}. |
{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 | |
| SERVER_LANG USER_LANG | In the cloud environment we don't have something like in "Server", so those constants (which means "server language") 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) | |
| LOCAL SERVER_LOCAL USER_LOCAL | In the cloud environment, we don't have something like in "Server", so the LOCAL and SERVER_LOCAL constants (which both mean "server timezone") are not provided as time zones, nor is USER_LOCAL provided (only "RUN_AS_LOCAL" is valid which also exists in the server) |
If you still have questions, feel free to refer to our support team.
