Summary
When customizing actionsoperations, you can set specific fields. The following indicates what fields are available for modification. For values, you can use text or Substitution variables or a combination of both. Open an issue if If you have a need for additional fields, raise a support request with our support team.. The general format for setting a field is .set. or .set.subtask. with the custom number as a prefix and the field name to be set as the postfix. Main issue fields are controlled by .set. and subtasks copied as a result of cloning the main issue are set using .set.subtask.
Field Name | Notes and Examples | |||
---|---|---|---|---|
summary |
| |||
description |
| |||
environment |
| |||
issuetype | # This can set subtask issue type only. See Clone properties for discussion of setting the project and issue type of the cloned issue.
| |||
priority |
| |||
Assignee |
| |||
Special Value | Example | |||
unassigned |
| |||
current user |
| |||
automatic_assignee |
| |||
project_lead |
| |||
reporter |
| |||
components |
| |||
labels |
It is recommended to include the required labels in the ignoreFields or fieldExcludes (refer to Clone properties) list, for them to behave as expected during Clone operations. | |||
security |
| |||
Special Value | Example | |||
Project default |
| |||
affectsVersions |
| |||
fixVersions |
| |||
duedate | # Format: d/MMM/yy - but any JIRA application property format should work
| |||
originalEstimate | # Time duration format - note, for ignoreField use, you will need to add timetracking as the field name to ignore
| |||
remainingEstimate | # Time duration format
To copy original estimate using substitution variable, use -
| |||
comment | # Custom comment can be added as a part of cloning operation
Example -
| |||
custom fields | # Note that blanks must be escaped in custom field names
|
...