Synchronize issue when created or changed to issue in another project and vice versa

Question

I want to build a automation rule, which synchronizes the content of an issue (fields: description, attachements, comments -> in best case the complete content).

When a issue in project A is created, then clone it to project B.

If the value of a field changes in project B it will be synchronized to the corresponding issue in project A and so on.

It's a difficult task, I know, but I would be very thankfull if anybody shares his experience.

Best regards

Lukas

Clara Belin-Brosseau_Elevatic · Answer

Hi @Lukas Pernpeintner

In case you didn't find an easy way to solve this yet, I can suggest trying our app Elements Copy & Sync to both clone an issue from project A to project B and keep their fields synchronized.

One single app does everything in a unique configuration so it should only take you a few minutes to set up.

Here are the steps you should follow:

* Create a "Copy & Sync" recipe
* Define source and targets projects
* In content, define which fields should be synchronized (description, attachements, comments and more) and the synchronization direction

* Trigger: define when the clone and sync should be triggered: in your case it can be an Automation trigger "When a new project is created".

Don't hesitate to try the app and ask if you have any question!

Lukas Pernpeintner · Answer

Hello @Trudy P Claspill

the type of both projects is company-managed, Software - Kanban.

We played around with some simple Automation Rules and we also tried to create such a rule on our own way, with the help of AI, but the level of experience is more or less basic.

I also know the issue-security-schemas. We use them on other projects with other requirements, but this solution doesn't fit in this case.

The background of the synchronization is that we want to let external users into our instance and we want to ensure that they don't see any of our stuff.

We just want to have a list of open points with the externals in another project (project B)  and the source of the list are issue, which are created from project A. The second requirement is that the externals have to maintain their issues and we want to see values then in project A.

So the main requirement would be an automation rule, which clones issues, when created in project A (or project B)  and update the both linked issues when changes are made in project A or project B.

In one word I think it's a synchronization, but of course not with any purchased apps 😁

I hope this helps you to understand my problem.

Thanks in advance!

Lukas

Trudy P Claspill · Answer

Hello @Lukas Pernpeintner

Welcome to the Atlassian community.

What are the space types of Project A and Project B? Are they Service, Software, or Business? Are they Team-managed or Company-managed?

What problem are you trying to solve by cloning issues and synchronizing data between them?

What is your level of experience with Automation Rules?

What you want will take multiple rules to accomplish; one to clone the issue, and 1..n to copy data between the issues.

Given the potential complexity of this solution it is important to understand the problem you are trying to solve. There may be a better way to solve the problem or reduce the complexity of the solution.