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 19 Next »

On this page


Field codes

Virtual fields


Those fields acquire numeric codes from 0 to 9999.

Field code nameField code server (context "issue")Number code server (issue)Field code server (context "parent")Number code server (parent)Field code cloud (context = "issue" "parent" or "seed")Number code cloudMapNotes
Last comment's visibility restriction

%{issue.lastComment.visibility}

00130

 

%{parent.lastComment.visibility}

00132

 %{context.labels} (error)
Summary

%{issue.summary}

00000

 

%{parent.summary}

00029

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

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

00002

 

%{parent.assignee.displayName}

%{parent.assignee.fullName}

00032

 %{context.assignee.displayName} (tick)
Description%{issue.description}
00001		 

%{parent.description}

00030

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

%{issue.reporter.displayName}

%{issue.reporter.fullName}

00005

 

%{parent.reporter.displayName}

%{parent.reporter.fullName}

00035

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

%{issue.creator.displayName}

%{issue.creator.fullName}		 

%{parent.creator.displayName}

%{parent.creator.fullName}

00152

 %{context.creator.displayName} (tick)
Due date

%{issue.dueDate}

00012

 

%{parent.dueDate}

00039

 %{context.dueDate} (tick)
Issue type

%{issue.issueType}

00014

 

%{parent.issueType}

00040

 %{context.issueType} (tick)
Issue key

%{issue.key}

00015

 

%{parent.key}

00041

 %{context.key} (tick)
Issue status

%{issue.status}

00016

 

%{parent.status}

00042

 %{context.status} (tick)
Priority

%{issue.priority}

00017

 

%{parent.priority}

00043

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

%{issue.remainingEstimate}

%{issue.estimate}

00024

 

%{parent.remainingEstimate}

%{parent.estimate}

00044

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

%{issue.timeSpent}

00025

 

%{parent.timeSpent}

00045

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

%{issue.votes}

00026

 

%{parent.votes}

00046

 %{context.votes} (tick)
Resolution

%{issue.resolution}

00028

 

%{parent.resolution}

00048

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

%{issue.originalEstimate}

00068

 

%{parent.originalEstimate}

00069

 %{context.originalEstimate} (tick)
Environment

%{issue.environment}

00070

 

%{parent.environment}

00082

 %{context.environment} (tick)
Attachments

%{issue.attachments}

%{issue.attachment}

00071

 

%{parent.attachments}

%{parent.attachment}

00083

 %{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

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

%{issue.fixVersions}

%{issue.fixVersion}

00074

 

%{parent.fixVersions}

%{parent.fixVersion}

00086

 %{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

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

%{issue.versions}

%{issue.version}

00077

 

%{parent.versions}

%{parent.version}

00089

 %{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

 %{context.versions.length} (tick)
Component/s

%{issue.components}

%{issue.component}

00094

 

%{parent.components}

%{parent.component}

00095

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

%{issue.subtasks.count}

%{issue.subtasks.length}

00027

 

%{parent.subtasks.length}

%{parent.subtasks.count}

00047

 %{context.subtasks.length} (tick)
Keys of linked issues

%{issue.links}

%{issue.linkedIssues}

00098

 

%{parent.linkedIssues}

%{parent.links}

00100

 %{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

 %{context.links.count} (tick)
Security level

%{issue.securityLevel}

00103

 

%{parent.securityLevel}

00104

 %{context.securityLevel} (tick)
Last comment

%{issue.lastComment}

00109		 

%{parent.lastComment}

00110

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

%{issue.status.previous}

00138

 

%{parent.status.previous}

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

%{issue.status.category}

%{issue.statusCategory}

00144

 

%{parent.status.category}

%{parent.statusCategory}

00145

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

%{issue.lastStatusChange}

000158

 

%{parent.lastStatusChange}

00159

 %{context.lastStatusChange} (tick)
Last commenter

%{issue.lastComment.author}

00164

 

%{parent.lastComment.author}

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

%{issue.sprintId}

00185

 

%{parent.sprintId}

00185

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

%{issue.sprintStartDate}

00186

 

%{parent.sprintStartDate}

00189

 
 (error)
Sprint completion date

%{issue.sprintCompletionDate}

00188

 

%{parent.sprintCompletionDate}

00193

%{issue.sprintCompletionDate}

00191

 
 (error)
Labels

%{issue.labels}

00080

 

%{parent.labels}

00092

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

%{parent.watcher}

00134

 %{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

 %{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

 %{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

 %{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

 %{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

 %{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

 %{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

 %{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

 %{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

 %{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.

Field codes for transition info (not available on JWTC)

Display list


Temporary field codes (not available on JWTC)

Display list

Virtual fields generated with other plugins

Display list

Supported custom field types

Display list

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

Fields only available in JWTX (information only)

Display list


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