Is it possible to clone issue changes across different projects?

[Leon Gumba]

Hello! I've set up a rule in Jira Cloud Automation to clone issues from one project to another upon their creation. But I also need subsequent updates to the original issue to be automatically cloned to the newly created issue in the destination project as well.

For example, a user creates an issue in Project A and this issue is successfully cloned to Project B based on the automation rule. Then, a user makes changes to that issue inside the initial Project A (e.g. changes a value inside a custom field, adds a comment or an attachment, etc.). Is there a way, without using third-party apps, to clone these changes in real time to the corresponding issue in Project B?

If it's not possible, what's the best way to track the changes in the initial issue for users who work in Project B? Perhaps, linking those issues together somehow?

[Kalyan Sattaluri · Accepted solution]

Hello @Leon Gumba 

Welcome to community. yes, its possible natively.

You need to write another rule with trigger - Field value changed and choose all your fields you want to monitor/sync.

Then you branch on linked issues, choose link type as Cloned and then you can edit the issue in Project B with values frmo the trigger issue. you will need to reference trigger issue fields as {{triggerissue.field}}..

Just curious, will there be just 1 cloned issue..

[Leon Gumba]

Hey @Kalyan Sattaluri thank you very much for your reply!

I'm trying to figure out how to implement your suggestion. I'm probably doing it wrong right now, so I'll share a screenshot. Maybe you can tell me what I should change in this setup?

[Kalyan Sattaluri]

hello @Leon Gumba 

What you have is correct and it should work.

Just note that if your linked issue is in another project, then you have to expand the scope of your rule in rule details to include both projects so that the cloned issue can be updated.

If you dont have permissions to increase scope, then unfortunately, you have to make use of REST api to do this update.

Hope it helps, let us know if issues.

[Leon Gumba]

I know it's been almost two months since I created this topic, but I decided to revisit it and share my solution in case someone else encounters a similar situation/stumbles upon this thread.

I found that the best approach is to configure filters in the target project to display issues from the source project on its board. This method is much easier and more convenient than trying to figure out how to clone issues and keep the cloned issue changes updated in real time.

[Jeremyn Horsley]

Hi Leons,  Could you please elaborate on your solution?  A screenshot of the filter would help.  I am trying to include and track issues in my project that are being completed within another projects scope.  Thanks in advance!

[Leon Gumba]

@Jeremyn Horsley hi! You have a couple of ways to write that kind of query:

project in ("Your 1st project key", "Your 2nd project key")

project = "Your 1st project key" OR project = "Your 2nd project key"

Here's a screenshot of an example: