Clone epic, tasks and sub-tasks

Use case

Clone an epic, the tasks under the epic and the sub-tasks of these tasks.

Prerequisites

Set up custom fields

Create a Text (single line) custom field

Name: Template Issue

Configuration

Add the first Create issue post function

Add a Create issue post function to the desired workflow transition.

Issues to be created

Mode

Choose Single issue

Issue type

Choose Parser expression (standard issue type) and write the following expression:

%{issue.issueType}

Summary

Enter the following expression

CLONE - %{issue.summary}

with parsing mode set to Advanced Text

Additional options

Update the following fields

Epic Name

Choose Parsed text (basic mode) and write the following expression:

CLONE - %{issue.summary}

Resolution

Choose Parsed text (advanced mode) and write the following expression:

null

Copy remaining fields

Select From current issue and All remaining fields

Issue links

Add a Relates to issue link and link it to the current issue

Add a second Create issue post function

Issues to be created

Mode

Choose Multiple issues

Expression

Enter the following parser expression

toStringList(%{issue.cfnnnnn})
# Replace the field code with the one of your custom field. Use the field dropdown to automatically insert the field code.
# You can use any field supporting multiple options, e.g. checkboxes or multi-selects.

with parsing mode set to Text list

Issue type

Choose Selected issue type → Sub-task

Parent issue

Choose Current issue

Screenshots

Screencast

Related use cases

Use case	Workflow function	Parser functions	Label
Add a hyperlink to an issue in an email	Send email
Add assignee as watcher to every blocking issue	Update linked issue or sub-task
Add a table with the elements of a text to an email	Send email	toString() textOnStringList() toStringList()
Add attachments from current issue to cloning issues	Update linked issue or sub-task
Add comment with the request participants' display name	Add comment	toString() textOnStringList() toStringList() userDisplayName()
Add days skipping weekends and holidays to a Date Picker field	Update or copy field values	addTime()
Add internal Jira Service Management comment	Add comment
Add or remove request participants	Update or copy field values
Add percentaged profit margin when closing issue	Log work
Add sub-tasks to an automatically created issue	Create issue	getMatchingValue()
Add three days skipping weekends automatically to a Date Picker	Update fields	dateTimeToString() dayOfTheWeek() addDays()
Add user to field depending on selected options	Update field based on rules
Add watchers based on issue type	Add or remove watchers
Add watchers from another field	Update fields Transition issue	union() toStringList()
Add watchers ignoring inactive users	Update or copy field values	usersInGroup() isActive() toString() filterByPredicate()
A developer must not execute the transition	User is not in project role
Alert the assignee of an important issue	Send email
Alert the assignee of important issues	Add comme nt
Alert the reporter	Add comment
All blocking issues must be resolved	Condition on linked issues Validation of linked issues
All sub-tasks in the Closed status must have a specific resolution	Condition on sub-tasks Validation of sub-tasks
All sub-tasks must be Done or Closed	Condition on sub-tasks Validation of sub-tasks
All sub-tasks must be resolved	Condition on sub-tasks Validation of sub-tasks		STAFF PICK
All sub-tasks with a resolution of Done must be in a specific status	Condition on sub-tasks Validation of sub-tasks
An issue must have at least 3 resolved Test Cases	Condition on sub-tasks Validation of sub-tasks
Assignee may only have a restricted number of assigned issues	Condition based on JQL query Validation based on JQL query
Assign important issues to the project lead	Update or copy field values
Assign issue to current user	Update or copy field values
Assign issue to the default user of a role	Assign to project role
Automatically assign a tester during your development process	Assign to project role