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; } } }

How to clone issue to another project and have status changes reflected back to the original issue?

Katie M_xma6tp

I am looking for an automated process to hopefully clone issues from one board and send them to different projects. Once the issues are cloned and in a different project I want to be able to get status updates (in progress, done, etc) sent back to the original issue and update their status accordingly.

The process would be: Manually clone issue in board A to desired project which we'll call B for this purpose. Keep the issues linked. Once the cloned issue, B, has a status update, I want this to be sent to issue A and update its status.

Is this possible with Jira's native automation or would a marketplace app be necessary?

Accepted answers

Robert DaSilva_a432as

Hi @Katie M ,

I was helping another community member with a similar request earlier this week. You can review that conversation here: https://community.atlassian.com/t5/Jira-questions/Issue-fields-information-sync-in-Jira-Cloud/qaq-p/2817866

The short answer is yes, this is possible through Jira Automation.

You'll want to set up a rule that monitors the projects issues are cloned into, and have an "Issue Transitioned" trigger. From here, you can use a "For Linked Issues" condition to find the original issue you cloned from. In this new branch, you can then modify the status to be equal to the trigger issue, which would be the cloned issue.

Here's a brief screenshot of what you should be aiming for:

Screenshot 2024-09-26 at 3.11.05 PM.png

You'll want to make sure that the automation rule is applied to all projects in scope, any trigger projects, and then any destination projects you want to monitor.

As always, I recommend testing this in a sandbox before deploying to production.

Hope that helps,

Robert

All comments

Robert DaSilva_a432as

Hi @Katie M ,

The short answer is yes, this is possible through Jira Automation.

Here's a brief screenshot of what you should be aiming for:

Screenshot 2024-09-26 at 3.11.05 PM.png

You'll want to make sure that the automation rule is applied to all projects in scope, any trigger projects, and then any destination projects you want to monitor.

As always, I recommend testing this in a sandbox before deploying to production.

Hope that helps,

Robert

Clara Belin-Brosseau_Elements

Hello @Katie M

If you're seeking for an easy way to automatically clone an issue across projects and sync their status, I 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).

You can check our guide here.

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

Katie M_xma6tp

Hi Robert,

Thank you this is perfect! Do you happen to know if there is a way so that only one project is having the issue status updated instead of this being Jira-wide?

We have the project where the issues will originate and then we will be cloning them to multiple projects depending on the type. From there though I'd only like the original project to have its issues transitioned with the cloned ones. I don't want other projects to be affected by this automation rule.

Robert DaSilva_a432as

Hi @Katie M ,

If you'd like this to only trigger from one project, I would recommend adding in a Condition box immediately after the "Trigger", which restricts the project to the only one you care for.

This means any "Status Transition" inside the source project will trigger the rule on all the linked projects.

Hope this helps!

Robert

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud