nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Automation for cloning tickets from one to another project and linking as it is.

madhu kiran_vbsd0w

We have two projects one project we have template tickets feature->epic->story

second project when ever an initiative is created and a manually automation is triggered we need to copy all the tickets from template project and have them as children of Initiative.

initiative->feature->epic->story.

Accepted answers

All comments

Varsha Joshi

Hi @madhu kiran

Have you tried creating an automation rule? Could you share what have you created so far? It can be done; I have done that for one of our projects.

Trudy P Claspill

Hello @madhu kiran

In addition to the questions asked by @Varsha Joshi :

Are you working with Jira Cloud or Jira Data Center?
If you are working with Jira Cloud, are you working with the Free, Standard, Premium, or Enterprise subscription.
Have you modified the work item hierarchy to support a hierarchy of Initiative / Feature / Epic / Story?

madhu kiran_vbsd0w

Hi @Trudy P Claspill @Varsha Joshi ,

1. I am using Jira cloud premium.
2. yes i have updated the work item hierarchy.

I was able to clone issues and I was able to add initiative as parent to feature,
but i am facing issues when linking epics to features.

Screenshot 2025-09-23 084047.png Screenshot 2025-09-23 084059.png

please let me know how i can do it.

Hardik Babbar

Hi @madhu kiran !

Why not add links to the original "template project" features under the initiative in the second project?

I say this because if you clone the work items, you'll have duplicates of the same work which will not be synced with the original work items adding overhead and future sync issues (when field values, comments or status changes on the original work item)!

madhu kiran_vbsd0w

Hi @Hardik Babbar ,

for every initiative we have to the have the tickets with some default details, so once it is cloned it will be changed according to the requirement.

Hardik Babbar

Ah, gotcha! Unfortunately, I wasn't able to find a way to do this within one automation, maybe API can be used.

One workaround I can think of is using two automations:

First: Manual Trigger from the second project's Initiative to clone all features. Add a link "is cloned by" to the original feature.

Screenshot 2025-09-29 093838.png

Second: Automation Trigger when a Feature is created and has a link "is cloned by" to loop through all related Epics in the first project.

Screenshot 2025-09-29 101549.png

Now there are a few points to note here:
1. The second automation needs to have the Checkbox checked to allow it to run from other rule actions.

Screenshot 2025-09-29 101942.png

2. The "is cloned by" link can later be removed within the second automation as well.

Again, just a workaround, maybe there is a better solution out there

madhukiran

Thank you for your suggestion, I got created rule and it is working fine.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

automation