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 - Sync between original task and cloned task

Alejandra Martin

Hi community. I'm working with several automation, and i need to resolve following casuistic.

Projects

Create Issue and Transitioned from To Process to Done

Automation 1. When the issue is in Done status, automation clone issue in Project 2

This work OK, and link original issues to clone issue.

But We need resolve that if the user transitioned from Done to Cancelled in project 1, the clone Issue of Project 2 update status to Cancelled

Could you guide how can made that last automation?

Thanks in advance!

Best regards!

Alejandra Martìn

Accepted answers

Bill Sheboy

Hi @Alejandra Martin

What is the scope of your rule (in the details at the top): single-project, multiple-project, or global?

A single-project, scope rule can create (or clone) into other projects, but it cannot see or update them otherwise. And so your rule to sync the cancelled work items will need multiple-project or global scope.

Please discuss this with your Jira Site Admin as they will need to change the scope, and they may want to understand the scenario to prevent any side-effects for other projects.

Kind regards,
Bill

All comments

Brita Moorus

Hi, @Alejandra Martin! 👋

You could solve that using the following steps:

Trigger: When work item is transitioned from Done to Cancelled.
Related work items condition: Check that the work item has a work item link of type "clone" (to ensure that it has a cloned work item).
Branch rule/related work items: For Linked work items that have cloned link type.
Transition work item: Transition work item to Cancelled status (you can copy that from trigger work item).

Screenshot 2025-06-27 at 17.43.11.png

Hope this helps! ✨

Alejandra Martin

Hi Brita, thanks for your answer. I made the rule but seems to be not work. This is the cloend issued in Project. 2 In Linked Work items refer the original work item of project 1. PRoject 1 is cancelled.

Automation is active for those 2 projects, ant not show error

Alejandra Martin

Bill Sheboy

Hi @Alejandra Martin

What is the scope of your rule (in the details at the top): single-project, multiple-project, or global?

Please discuss this with your Jira Site Admin as they will need to change the scope, and they may want to understand the scenario to prevent any side-effects for other projects.

Kind regards,
Bill

Alejandra Martin

Hi Bill, scope is both project (1 and 2).

Bill Sheboy

Please post an image of the audit log details showing the rule execution, expanding the areas at the right side. This will help compare to the rule image for which steps and work items processed.

Alejandra Martin

Hi Bill, thanks for your update. I think rule is not triggered because, audit log not show rule execution, only setup changes.

Thanks in advance!

Clara Belin-Brosseau_Elevatic

Hi @Alejandra Martin

An alternative to Automation (easier and quicker) to clone issues and then keep their statuses in sync would be to try our app Elements Copy & Sync.

You'll be able to implement your use case within a single configuration rule.

Don't hesitate to check the documentation or even directly try the app (it's free during 30 days and it stays free under 10 users).

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