Get started

Use case library

JWT expression editor

JWT expression parser functions

JWT workflow functions

JWT remote actions

JWT automation rules

JWT calculated fields

JWT calendars

JWT properties

JWT JQL functions

Cloud migration hub

Additional product info

Versions Compared

Old Version 4

changes.mady.by.user Iheb Kharab

Saved on

compared with

New Version Current

changes.mady.by.user Iheb Kharab

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Page properties
hiddentrue


Tech review

Status
colourGreen
titledone

Style guide

Status
colourGreen
titledone

Page status

Status
colourGreen
titledone

Status
titletodo
Status
colourYellow
titleReady for review
Status
colourGreen
titledone
Status
colourRed
titleflagged



Excerpt


UI Text Box
sizemedium
typeinfo

There are multiple parsing modes available in the expression parser. The two most commonly used parsing modes are:

  • Basic: with this simple parsing mode you can write free text and insert field codes with format %{...somefield} or %{...somefield.i} anywhere in your text. These field codes will be replaced at runtime with the corresponding field values of the issue currently being processed.
    • Advanced: with this parsing mode we can do much more complex text composition thanks to the usage of functions for replacing substrings, changing cases, reading fields in linked issues, sub-tasks, JQL selected issues, and much more. It requires the text to be parsed to be written as a string expression respecting the parser syntax.
    You can easily switch between parsing modes. The available modes depend on the context!

    A parsing mode determines how the JWT expression parser interprets an expression. 

    The available parsing modes depend on the context you are using the expression in. As an example, only the Logical mode is available if you configure a conditionalexecution in a workflow post function or that you can only use the Numeric mode if you want to set a number field using a parser expression.

    Image Added


    Available parsing modes

    Page properties report
    firstcolumnMode
    headingsIcon, Short description, Supported elements, Output
    cqllabel = "parsing_mode" and space = currentSpace() and ancestor = currentContent()

    UI Text Box
    typetip

    Most functions will accept string text values so casting values to string text is a very powerful function. 

    Details can be found below in the converting data types section! Additionally, you can directly transform a field value to text using the following syntax: %{...somefield}

    UI Expand
    titleParsing modes overview
    ModeSupported featuresReturn typeExample
    BasicField codes
    Status
    subtletrue
    titletext

    The basic parsing mode supports the usage of field codes. Field codes can be used to access issue field values.

    Code Block
    languagebash
    titlesimple text using a field code to read the summary
    linenumberstrue
    This is the issue summary: %{trigger.issue.summary}
    Advanced

    Field codes

    Parser Functions

    Status
    subtletrue
    titletext

    The advanced parsing mode has a defined syntax that allows you to write functions to read and manipulate data from any issue in Jira. Field codes are supported as well as clear text, written in quotation marks.

    Code Block
    languagebash
    titleAdvanced expression to read the issue summary and use a function to get the assignee mail address
    linenumberstrue
    This is the issue summary:" + %{trigger.issue.summary} + " and the assignee mail is: " + userEmail(%{trigger.issue.assignee})
    Math/date-time

    Field codes

    Parser Functions

    Status
    subtletrue
    titlenumber
    Status
    subtletrue
    titledate
    Status
    subtletrue
    titledate_time

    The mathematical and date time parsing mode works like the advanced mode but expect a number as result instead of a string. The resulting number is used to updated numeric or date time fields. In case of date or date time fields the number will be cast to a date.

    Code Block
    languagebash
    titleTime to resolve the issue
    linenumberstrue
    {trigger.issue.resolutionDate} - {trigger.issue.createdDate}
    Logical

    Field codes

    Parser Functions

    Status
    subtletrue
    titleboolean

    The logical parsing mode works like the advanced parsing mode but expression result must return true or false.

    Code Block
    languagebash
    titleCheck if the assignee is equals the reporter
    linenumberstrue
    {trigger.issue.assignee} = {trigger.issue.reporter}
    Issue List

    Field codes

    Parser Functions

    StatussubtletruetitletextString List

    Field codes

    Parser Functions

    StatussubtletruecolourYellowtitletextMixed

    Field codes

    Parser Functions written in three curly braces

    Statussubtletruetitletext

    You can write your text in basic text mode, and then switch to advanced text mode using Automatic parsing mode converter.

    The text to be parsed will be automatically rewritten as a text expression. Now, you can simply make the modifications you require, making use of text formatting functions, or inserting math or time expressions where needed.

    To update issue fields the parsing result will be cast to the expected value e.g. a user name will be cast to a user to update a user field like the assignee field.


    Excerpt Include
    DECADIS:Contact support
    DECADIS:Contact support
    nopaneltrue