Page History

Versions Compared

Key

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

Page properties

hidden	true

Tech review

Status

colour	Yellow
title	Ready for review

Style guide

Status

colour	Yellow
title	Ready for review

Status

title	todo

Status

colour	Yellow
title	Ready for review

Status

colour	Green
title	done

Status

colour	Red
title	flagged

Excerpt

UI Text Box

size	medium
type	info

A parsing mode determines how the JWT for Jira Cloud expression parser interprets an expression. The available parsing modes depend on the context in which you use the expression. This means for example, that only the Logical mode is available if you configure a conditionalexecution in a workflow post function.

Image Removed

Image Added

Available parsing modes

Page properties report

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

There are two parsing modes available in the expression parser:

General: you can write freetext, insert field codes or use functions anywhere in your text. Field codes will be replaced at runtime with the corresponding field values of the issue currently being processed. Using functions for replacing substrings, changing cases, reading fields in linked issues, sub-tasks, JQL selected issues, and much more we can do much more complex operations. It requires the text to be parsed to be written as a string expression respecting the parser syntax which is described below.

The available modes depend on the context!

Please be aware that besides the JWT for Jira Cloud expression parser you can choose to use Jira expressions as a parsing mode in every context.

Comments

UI Text Box

type	info

Comments can be added to all parsing modes. They serve as internal documentation for the expression and are ignored when evaluating the expression.

Parsing mode

Syntax

Examples

General

Only available when using expressions enclosed by %{}.

Starts with # and ends either at the end of the line or if the expression is closed by }

Code Block
List of issue keys for %{issue.key #choose an issue} is: %{subtasks() # and show all sub-tasks}

Code Block
%{# This example simply returns the number of linked issues using a JWT expression %{issue.links.length}}

Logical

It starts with # and ends at the end of the line

Code Block
%{issue.key} = "PRJ-42" # simple comparison with issue key

Code Block
# This example simply returns the number of linked issues using a JWT expression %{issue.links.length}

Jira expression

It starts with // and ends with the end of the line

Code Block
issue.key == 'PRJ-42' // simple comparison with issue key

Excerpt Include

	DECADIS:Contact support
	DECADIS:Contact support
nopanel	true

UI Expand

title	Parsing modes overview

ModeSupported featuresReturn typeExampleGeneral

Field codes

Parser Functions

Text with the following restriction: the following combination of characters has to be escaped by "\" when not being used as a field code field codes: %{ → \%\{

Status

subtle	true
title	text

The general parsing mode allows you to write functions to read and manipulate data from any issue in Jira. Field codes are supported as well as clear text.

Code Block

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

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

Functions as well as Field codes have to be enclosed by %{...}. When you are nesting functions, only one %{...} is necessary. Within functions, texts have to be written in quotation marks. Quotes (") within a quoted text have to be escaped (e.g. "This is a \"quoted\" text" will result in This is a "quoted" text).

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: " + %{issue.summary} + " and the assignee mail is: " + userEmail(%{issue.assignee.email})

Please be aware that the general mode always return a text. In case this is used as an input for a number (especially date) parameter or as an issue list, JWT for Jira Cloud cares internally for a correct conversion.

Code Block

language	bash
title	Use mathematical operations:: Time to resolve the issue
linenumbers	true

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

Code Block

language	bash
title	Working with issue lists: Getting the sub-tasks of an issue
linenumbers	true

%{subtasks()}

Code Block

language	bash
title	Nesting functions: Getting the number of the sub-tasks of an issue
linenumbers	true

%{count(subtasks())}

Code Block

language	bash
title	More complex example for a text which contains the current summary, the summary of the parent issue and the number of sub-tasks of the parent issue.
linenumbers	true

This is the issue summary: "%{issue.summary}" and that of the parent "%{parent.summary}". Issue %{parent.key} has %{count(subtasks(%{parent.key}))} sub-tasks.

Code Block

language	bash
title	An alternative expression, where the entire expression is written as one function, would be
linenumbers	true

%{"This is the issue summary: \"" + %{issue.summary} + "\" and that of the parent \"" + %{parent.summary} +"\". Issue " + %{parent.key} + " has "+count(subtasks(%{parent.key})) +" sub-tasks."}

UI Text Box

type	tip

The following combination of characters has to be escaped by "\" when not being used as a field code or function delimiter: %{ → \%\{

Content

Space Tools

Versions Compared

Old Version 13

New Version Current

Key

Available parsing modes

Comments