Page History

Versions Compared

Key

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

UI Text Box

size	medium
type	info

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. This means for example, that 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.

NEW screenshots

Multiple available parsing modes	Pre-configured parsing mode

Available parsing modes

Page properties report

headings	Short description, Supported elements, Output
cql	label = "parsing_mode" and space = currentSpace() and ancestor = currentContent()

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

UI Text Box

type	tip

Logical

Field codes

Parser Functions

Status

subtle	true
title	boolean

Code Block

language	bash
title	Check if the assignee is equals the reporter
linenumbers	true

{trigger.issue.assignee} = {trigger.issue.reporter}

Issue List

Field codes

Parser Functions

Statussubtletruetitleissue LISTString List

Field codes

Parser Functions

StatussubtletruetitleTEXT LISTMixed

Field codes

Parser Functions written in three curly braces

Status

subtle	true
title	text

UI Text Box

type	tip

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

Additionally, you can directly transform a field value to text using the following syntax: %{...somefield}

UI Expand

title	Parsing modes overview

ModeSupported featuresReturn typeExampleBasicField codes

Status

subtle	true
title	text

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

Code Block

language	bash
title	simple text using a field code to read the summary
linenumbers	true

This is the issue summary: %{trigger.issue.summary}

Advanced

Field codes

Parser Functions

Status

subtle	true
title	text

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

language	bash
title	Advanced expression to read the issue summary and use a function to get the assignee mail address
linenumbers	true

This is the issue summary:&quot; + %{trigger.issue.summary} + &quot; and the assignee mail is: &quot; + userEmail(%{trigger.issue.assignee})

Math/date-time

Field codes

Parser Functions

Status

subtle	true
title	number

Status

subtle	true
title	date

Status

subtle	true
title	date_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

language	bash
title	Time to resolve the issue
linenumbers	true

{trigger.issue.resolutionDate} - {trigger.issue.createdDate}

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

The text to be parsed will be automatically rewritten as a string 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.

Page properties

hidden	true

Tech review

Status

title	todo

Style guide

Status

title	todo

Status

title	todo

Status

colour	Yellow
title	Ready for review

Status

colour	Green
title	done

Status

colour	Red
title	flagged

Content

Space Tools

Versions Compared

Old Version 16

New Version 17

Key

Available parsing modes