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

[madhu kiran]

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.

[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)!

[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 Claspill]

Hello @madhu kiran 

In addition to the questions asked by @Varsha Joshi :

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

[madhu kiran]

Hi @Trudy 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.



please let me know how i can do it.