How to quickly clone task or subtask

[Blake Thompson]

I have a repetitive task that must be done dozens of times in different places. 
To track the status of the task, I make subtasks for each of the places the repetitive task must be done.
The problem is that cloning subtasks one at a time is tedious and slow. 

My team encounters this type of issue frequently regarding generic subtasks that we need many clones of, and only the name is changing on each of the subtasks.

Is there a way to "mass clone" a task or subtask many times, instead of manually cloning over and over? It would make this use case in Jira so much less time consuming. 

[Luka Hummel - codefortynine]

Hello @Blake Thompson and welcome to the community!

If you're looking to bulk clone tasks and subtasks efficiently, I recommend giving our app Deep Clone for Jira a try. Deep Clone allows you to clone multiple issues, including subtasks, in bulk with just a few clicks. Deep Clone supports cloning up to 100,000 issues at once.

You can also customize which fields to clone and automate repetitive processes, saving you a lot of time. It's perfect for your use case of repetitive tasks with minor changes.

[Clara Belin-Brosseau_Elements]

Hello @Blake Thompson and welcome to the Atlassian Community!

If I understand correctly, you’re trying to bulk clone tasks and sub-tasks at once, right?

In that case, I can suggest trying our app Elements Copy & Sync that allows you to clone and sync a full hierarchy of issues with all their content (summary, description, custom fields, comments, attachments, etc). It's easy and can of course be automated.

You can check the guide here.

The app is for free during 30 days (and it stays free under 10 users)

[Shawn Doyle - ReleaseTEAM]

Hi @Blake Thompson 

Is this something that you always want to happen? If so you could create an automation that is triggered at issue creation (or some other condition) and then clones into subtasks.

If not you could set up a manually triggered automation to clone the subtasks and fire it off as needed. You would need a way to identify which issues to create the subtasks on.

[Victor Law]

Hi @Blake Thompson

Welcome to the community.

Perhaps you can consider configuring a Manual Trigger automation with a set of actions that create sub-tasks using a list of fields as a template.

• https://support.atlassian.com/cloud-automation/docs/jira-automation-triggers/#Manual-trigger-from-issue
• https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Create-sub-tasks

Thank you.