Get started

Use case library

JWT expression editor

JWT expression parser functions

JWT remote actions

Cloud migration hub

Additional product info

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 27 Next »

On this page


Field codes

Virtual fields


Those fields acquire numeric codes from 0 to 9999.

Field name serverField code server (context "issue")Field code server (context "parent")Field name cloudField code cloud (context = "issue" "parent" or "seed")MapNotes
Last comment's visibility restriction

%{issue.lastComment.visibility}

00130

%{parent.lastComment.visibility}

00132

 %{context.labels}(error)
Summary

%{issue.summary}

00000

%{parent.summary}

00029

Summary%{context.summary}(tick)
Assignee's full name

%{issue.assignee.displayName}
%{issue.assignee.fullName}

00002

%{parent.assignee.displayName}

%{parent.assignee.fullName}

00032

Assignee's full name%{context.assignee.displayName}(tick)
Description%{issue.description}
00001

%{parent.description}

00030

Description%{context.description}(tick)
Reporter's full name

%{issue.reporter.displayName}

%{issue.reporter.fullName}

00005

%{parent.reporter.displayName}

%{parent.reporter.fullName}

00035

Reporter's full name%{context.reporter.displayName}(tick)
Creator's full name

%{issue.creator.displayName}

%{issue.creator.fullName}

%{parent.creator.displayName}

%{parent.creator.fullName}

00152

Creator's full name%{context.creator.displayName}(tick)
Due date

%{issue.dueDate}

00012

%{parent.dueDate}

00039

Due date%{context.dueDate}(tick)
Issue type

%{issue.issueType}

00014

%{parent.issueType}

00040

Issue type%{context.issueType}(tick)
Issue key

%{issue.key}

00015

%{parent.key}

00041

Issue key%{context.key}(tick)
Issue status

%{issue.status}

00016

%{parent.status}

00042

Issue status%{context.status}(tick)
Priority

%{issue.priority}

00017

%{parent.priority}

00043

Priority%{context.priority}(tick)
Remaining estimate (minutes)

%{issue.remainingEstimate}

%{issue.estimate}

00024

%{parent.remainingEstimate}

%{parent.estimate}

00044

Remaining estimate (minutes)%{context.remainingEstimate}(tick)
Total time spent (minutes)

%{issue.timeSpent}

00025

%{parent.timeSpent}

00045

Total time spent (minutes)%{context.timeSpent}(tick)
Number of votes received

%{issue.votes}

00026

%{parent.votes}

00046

Number of votes received%{context.votes}(tick)
Resolution

%{issue.resolution}

00028

%{parent.resolution}

00048

Resolution%{context.resolution}(tick)
Original estimate (minutes)

%{issue.originalEstimate}

00068

%{parent.originalEstimate}

00069

Original estimate (minutes)%{context.originalEstimate}(tick)
Environment

%{issue.environment}

00070

%{parent.environment}

00082

Environment%{context.environment}(tick)
Attachments

%{issue.attachments}

%{issue.attachment}

00071

%{parent.attachments}

%{parent.attachment}

00083

Attachments%{context.attachments}(tick)
Number of attachments

%{issue.attachments.count}

%{issue.attachment.count}

%{issue.attachments.length}

00073

%{parent.attachments.count}

%{parent.attachment.count}

%{parent.attachments.length}

00085

Number of attachments%{context.attachments.length}(tick)
Fix version/s

%{issue.fixVersions}

%{issue.fixVersion}

00074

%{parent.fixVersions}

%{parent.fixVersion}

00086

Fix version/s%{context.fixVersions}(tick)
Number of fix version/s

%{issue.fixVersions.count}

%{issue.fixVersion.count}

%{issue.fixVersions.length}

00076

%{parent.fixVersions.count}

%{parent.fixVersion.count}

%{parent.fixVersions.length}

00088

Number of fix version/s%{context.fixVersions.length}(tick)
Affects version/s

%{issue.versions}

%{issue.version}

00077

%{parent.versions}

%{parent.version}

00089

Affects version/s%{context.versions}(tick)
Number of affects version/s

%{issue.versions.count}

%{issue.version.count}

%{issue.versions.length}

00079

%{parent.versions.count}

%{parent.version.count}

%{parent.versions.length}

00091

Number of affects version/s%{context.versions.length}(tick)
Component/s

%{issue.components}

%{issue.component}

00094

%{parent.components}

%{parent.component}

00095

Component/s%{context.components}(tick)
Number of sub-tasks

%{issue.subtasks.count}

%{issue.subtasks.length}

00027

%{parent.subtasks.length}

%{parent.subtasks.count}

00047

Number of sub-tasks%{context.subtasks.length}(tick)
Keys of linked issues

%{issue.links}

%{issue.linkedIssues}

00098

%{parent.linkedIssues}

%{parent.links}

00100

Keys of linked issues%{context.links}(tick)
Number of linked issues

%{issue.links.count}

%{issue.links.length}

%{issue.linkedIssues.count}

%{issue.linkedIssues.length}

00099

%{parent.linkedIssues.length}

%{parent.linkedIssues.count}

%{parent.links.count}

%{parent.links.length}

00101

Number of linked issues%{context.links.count}(tick)
Security level

%{issue.securityLevel}

00103

%{parent.securityLevel}

00104

Security level%{context.securityLevel}(tick)
Last comment

%{issue.lastComment}

00109

%{parent.lastComment}

00110

Last comment%{context.lastComment}(tick)
Previous issue status

%{issue.status.previous}

00138

%{parent.status.previous}

00139		Previous issue status%{context.status.previous}(tick)
Issue status category

%{issue.status.category}

%{issue.statusCategory}

00144

%{parent.status.category}

%{parent.statusCategory}

00145

Issue status category%{context.status.category}(tick)
Date and time of last status change

%{issue.lastStatusChange}

000158

%{parent.lastStatusChange}

00159

Date and time of latest status change%{context.lastStatusChange}(tick)
Last commenter

%{issue.lastComment.author}

00164

%{parent.lastComment.author}

00165		Last commenter%{issue.lastComment.author}(tick)
Sprint ID

%{issue.sprintId}

00185

%{parent.sprintId}

00185

Sprint ID%{issue.cf10020}(warning)On Cloud, it is called with the custom field code
Sprint start date

%{issue.sprintStartDate}

00186

%{parent.sprintStartDate}

00189

Sprint startDate
(error)
Sprint completion date

%{issue.sprintCompletionDate}

00188

%{parent.sprintCompletionDate}

00193

%{issue.sprintCompletionDate}

00191

Sprint completeDate
(error)
Labels

%{issue.labels}

00080

%{parent.labels}

00092

Labels%{context.labels}(tick)
Watchers%{issue.watcher}
00133

%{parent.watcher}

00134

Watchers%{issue.watcher}(warning)

JWT DC returns the name of the user, JWT Cloud returns the Atlassian account Id.

Component leads

%{issue.components.leads}

%{issue.component.leads}

00125

%{parent.components.leads}

%{parent.component.leads}

00126

Component/s leads%{context.components.leads}(warning)

JWT DC returns the name of the user, JWT Cloud returns the Atlassian account Id.

Reporter

%{issue.reporter}

00006

%{parent.reporter}

00034

Reporter%{context.reporter}(warning)

JWT DC returns the name of the user, JWT Cloud returns the Atlassian account Id.

Date and time of last update

%{issue.updated}

00011

%{parent.updated}

00056

Date and time of last update%{context.updated}(warning)

The date format of the returned value differs between JWT DC and JWT Cloud. JWT Cloud always returns a text in the form YYYY-MM-DD for dates and YYYY-MM-DDTH24:MM:SS.msTZ for datetime values. JWT DC returns a format depending on the settings of jira.date.time.picker.java.format.

Creator

%{issue.creator}

00148

%{parent.creator}

00151

Creator%{context.creator}(warning)

JWT DC returns the name of the user, JWT Cloud returns the Atlassian account Id.

Assignee's email

%{issue.assignee.email}

00004

%{parent.assignee.email}

00033

Assignee's email%{context.assignee.email}(tick)

In JWT Cloud, the email is only accessible if the respective user has set the visibility in the profile accordingly.

Assignee

%{issue.assignee}

00003

%{parent.assignee}

00031

Assignee%{context.assignee}(warning)

JWT DC returns the name of the user, JWT Cloud returns the Atlassian account Id.

Reporter's email

%{issue.reporter.email}

00007

%{parent.reporter.email}

00036

Reporter's email%{context.reporter.email}(tick)

In JWT Cloud, the email is only accessible if the respective user has set the visibility in the profile accordingly.

Date and time of creation

%{issue.created}

00009

%{parent.created}

00055

Date and time of creation%{context.created}(warning)

The date format of the returned value differs between JWT DC and JWT Cloud. JWT Cloud always returns a text in the form YYYY-MM-DD for dates and YYYY-MM-DDTH24:MM:SS.msTZ for datetime values. JWT DC returns a format depending on the settings of jira.date.time.picker.java.format.

Available target statuses

%{issue.status.achievable}

00192

%{parent.status.achievable}

00193

Available target statuses%{context.status.achievable}(tick)
Sprint end date

%{issue.sprintEndDate}

00187

%{issue.sprintEndDate}

00190

 
(error)
Remaining issues in project

%{issue.remainingIssuesInProject}

00102


 %{context.labels}(error)
Affects version/s with details

%{issue.versions.details}

%{issue.version.details}

00078

%{parent.versions.details}

%{parent.version.details}

00090

 
(error)

Project fields codes


Field code nameField code server (context "issue")Field code cloud (context = "issue" "parent" or "seed")MapNotes
Project key%{issue.project.key}

00018

%{issue.project.key}(tick)
Project name%{issue.project.name}

00019

%{issue.project.name}(tick)
Project ID%{issue.project.id}

00022

%{issue.project.id}(tick)
Project description%{issue.project.description}

00049

%{issue.project.description}(tick)
Project URL%{issue.project.url}

00050

%{issue.project.url}(tick)
Project category%{issue.project.category}

00051

%{issue.project.category}(tick)
Project lead's full name

%{issue.project.leadDisplayName}

%{issue.project.leadFullName}

00053

%{issue.project.leadDisplayName}(warning)
Project lead's email%{issue.project.leadEmail}

00054

%{issue.project.leadEmail}(tick)

In JWT Cloud, the email is only accessible if the respective user has set the visibility in the profile accordingly.

Project lead%{issue.project.lead}

00052

%{issue.project.lead}(warning)

JWT DC returns the name of the user, JWT Cloud returns the Atlassian account Id.

Temporary field codes (not available on JWTC)

Display list
Field code nameField code server (context "issue")Field code server (context "parent")Map
Ephemeral number 1

%{issue.temporaryNumber1}

00058

%{parent.temporaryNumber1}

00115

(error)
Ephemeral number 2

%{issue.temporaryNumber2}

00059

%{parent.temporaryNumber2}

00116

(error)
Ephemeral number 3

%{issue.temporaryNumber3}

00060

%{parent.temporaryNumber3}

00117

(error)
Ephemeral number 4

%{issue.temporaryNumber4}

00064

%{parent.temporaryNumber4}

00118

(error)
Ephemeral number 5

%{issue.temporaryNumber5}

00065

%{parent.temporaryNumber5}

00119

(error)
Ephemeral string 1

%{issue.temporaryText1}

00061

%{parent.temporaryText1}

00120

(error)
Ephemeral string 2

%{issue.temporaryText2}

00062

%{parent.temporaryText2}

00121

(error)
Ephemeral string 3

%{issue.temporaryText3}

00063

%{parent.temporaryText3}

00122

(error)
Ephemeral string 4

%{issue.temporaryText4}

00066

%{parent.temporaryText4}

00123

(error)
Ephemeral string 5

%{issue.temporaryText5}

00067

%{parent.temporaryText5}

00124

(error)

Virtual fields generated with other plugins

Display list

The following fields are generated by certain apps once they are installed in your Jira instance. Their field code is stored in the internal code, and it becomes available to be used once you install the plugin which belongs to.

You need to be a Jira administrator to install apps!

Field code nameThird-party pluginField code serverField code cloudMap
Tempo Account KeyTempo Timesheets

%{issue.tempoAccountKey}

00182

%{parent.tempoAccountKey}

00181

(error)(error)
Tempo Account NameTempo Timesheets

%{issue.tempoAccountName}

00180

%{parent.tempoAccountName}

00183

(error)(error)
Team NameAdvanced Roadmaps

%{issue.teamName}

00224

%{parent.teamName}

00225

(error)(error)
Customer request channelJira Software Management

%{issue.customerRequestChannel}

00196

%{parent.customerRequestChannel}

00197

(error)(error)
Customer request type name

Jira Software Management

%{issue.customerRequestTypeName}

00178

%{parent.customerRequestTypeName}

00179

(error)(error)

Supported custom field types

Display list
Custom field typeMapNotes
Group Picker (single group) ID 


Labels (Custom field) 

Please note, that the separator differs between JWT Server and JWT Cloud, in case there is more than one label. JWT DC shows a blamk space, in JWT Cloud it is a comma:

JWT DCJWT Cloud
label_1 label_2 label_3label_1,label_2,label_3
Project Picker (single project) 

Please note, that JWT DC returns the project name whereas JWT Cloud returns the project key. In order to receive the project name in JWT Cloud please use Project Picker (single project) - Name: %{issue.cfnnnnn.name}


Date Time Picker 

Please note, that the output format differs between JWT DC and JWT Cloud. JWT Cloud also shows milliseconds and offset.

JWT DCJWT Cloud
1993-02-02 13:001993-02-18T13:00:00.000+0000
Labels 

Please note, that the separator differs between JWT Server and JWT Cloud, in case there is more than one label. JWT DC shows a blamk space, in JWT Cloud it is a comma:

JWT DCJWT Cloud
label_1 label_2 label_3label_1,label_2,label_3
Select list (cascading) 

Please note, that the output format differs between JWT DC and JWT Cloud. JWT DC uses a hyphen ("-") as separator for parent and child value, JWT Cloud uses a comma (","):

JWT DCJWT Cloud
Parent value - Child valueParent value,Child value
User Picker (single user) 

JWT DC returns the name of the user, JWT Cloud returns the Atlassian account Id.

User Picker (multiple users) 

JWT DC returns the name of the user, JWT Cloud returns the Atlassian account Id.

Date Picker 
URL Field 
Rank 


Text field (single line) 


Number Field 
Select List (multiple choices) 
Select List (single choice) 
Text Field (multi-line) 


Version Picker (multiple versions) 


Checkboxes 
Radio Buttons 
Version Picker (single version) 


Multi-valued fields

Display list

The following fields are considered multi-valued fields:

  • Component/s
  • Component/s leads
  • Affects version/s
  • Fix version/s
  • Labels
  • Attachments
  • Watcher
  • Available transitions
  • Available target statuses
  • Recent attachments
  • Custom fields
    • Select List (Multiple choice)
    • Checkboxes
    • Labels
    • User picker (multiple users)
    • Group picker (multiple groups)
    • Version picker (multiple versions)
  • Issue Picker

The special thing about these fields is that they can be treated as lists when we have an expression that contains a logical operator.

For example, the following expression would work on server without the need of using the function toStringList(), but with other fields that are not multi-valued, like Summary, we would need to use it. 

%{issue.versions} in %{issue.fixVersions}
  • In case you try to use it as a string parameter in a function, that's not working. In that case you have to wrap in with  toStringList().
  • In case you compare such a field with a list built by "toStringList" where this StrigList is the left-hand operator, it's not working
  • fortunately that's not important for the transpilation as we are only transpiling correct JWT parser expressions

Available context

Parsing context

JWT parser always runs on a parsing context. The parsing context consists of 3 lists: issue list, string list and number list. The content of this lists are the elements of the context. There are 3 kind of elements: issues, strings and numbers. Elements in a list are ordered, thus each element in these list has an index associated (0, 1, 2, ...).

The index 0 makes reference to the current issue. The index 1 references the seed.

In Cloud, we don't have available the indexes after 1 (2,3,4...), and for the migration we will only migrate the index 0 from Server .

More details about the parsing context can be found here.

The following context are availble

  • issue
  • parent
  • seed

Fields available for the "system" context

Display list
Field code name
No content found.

If you still have questions, feel free to refer to our support team.