| Field name | Field code | Type | Output | Example output |
|---|
| Affects version/s | {issue.versions.id}
| | Comma separated list of version IDs | 10010,10020,10030 |
| Number of affects version/s | {issue.versions.length}
| | Number of affected versions in current issue | 3 |
| Assignee | %{issue.assignee}
| | The Atlassian account ID of the user who has the issue assigned | 10007 |
| Assignee's full name | %{issue.assignee.displayName}
| | Name and surname of the user who currently has the issue assigned | Albert Einstein |
| Assignee's email | %{issue.assignee.email}
| | Email address of the user who currently has the issue assigned | albert.einstein@yahoo.com |
| Attachments | %{issue.attachments}
| | Comma separated list of file names of all files attached to the issue | file1.txt,readme.pdf,screenshot.png |
| Number of attachments | {issue.attachments.length}
| | Number of files attached to current issue | 3 |
| Custom field | %{issue.cf10100}
| | Value of the given custom field as a string.
All custom fields will be notated like this %{issue.cfnnnnn} where nnnnn contains the Jira custom field id, that can be determined of the Jira custom field administration | Your customfield value
|
| Custom field | {issue.cf10133} | | Value of the given custom field as a number.
All custom fields will be notated like this {issue.cfnnnnn} where nnnnn contains the Jira custom field id, that can be determined of the Jira custom field administration | 47 |
| Component/s | %{issue.components}
| | Comma separated list of component names | Web Site,Authenticator,Statistics |
| Component/s ID | {issue.components.id}
| | Comma separated list of component IDs | 10010,10020,10030 |
| Component/s leads | %{issue.components.leads}
| | Comma separated list of the Atlassian account IDs of the leads for the components | 557068:145e0983-5707-439c-80e4-1160dd57g114,777068:145e0983-5707-439c-80e4-1160dd57x554,765428:168p0983-5987-444e-80e4-1160dd57g114 |
| Date and time of creation | %{issue.created}
| | Date and time when issue has been created. It's formatted as follows: YYYY-MM-DDTH24:MM:SS.msTZ | 2019-04-01T14:19:07.060+0200 |
| Creator | %{issue.creator}
| | Atlassian account ID of the user who actually creates the issue in JIRA | 765428:168p0983-5987-444e-80e4-1160dd57g114 |
| Creator's full name | %{issue.creator.displayName}
| | Name and surname of the user who actually created the issue in JIRA | Richard Feynman |
| Creator's email | %{issue.creator.email}
| | Email address of the user who actually created the issue in JIRA | richard.feynman@gmail.com |
| Description | %{issue.description}
| | Issue description | Take your Jira to the next level by using JWT for Jira Cloud |
| Due date | %{issue.dueDate}
| | Field that stores a date with no time part and is used to schedule issues. It's formatted as follows: YYYY-MM-DD | 2019-10-22 |
| Environment | %{issue.environment}
| | Field to describe the environment where the issue has occurred | Take your Jira to the next level by using JWT for Jira Cloud |
| Fix version/s | %{issue.fixVersions}
| | Comma separated list of fix version names | 1.0,2.0,2.1 |
| Fix version/s ID | {issue.fixVersions.id}
| | Comma separated list of fix versions IDs | 10010,10020,10030 |
| Number of fix version/s | {issue.fixVersions.length}
| | Number of fixed versions in current issue | 5 |
| Issue ID | {issue.id}
| | ID of the current issue | 10001 |
| Issue key | %{issue.key}
| | Issue key of the current issue | CRM-25 |
| Issue type | %{issue.issueType}
| | Name of issue's Issue Type in the user's language set in his profile | Improvement |
| Issue type ID | {issue.issueType.id}
| | ID of issue's Issue Type | 10056 |
| Labels | %{issue.labels}
| | Comma separated list with all the labels of the issue | web,customer,java,mobile |
| Number of labels | {issue.labels.length}
| | Number of labels in current issue | 4 |
| Last comment | %{issue.lastComment}
| | Last comment entered in the issue | Take your Jira to the next level by using JWT for Jira Cloud |
| Last commenter | %{issue.lastComment.author}
| | Atlassian account ID of the user who entered the last comment in the issue | 557068:145e0983-5707-439c-80e4-1160dd57g114 |
| Issue status | %{issue.status}
| | Name of current status of the issue in the user's language set in his profile | Open |
| Issue status ID | %{issue.status.id} | | ID of current status of the issue | 10100 |
Issue status category
| %{issue.status.category}
| | Name of the category in the user's language set in his profile | Done |
Previous issue status
| %{issue.status.previous}
| | Name of the status the issue was just before current one The name is shown in the user's language set in his profile | Closed |
| Keys of linked issues | %{issue.links}
| | Comma separated list of issue keys | CRM-13,HR-25,SD-12 |
| Number of linked issues | {issue.links.length}
| | Number of issues linked to current issue | 3 |
| Original estimate (minutes) | {issue.originalEstimate}
| | Time originally estimated for the issue expressed in minutes It's a real number, so it may have a non-zero fractional part | 360 |
| Remaining estimate (minutes) | {issue.remainingEstimate}
| | Remaining time estimated for the issue expressed in minutes It's a real number, so it may have a non-zero fractional part | 270 |
| Total time spent (minutes) | {issue.timeSpent}
| | Work time currently spent at the issue expressed in minutes It's a real number, so it may have a non-zero fractional part | 90 |
| Priority | %{issue.priority}
| | Name of the priority in the user's language set in his profile | Critical |
| Priority ID | {issue.priority.id}
| | ID of the priority the issue belongs to | 10010 |
| Project | %{issue.project}
| | Project Key of the project the issue belongs to | HR |
| Project ID | {issue.project.id}
| | Project ID of the project the issue belongs to | 10100 |
| Project key | %{issue.project.key}
| | Project Key of the project the issue belongs to (identically to Project, i.e %{issue.project}) | HR |
| Project name | %{issue.project.name}
| | Name of the project the issue belongs to | Customer Relationship Management |
| Project description | %{issue.project.description}
| | Field description of the project the issue belongs to | Take your Jira to the next level by using JWT for Jira Cloud |
| Project URL | %{issue.project.url}
| | Field URL of the project the issue belongs to | https://www.decadis.de/x |
| Project category | %{issue.project.category}
| | Name of the Category of the project the issue belongs to | Take your Jira to the next level by using JWT for Jira Cloud |
| Project lead | %{issue.project.lead}
| | Atlassian account ID of the user who leads the project the issue belongs to | 557068:145e0983-5707-439c-80e4-1160dd57g114 |
| Project lead's full name | %{issue.project.lead.displayName}
| | Name and surname of the user who leads the project the issue belongs to | Galileo Galilei |
| Project lead's email | %{issue.project.lead.email}
| | Email address of the user who leads the project the issue belongs to | galileo.galilei@me.com |
| Reporter | %{issue.reporter}
| | Atlassian account ID of the user who reported the issue | 557068:145e0983-5707-439c-80e4-1160dd57g114 |
| Reporter's full name | %{issue.reporter.displayName}
| | Name and surname of the user who created the issue | Albert Einstein |
| Reporter's email | %{issue.reporter.email}
| | Email address of the user who created the issue | albert.einstein@yahoo.com |
| Resolution | %{issue.resolution}
| | The name of the resolution currently set at the issue. The name of the resolution is shown in the user's language set in his profile | Won't fix
|
| Date and time of resolution | %{issue.resolutionDate}
| | Date and time of the most recent update of field Resolution. It's formatted as follows: YYYY-MM-DDTH24:MM:SS.msTZ | 2019-04-01T14:19:07.060+0200 |
| Security level | %{issue.securityLevel}
| | Name of the security level the issue currently has | Classified |
| Security level ID | {issue.securityLevel.id}
| | ID of the security level the issue currently has | 10001 |
| Keys of sub-tasks | %{issue.subtasks}
| | Comma separated list of issue keys | CRM-23,CRM-26,CRM-31 |
| Number of sub-tasks | {issue.subtasks.length}
| | Number of subtasks of current issue | 3 |
| Summary | %{issue.summary}
| | The issue summary | Take your Jira to the next level by using JWT for Jira Cloud |
Available transitions
| %{issue.transitions.achievable}
| | A comma separated list with the names of transitions with origin in current issue status | Start Progress,Resolve Issue,Close Issue
|
| Date and time of last update | %{issue.updated}
| | Date and time of the most recent issue update It's formatted as follows: YYYY-MM-DDTH24:MM:SS.msTZ | 2019-04-01T14:19:07.060+0200 |
| Number of votes received | {issue.votes}
| | Number of votes received by the issue | 5 |
| Date and time of latest status change | %{issue.lastStatusChange}
| | Date and time of the most recent status change in the issue. It's formatted as follows: YYYY-MM-DDTH24:MM:SS.msTZ | 2019-04-01T14:19:07.060+0200
|
| Watchers | %{issue.watcher}
| | Comma separated list of Atlassian account IDs of current watchers of the issue | 557068:145e0983-5707-439c-80e4-1160dd57g114,777068:145e0983-5707-439c-80e4-1160dd57x554 |
|
|
|
|
|
Overview
Field code notation
Only valid for sub-tasks.
no preceding % sign)
Readable fields