Versions Compared

Key

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

...

Values returned when reading virtual fields

Fields which belongs to the issue

Field nameField CodeTypeValue returned when cast to stringExamples
Summary
%{issue.summary}
Text stringIssue summary.-
Description
%{issue.description}
Text stringIssue description.-
Assignee
%{issue.assignee}
UserThe name of the user who has the issue assigned.albert.einstein
Assignee's full name
%{issue.assignee.fullName}
Text stringName and surname of the user who currently has the issue assignedAlbert Einstein
Assignee's email
%{issue.assignee.email}
Text stringEmail address of the user who currently has the issue assignedalbert.einstein@yahoo.com
Reporter
%{issue.reporter}
UserThe name of the user who reported the issue. This field is editable, while Creator field isn't.albert.einstein
Reporter's full name
%{issue.reporter.fullName}
Text stringName and surname of the user who created the issueAlbert Einstein
Reporter's email
%{issue.reporter.email}
Text stringEmail address of the user who created the issuealbert.einstein@yahoo.com
Creator
%{issue.creator}
UserUser name of the user who actually creates the issue in JIRA. This field, unlike Reporter, can't be edited.richard.feynman
Creator's full name
%{issue.creator.fullName}
Text stringName and surname of the user who actually created the issue in JIRARichard Feynman
Creator's email
%{issue.creator.email}
Text stringEmail address of the user who actually created the issue in JIRArichard.feynman@gmail.com
Current user
%{issue.currentUser}
UserName of the user who is executing the transition.isaac.newton
Current user's full name
%{issue.currentUserFullName}
Text stringName and surname of the user who is executing the transition.Isaac Newton
Current user's email
%{issue.currentUserEmail}
Text stringEmail address of the user who leads the project the issue belongs to.albert.einstein@yahoo.com, isaac.newton@gmail.com
Current date and time
%{issue.currentDateTime}
Date and TimeCurrent date and time of JIRA server's clock. When cast to string format defined at jira.date.time.picker.java.format is used.19/Mar/14 1:38 PM for jira.date.time.picker.java.format = dd/MMM/yy h:mm a

Date and time of creation
%{issue.created}
Date and timeDate and time when issue has been created. When cast to string format defined at jira.date.time.picker.java.format is used.19/Mar/14 1:38 PM for jira.date.time.picker.java.format = dd/MMM/yy h:mm a


Date and time of last update
%{issue.updated}
Date and timeDate and time of the most recent issue update. When cast to string format defined at jira.date.time.picker.java.format is used.19/Mar/14 1:38 PM for jira.date.time.picker.java.format = dd/MMM/yy h:mm a
Date and time of latest status change
%{issue.lastStatusChange}
Date and timeDate and time of the most recent status change in the issue. When cast to string format defined at jira.date.time.picker.java.format is used.19/Mar/14 1:38 PM for jira.date.time.picker.java.format = dd/MMM/yy h:mm a

Useful to find out for how much time is the issue in current status using expression: {00057} - {000158}, where {00057} = Current date and time and {000158} is Date and time of latest status change.


Due date
%{issue.dueDate}
DateField that can store a date with no time part, and is used to schedule issues. When cast to string format defined at jira.date.time.picker.java.format is used.19/Mar/14 for jira.date.time.picker.java.format = dd/MMM/yy h:mm a, since this field doesn't store time part.
Date and time of resolution
%{issue.resolutionDate}
Date and timeDate and time of the most recent update of field Resolution. When cast to string format defined at jira.date.time.picker.java.format is used.19/Mar/14 1:38 PM for jira.date.time.picker.java.format = dd/MMM/yy h:mm a
Priority
%{issue.priority}
PriorityName of the priority in Default language configured in the JIRA instanceBlocker
Critical
Major
Original estimate (minutes)
%{issue.originalEstimate}
NumberTime originally estimated for the issue expressed in minutes. It's a real number, so it may have a non-zero fractional part.-
Remaining estimate (minutes)
%{issue.estimate}
NumberRemaining time estimated for the issue expressed in minutes. It's a real number, so it may have a non-zero fractional part.-
Total time spent (minutes)
%{issue.timeSpent}
NumberWork time currently spent at the issue expressed in minutes. It's a real number, so it may have a non-zero fractional part.-
Work logged in transition (minutes)
%{issue.transition.worklog}
NumberNumber of minutes logged in current transition screen.This field can be used to enforce logging some time in transition screen.


Components
%{issue.component}
ComponentsComma separated list of component namesWeb Site, Authenticator, Statistics
Components leaders
%{issue.component.leads}
Multi userComma separated list of user namesalbert.einstein@yahoo.com, richard.feynman@gmail.com
Fixed versions
%{issue.fixVersion}
VersionsComma separated list of fixed versions1.0, 2.0, 2.1
Fixed versions with details
%{issue.fixVersion.details}
Text stringA text with a line for each fixed versions. Each line contains the following information separated by characters '#': name of version, description, release date and archive situation1.0 # First release # RELEASED ON 28/Mar/14 12:00 AM # ARCHIVED
Number of fixed versions
%{issue.fixVersion.count}
NumberNumber of fixed versions in current issue.-
Affected versions
%{issue.version}
VersionsComma separated list of fixed versions1.0, 2.0, 2.1
Affected versions with details
%{issue.version.details}
Text stringA text with a line for each affected versions. Each line contains the following information separated by characters '#': name of version, description, release date and archive situation1.0 # First release # RELEASED ON 28/Mar/14 12:00 AM # ARCHIVED
Number of affected versions
%{issue.version.count}
NumberNumber of affected versions in current issue.-
Number of votes received
%{issue.votes}
NumberNumber of votes received by the issue.-
Keys of subtasks
%{issue.subtasks}
Text stringComma separated list of issue keys.CRM-23, CRM-26, CRM-31
Number of subtasks
%{issue.subtasks.count}
NumberNumber of subtasks of current issue.-
Keys of linked issues
%{issue.linkedIssues}
Text stringComma separated list of issue keys.CRM-13, HR-12, SDESK-45
Number of linked issues
%{issue.linkedIssues.count}
NumberNumber of issues linked to current issue.-
Environment
%{issue.environment}
StringField to describe the environment where the issue has occurred.-
Attachments
%{issue.attachment}
AttachmentsComma separated list of file names of all files attached to the issue.file1.txt, readme.pdf, screenshot.png

Number of attachments
%{issue.attachment.count}
NumberNumber of files attached to current issue.-
Labels
%{issue.labels}
LabelsBlank separated list with all the labels of the issue.web customer java mobile
Number of labels
%{issue.labels.count}
NumberNumber of labels in current issue.-
Issue key
%{issue.key}
Text stringIssue keyCRM-25
HR-52
SDESK-1
Issue type
%{issue.issueType}
Issue typeName of issue's Issue Type in Jira's default languageBug
Improvement
New Feature
Task


Issue status
%{issue.status}
Issue statusName of current status of the issue in Jira's default language.Open
In Progress
Resolved
Issue status category

%{issue.statusCategory}
Status categoryName of the category in Jira's default language.To Do
In Progress
Done
Previous issue status

%{issue.status.previous}
Issue statusName of the status the issue was just before current one. The name is shown in Jira's default language.Open
In Progress
Closed
Previous issue status category
%{issue.statusCategory.previous}
Status categoryName of the category of the status the issue was just before current one. The name is shown in Jira's default language.To Do
In Progress
Done
Available transitions

%{issue.transitions.achievable}
Text stringA comma separated list with the names of transitions with origin in current issue status.If current issue is in Open status of classic Jira workflow, then field Available transitions will return: Start Progress, Resolve Issue, Close Issue
Available target statuses

%{issue.status.achievable}
Text stringA comma separated list with the names of target status of those transitions with origin in current issue status.If current issue is in Open status of classic Jira workflow, then field Available target statuses will return: In Progress, Resolved, Closed
Resolution
%{issue.resolution}
ResolutionThe name of the resolution currently set at the issue, or empty string if Resolution is not set. The name of the resolution is shown in Jira's default language.Resolved
Won't fix
Cancelled
Security level
%{issue.securityLevel}
Security levelName of the security level the issue currently has.Classified
Last comment
%{issue.lastComment}
Text stringLast comment entered in the issue.-
Last comment's visibility restriction
%{issue.lastComment.visibility}
Text string

Name of a group or project role the visibility of the last comment entered in the issue is restricted to. If no restriction is applied to the comment, this field is returns an empty string. For Service Desk's special Internal visibility restriction, string "Internal" is returned. This field can be used to check visibility restriction of field entered in transition when it exists.

When using a post-function for setting this field in order to set visibility restrictions over the comment entered in the transition screen, always insert the post-function after post-function "Add a comment to an issue if one is entered during a transition.", like in this example:

-
Last commenter
(since version 2.1.33)
%{issue.lastComment.author}
UserName of the user who entered the last comment in the issue.galileo.galilei
Transition's comment
%{issue.transition.comment}
Text stringComment entered in transition screen. This field can be used to make comment mandatory in transition screen, or to validate the content of comment entered in a transition.-
Watchers
%{issue.watcher}
Multi-userComma separated list of user names of current watchers of the issue.albert.einstein, richard.feynman, galileo.galilei
Project key
%{issue.project.key}
Text stringProject Key of the project the issue belongs to.CRM, HR, SDESK
Project name
%{issue.project.name}
Text stringName of the project the issue belongs to.Customer Relationship Management
Project description
%{issue.project.description}
Text stringField Description of the project the issue belongs to.-
Project URL
%{issue.project.url}
Text stringField URL of the project belongs to.https://www.decadis.de
Project category
%{issue.project.category}
Text stringName of the Category of the project the issue belongs to.-
Project leader
%{issue.project.lead}
UserName of the user who leads the project the issue belongs to.galileo.galilei
Project leader's full name
%{issue.project.leadFullName}
Text stringName and surname of the user who leads the project the issue belongs to.Galileo Galilei
Project leader's email
%{issue.project.leadEmail}
Text stringEmail address of the user who leads the project the issue belongs to.galileo.galilei@me.com
Rest of issues in the project
%{issue.remainingIssuesInProject}
Text stringComma separated list of issue keys in the project except current issue's key.CRM-1, CRM-2, CRM-3, CRM-4
Workflow scheme
%{issue.workflowScheme}
Text stringThe name of the workflow scheme of the project current issue belongs to.-
JIRA base URL
%{issue.baseUrl}
Text stringReturns the base URL of current JIRA instance.-
Sprint ID
%{issue.sprintId}
Text stringThe internal ID for the sprint of current issue. This value can be used for setting field Sprint in other issues.-
Sprint Start Date
%{issue.sprintStartDate}
DateSprint's start date.-
Sprint End Date
%{issue.sprintEndDate}
DateSprint's end date.-

For every virtual and custom field in a sub-task, there is also another virtual field representing the same field in its parent issue, making it very easy to read and write parent's issue fields.

Fields which belongs to the project

Project key
%{project.key}
Text stringKey of the project from the event.CRM, HR, SDESK
Project name
%{project.name}
Text stringName of the project from the event.Customer Relationship Management
Project description
%{project.description}
Text stringField Description of the project from the event.-
Project URL
%{project.url}
Text stringField URL of the project from the event.https://www.decadis.de
Project category
%{project.category}
Text stringName of the Category of the project from the event.-
Project leader
%{project.lead}
UserName of the user who leads the project from the event.galileo.galilei
Project leader's full name
%{project.leadFullName}
Text stringName and surname of the user who leads the project from the event.Galileo Galilei
Project leader's email
%{project.leadEmail}
Text stringEmail address of the user who leads the project from the event.galileo.galilei@me.com


Fields which belongs to the component

Component id
%{component.id}
Text stringId of the component from the event.10000
Component name
%{component.name}
Text stringName of the component from the event.Customer Relationship Management Component
Component description
%{component.description}
Text stringField Description of the component from the event.-
Component lead
%{component.lead}
Text stringName of the user who leads the component from the event.galileo.galilei
Component default assignee
%{component.defaultAssignee}
Text stringName of the user who is the default assignee of the component from the event.galileo.galilei


Fields which belongs to the version

Version id
%{version.id}
Text stringId of the version from the event.10000
Version name
%{version.name}
Text stringName of the version from the event.Customer Relationship Management Component
Version description
%{version.description}
Text stringField Description of the version from the event.-
Version archived
%{version.archived}
Text stringArchived status of the version from the event.galileo.galilei
Version released
%{version.released}
Text stringReleased status of the version from the event.galileo.galilei
Version start date%{version.startDate}Text stringStart date of the version from the event.
Version release date%{version.releaseDate}Text stringRelease date of the version from the event.
Version project%{version.project}Text stringProject key of the version from the event.
Version project id%{version.projectId}Text stringProject id of the version from the event.
Version sequence%{version.sequence}Text stringSequence of the version from the event.