These examples show how to combine the Clone work item and Clone JQL search results automation actions in real Jira Automation flows.
1. Scheduled hierarchy clone
-
Objective: Keep a recurring project plan (an epic with all its child issues) up to date without recreating it manually.
-
Process: Build a scheduled automation rule (e.g. a weekly or monthly trigger) that runs the Clone work item action against the template epic's key, cloning the full hierarchy into the current or a chosen target project.
-
Outcome: A fresh copy of the project plan is created automatically on schedule, with no manual cloning step.
2. Clone on resolution
-
Objective: Immediately start the next cycle once all items in an epic are resolved.
-
Process: Trigger a rule when the last child item of an epic transitions to a resolved status, add a condition confirming all children are resolved, then run Clone work item on the parent epic's key to clone the epic together with its child hierarchy.
-
Outcome: A new instance of the epic and its children is created the moment the previous cycle finishes, keeping recurring work moving without manual intervention.
3. Bulk clone from a JQL search
-
Objective: Clone a whole set of template items in one automation run — e.g. all template epics needed for a new project kickoff.
-
Process: Use Clone JQL search results with a JQL query identifying the template items (e.g.
project = TEMPLATES AND labels = kickoff), and set an appropriate maximum item count as a safety limit. -
Outcome: All matching items are cloned together in a single run, saving time compared to cloning each template individually.
Learn more
If you're having trouble setting this up, contact us or book a demo.