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.
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 | ||||
|---|---|---|---|---|---|---|---|
 | Replace the field codes by the ones provided in JWT Cloud, for details see Migrate field codes. | ||||||
| General mode | The whole parser expression (which has been migrated like described in Migrate field codes and Migrate JWT Parser functions) has to be enclosed by %{ } | |||||
| For differences between JWT DC and JWT Cloud logical mode, see Migrate logical parser expressions | ||||||
| General mode | The whole parser expression (which has been migrated like described in Migrate field codes and Migrate JWT Parser functions) has to be enclosed by %{ } | |||||
| General mode | The whole parser expression (which has been migrated like described in Migrate field codes and Migrate JWT Parser functions) has to be enclosed by %{ } | |||||
| General mode | The whole parser expression (which has been migrated like described in Migrate field codes and Migrate JWT Parser functions) has to be enclosed by %{ } | |||||
| General mode | The field codes which are used in the JQL query have to be migrated according to Migrate field codes. You have to concatenate them to the remaining JQL. Double quotes have to be replaced by single quotes. This expression must be surrounded by Example
| |||||
| General mode | Replace {{{ and }}} by %{ and } (and migrate the fields and functions as described here and on the subsequent pages) |
If you still have questions, feel free to refer to our support team.
