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 to move a cloned issue from one epic to another in a different Jira project

Mateja Leskovec

Hello everyone,

I'd like to understand if it's possible to set the following automation:

Each team working on a product has their own Jira project. Their work is tracked in different epics under one initiative per product. As the products are kicked off, the epics are created - meaning that each project has it's unique initiative and respective epics.

At one point we'd need to clone a ticket from Project A to Project B, but also track it under the epic of Project B.

Does the automation support this?

Thank you!

Accepted answers

All comments

Trudy P Claspill

Hello @Mateja Leskovec

Are these Company Managed projects?

Automation has a Clone issue action that would allow you to specify another project as the destination. In that action you can also set the fields in the newly created issue, and that would include setting the Parent of the new issue to match the source issue

This works only between Company Managed projects.

Luka Hummel - codefortynine

Hi @Mateja Leskovec

If you are willing to try a third-party app, you can try our Deep Clone for Jira.

Deep Clone can keep the original Parent Link when cloning issues to other projects.

2024-07-19 11-16.png

Mateja Leskovec

Hello Trudy,

we would need also need the Parent of the newly created issue to change to a different epic under the same initiative.

So the completion of the original issue in Project A and under Epic C would created a clone of X in the Project B and under Epic D, but both housed under the Initiative X.

Mateja Leskovec

Hello Luka, we would want this to be an automated process, not a manual one.

Trudy P Claspill

The Clone action allows you to set the Parent field, which is how you identify the parent/Epic for the newly created issue. Here is a simple example where you know the explicit issue key of the Epic.

Screenshot 2024-07-22 at 8.28.12 AM.png

The next thing you have to determine is how you will know what Epic to specify. Do all the cloned issues go to the same Epic, every time? Or is there some logic you need to execute to determine the Epic that will be the parent of a particular clone?

Luka Hummel - codefortynine

Hi @Mateja Leskovec

That's not a problem, you can use Deep Clone together with Jira Automations and use a normal Jira Automation trigger to start a Deep Clone. You can read more on that here.

You then can also use the Field Editor feature, which allows you to set a new Parent for the cloned issue(s). Furthermore, you even can use Jira Expressions to set a dynamic parent.

2024-07-22 17-32.png

Mateja Leskovec

Hello Trudy,

every time is a different epic under the same initiative, so the automation would have to figure that out while cloning the issue.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-work-management

jira-work-management-cloud