Page History
...
| Excerpt | ||||||
|---|---|---|---|---|---|---|
Automation Toolbox for Jira provides a set of special fields called virtual fields, making almost all properties all properties of issues, projects and users accessible users accessible to every feature in the app. Virtual fields may be read and written by read and written by Automation Toolbox for Jira in the same way ordinary custom fields are. Virtual fields and their associated field codes, were created to
In Automation In Automation Toolbox for Jira you can use virtual fields by searching for and picking their associated field codes in the dropdown menus provided wherever a parser expression can be inserted.
|
The notation listed below references each virtual field code, independent from it's context.
| Info | ||
|---|---|---|
| ||
The virtual fields represent the field / data part of the field code notation. %{trigger.parent.summary} %{system.currentUser} Some virtual fields are only available when used in the right context! |
...
| Field Name | Field code | Effect of Writing | Allowed String Values
| Allowed Numeric Values
| Examples | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Summary | %{issue.summary} | Sets issue Summary | text string trimmed to 255 characters | numbers are cast to string | - | ||||||||||||||||
| Description | %{issue.description} | Sets issue Description | unlimited text string | numbers are cast to string | - | ||||||||||||||||
| Assignee | %{issue.assignee} | Assigns the issue to a user | user name (not user's full name) | n/a | - | ||||||||||||||||
| Reporter | %{issue.reporter} | Updates issue Reporter to a different user | user name (not user's full name) | n/a | - | ||||||||||||||||
| Due date | %{issue.dueDate} | Sets issue's system field Due Date | date-time in format defined at jira.date.time.picker.java.format, or as in JQL (yyyy/MM/dd HH:mm, yyyy-MM-dd HH:mm, yyyy/MM/dd, yyyy-MM-dd, or relative to current time using "w" (weeks), "d" (days), "h" (hours) or "m" (minutes) | number of minutes relative to current time. | 2014-03-25 : date example2015-01-31 14:35 : date with time example- 4d 1h : 4 days and 1 hour before current time.2w, 3d, 4h, 5m : 2 weeks, 3 days, 4 hours and 5 minutes after current time. | ||||||||||||||||
| Priority | %{issue.priority} | Updates the issue Priority | name of a Priority (e.g., Blocker, Critical, Major,...) | (0 = highest priority, 1 = second highest,... n = lowest | |||||||||||||||||
| Original estimate (minutes) | %{issue.originalEstimate} | Sets original estimate | cast from string to number will be attempted | number of minutes | 30: sets Original estimate to 30 minutes.Original estimate (minutes) can be increased or decreased using expression parser with formulas like: {00024} + 60 for increasing remaining estimate in 1 hour, or {00024} - {10000} for decreasing remaining estimate by the amount of minutes stored in custom field with code {10000}. | ||||||||||||||||
| Remaining estimate (minutes) | %{issue.estimate} | Sets remaining estimate | cast from string to number will be attempted | number of minutes | 30 : sets Remaining estimate to 30 minutes.Remaining estimate (minutes) can be increased or decreased using expression parser with formulas like: {00024} + 60 for increasing remaining estimate in 1 hour, or {00024} - {10000} for decreasing remaining estimate by the amount of minutes stored in custom field with code {10000}. | ||||||||||||||||
| Total time spent (minutes) | %{issue.timeSpent} | Sets time spent.+ | cast from string to number will be attempted | number of minutes | 30 : sets Time spent to 30 minutes.Total time spent (minutes) can be increased or decreased using expression parser with formulas like: {00024} + 60 for increasing remaining estimate in 1 hour, or {00024} - {10000} for decreasing remaining estimate by the a mount of minutes stored in custom field with code {10000}. | ||||||||||||||||
| Add to time spent (minutes) | %{issue.addTimeSpent} | Adds a number of minutes to current value of field "Total time spent (minutes)" | cast from string to number will be attempted | number of minutes | 60 : increases time spent in 1 hour. | ||||||||||||||||
| Components | %{issue.component} | Sets issue Components | Comma separated list of component names. Prefixes + and - can be used to add or remove (check or uncheck) single values or set of values. | n/a | + Web Site, User Management : adds the components Web Site and User Management to current issue, provided they exist in the project.- Library A, Component B : removes the components Library A and Component B from current issue, provided they exist in the project. | ||||||||||||||||
| Fixed versions | %{issue.fixVersion} | Sets Fixed versions | Comma separated list of version names. Prefixes + and - can be used to add or remove (check or uncheck) single values or set of values. | numbers are cast to string | + 1.0, 1.1 : adds versions 1.0 and 1.1 to field Fixed versions.- 2.0, 2.2 : removes versions 2.0 and 2.2 from field Fixed versions. | ||||||||||||||||
| Affected versions | %{issue.version} | Sets Affected versions | Comma separated list of version names. Prefixes + and - can be used to add or remove (check or uncheck) single values or set of values. | numbers are cast to string | + 1.0, 1.1 : adds versions 1.0 and 1.1 to field Affected versions.- 2.0, 2.2 : removes versions 2.0 and 2.2 from field Affected versions. | ||||||||||||||||
| Environment | %{issue.environment} | Sets issue Environment | unlimited text string | numbers are cast to string | - | ||||||||||||||||
| Issue status | %{issue.status} | Will make the issue progress through the workflow to the written status, provided there is transition in the workflow from current status to the written status. It requires that all conditions and validations in the transition are satisfied. | name of a Status (e.g., Open, In Progress, Resolved,...) | n/a | Resolved : will search for a transition from current issue's status to Resolved status. If conditions are satisfied, it will try to execute the transition. Then if validators are satisfied in that transition are satisfied, it will be executed, resulting in moving issue to Resolved status. Every post-function in the executed transition is also executed. | ||||||||||||||||
| Resolution | %{issue.resolution} | Sets issue Resolution | name of issue Resolution (e.g., Fixed, Won't Fix, Duplicate, Incomplete,...) | n/a | - | ||||||||||||||||
| Labels | %{issue.labels} | Sets Labels | Comma separated list of labels. If label doesn't exist it is created. Prefixes + and - can be used to add or remove (check or uncheck) single values or set of values. | numbers are cast to string | + jira, plugin : adds labels "jira" and "plugin" to the issue.- scrum, web : removes labels "scrum" and "web" from the issue. | ||||||||||||||||
| Attachments (only new attachments will be added) | %{issue.attachmentsAdd} | Adds new attachments coming from another issue keeping current attachments. Rejects duplicated attachments. | Comma or blank separated list of issue keys whose attachments will be copied to current issue. | n/a | CMRCRM-1 : adds to current issue the attachments in issue CRM-1 except if attachments are already in current issue.CRM-2, HR-34, HR-50 : adds to current issue the attachments in issues CRM-2, HR-34 and HR-50 except if attachments are already in current issue. | ||||||||||||||||
| Attachments with details | %{issue.attachment.details} | Text string | Comma separated list of file names with its mime types and sizes in Kbytes, for every file attached to the issue. | file1.txt (text/plain, 5.14 KB), readme.pdf (application/pdf, 179.8 KB), screenshot.png (image/png, 5.449 KB) | |||||||||||||||||
| Security level | %{issue.securityLevel} | Sets issue Security Level | name of a Security Level | n/a | Public : sets security level to Public, provided this security level exists in the Security Scheme of the project.Reserved : sets security level to Reserved, provided this security level exists in the Security Scheme of the project. | ||||||||||||||||
| Last comment | %{issue.lastComment} | Updates the last comment added to the issue if it exists | unlimited text string Optionally parameter visibility can be added for setting comment visibility. To do it add : {visibility=visibility_value} at the end of the text. This parameter permits same values as "Last comment's visibility restriction". | numbers are cast to string | WARNING: When writing into this field, please add your writer action AFTER "Add Comment" action since otherwise updated comment will be the one before last, instead of the last one. | ||||||||||||||||
| Last comment's visibility restriction | %{issue.lastComment.visibility} | Updates the visibility of the last comment in the issue if it exists. Can be used to set the visibility of a comment introduced with virtual field New comment | name of a Project Role or name of a Group. In Jira Service Desk it also admits values public public and internal (without doble quotes), or alternatively jsd_public and jsd_internal to avoid name collision with existing project roles and user groups. | n/a | Developers : for setting visibility to project role or group with name Developers.jsd_internal : for setting JSD internal visibility.jira-developers : for setting visibility to "jira-developers" user group. | ||||||||||||||||
| Watchers | %{issue.watcher} | Sets watchers of an issue. Can be used to add or remove watchers to linked issues, sub-tasks or issues returned by JQL, but requires to use operator '+' and '-'. Also can be used to copy watchers between issues. | comma separated list of user names, group names or project roles names. Prefixes + and - can be used to add or remove single users or set of users. | n/a | albert, richard, john : sets 3 users as watchers replacing current ones.+ Developers, Administrators : adds every user in project roles or groups Developers and Administrators to current watchers.- Testers, Administrators, + albert, richard : removes users in project roles or groups Testers and Administrators and adds users albert and richard as watchers. |
...
