Page Comparison

Subtask condition

create subtask

Ignore if original issue is a subtask

Option to take when original issue is a subtask. This applies when the original issue is a subtask:

• Create - continue to create the subtask, but, if the parent is a subtask, it will be created as a sibling subtask

• Ignore - do not create a subtask

Condition 1

See: How to use pattern matching conditioning

Condition 2

See: How to use pattern matching conditioning

Summary

Set issue summary field

Description

Set issue description field

Entry parent

create subtask

Parent of original issue

Since 5.0.

Project

create issue

Original project

Set project when creating issues

Issue type

Bug or Subtask

Set issue type

Priority

Parent's priority

Set priority

Reporter

Current user

Set priority

Assignee

Parent issue's assignee

Set assignee

Affected versions

Set affected versions from a comma separated list of version names

Fixed versions

Set fixed versions from a comma separated list of version names

Components

Parent issue's components

Set components from a comma separated list of component names

Due date

Set due date. Use work (since 5.7) to exclude non-working days (example: 5 work).

Time tracking

Set original and remaining estimate

Issue security level

create issue

None

Set security level for the issue

Labels

List of labels to be set on new issue

Link

Adds a link to another issue after the new issue is created

Copy links

All link types

Copy one or more links from the issue key (or keys) provided to the new issue. The new issue key will replace the key specified for the copy. By default, all link types will be copied from each issue key specified. Specify a comma separated list of link types to subset the copy to only those issue types. Since 5.0.

Copy remote links

All remote link types

Copy one or more remote links from the issue key (or keys) provided to the new issue. The new issue key will replace the key specified for the copy. By default, all remote link types will be copied from each issue key specified. Specify a comma separated list of remote link types to subset the copy to only those issue types. Since 6.0

Attachments

Issue key. If specified, attachments will be copied from the issue to the new issue after it is created.

Watchers

Add watchers from a comma separated list of user ids

Comment

Comment added to new issue after it is created

Comment security

None

Security group or role for the comment. Since 5.8.

Copy parent issue custom fields

A comma separated list of custom field names or ids - each field is copied from the parent issue

Copy original issue custom fields

A comma separated list of custom field names or ids - each field is copied from the original issue

Set custom field

Set the value of a specific custom field identified by its name or id.

For date fields, there is an option to specify a date offset (in days) that will be used to adjust the value. Use work (since 5.7) to exclude non-working days (example: 5 work).

JQL query

Query that is run to provide substitution variables including %jql_result_count%, %jql_result_list%, and %jql_result_1%. The query will be run once unless the field contains an entry specific subsitution variable, it which case the query will be run for each different entry value.

Create multiple issues

See: How to create multiple issues

Acting user

Transition user

Provides a way to for some permission checking and access to be done under a user different than the user doing the transition. This allows the workflow designer more flexibility to do actions for the user that they normally would not be able to do outside of the workflow. Tip: How to act on an issue for the assignee.

Subtask default handling

create subtask

Recommend to not select this option unless needed. Select to have JIRA default subtask create handling applied. Selecting this may override settings provided in the create configuration like setting fix versions. Defaulting behavior will be similar to how subtasks are created from the UI. Since 5.0.

Example scenarios where you may need this:

• You need a create listener to access the issue parent

• You have a post function on the create issue transition than needs access to the parent

Environment

Set the environment field

Notes

Allows the workflow designer to document the post function