Versions Compared

Old Version 41

changes.mady.by.user Pooja Gopalnaidu

Saved on

compared with

New Version 42

changes.mady.by.user Pooja Gopalnaidu

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Changes as per ticket JCPP-2356

...

When customizing actions, you may want to 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 you have a need for additional fields. 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

1.set.summary = Clone - %original_summary%

description

1.set.description = %original_description%

environment

1.set.environment = %original_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.

1.set.subtask.issuetype = Documentation subtask

1.set.subtask.issuetype = 19

priority

1.set.priority = 1

Assignee

1.set.assignee = bob

Special Value

Example

Notes

unassigned

1.set.assignee =

Assignee field must not appear on the UI, usually means you also need 1.set.ignoreFields = assignee

current user

1.set.assignee = %user_id%

The user ID of the logged in user.

automatic_assignee

1.set.assignee = %entry_automatic_assignee%

Assignee calculated from the new issues project, issue components, and the project configuration.project_lead

1.set.assignee = %entry_project_lead%Project lead associated with the new issue's project

reporter

1.set.reporter = bob

components

1.set.components = C1, C2

labels

1.set.labels = label1 label2

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

1.set.security = Developers

Special Value

ExampleFrom Version

Project default

1.set.security = %entry_project_default security%4.0

affectsVersions

1.set.affectsVersions =

fixVersions

1.set.fixVersions = V2, V1

duedate

# Format: d/MMM/yy - but any JIRA application property format should work

3.set.duedate = 13/Sep/17

originalEstimate

# Time duration format - note, for ignoreField use, you will need to add timetracking as the field name to ignore

1.set.originalEstimate = 3h 30m

remainingEstimate

# Time duration format 

1.plus.set.remainingEstimate = 3d

To copy original estimate using substitution variable, use -

1.plus.set.remainingEstimate = %parent_original_estimate%

Info

When remaining estimate is not set, the original estimate is considered as remaining estimate.

comment

# Custom comment can be added as a part of cloning operation

1.plus.set.comment = "<Any custom comment you may wish to add to the cloned issue>"

Example -

1.plus.set.comment = "The comments above belong to the parent issue"

custom fields

# Note that blanks must be escaped in custom field names

1.set.custom\ three = %original_assignee%

1.set.custom-multi-select = s2,s1, s3

1.set.custom-cascade-select = 1,A

1.set.customfield_10010 = test + %original_summary%

1.set.custom-date-type-field = %now%

If your project consists of custom fields, it is recommended to include them in the ignoreFields (refer to Clone properties) list, for them to behave as expected during Clone operations.