On this page |
The JWT expression parser is very powerful when it come to composing texts. This page contains a comprehensive overview of all related information. |
%{...}
), texts need to be written in double quotes, e.g., "This is a text""This is" + " a text." = "This is a text."
.\
" . This character can precede any of the following characters: ",
\, n, r, t, f and b in order to invoke an alternative interpretation. e.g. \n for a linefeed.If you want to introduce a double quote in a text expression you should precede it with escape character |
Text field values can be inserted into expressions using field codes in the format %{...somefield}, or %{...somefield.i} for referencing concrete levels in cascading select fields (i = 0 for base level).
For checking if a field has a value you can use For a concrete level in a Cascading Select or Multi-Cascading Select field, you should use |
Any field type has a text value, so you can also use%{...somefield} to insert text values of fields of type Number (which includes Date and Date-Time values). Read more about Data types (JWT expressions). |
Input | Output |
---|---|
%{"Hello" + " " + "world" + "."} | Hello world. |
%{trim(%{issue.summary})} | Summary of an issue without leading and trailing blanks |
%{issue.description} \nLAST USER: %{toUpperCase(%{system.currentUser})} | Description of an issue and a new line with string "LAST USER: " and the name of current user in upper case. |