How to make a clonned issue from a project update in the other project?
Asked by Raabe Tatiane Barbosa _DHL Supply Chain_:

I need a separete team to run their project, but I need that the issue they create clones to another project and all the changes they make in this project also updates in the other project. Basically, they need to share the issue in both projects


Answers:
author: Alex Koxaras _Relational_
body: Hi [@Raabe Tatiane Barbosa _DHL Supply Chain_](/t5/user/viewprofilepage/user-id/5010246) and welcome to the community,

You could do that without cloning the issue. In Jira you can have your kanban boards with issues from different projects. You only have to change the filter behind the kanban board and the team behind project "B" will be able to see the issue created in project "A". That is the first solution

The second solution would be to use an app like Exalate. This app clones and sync the issues and whatever else you want to do.

A third option would be to create multiple jira automation rules to clone and sync the issues between projects. However this solution is something that I haven't tested, but Im pretty sure that it can be done.

comments: author: Raabe Tatiane Barbosa _DHL Supply Chain_
body: Thank you for your answer!   

Unfortunatly the kanban board does not work for me on this case. I really need to sync the issues beteween projects. I could automate the clone, but I'm not being able to keep the clone sincronized in the other project. Any tips on that?


author: Matthias Gaiser _K15t_
body: [@Raabe Tatiane Barbosa _DHL Supply Chain_](/t5/user/viewprofilepage/user-id/5010246) as [@Mark Segall](/t5/user/viewprofilepage/user-id/4667637) pointed out on [your other post](TRIGGER:%20Issue Updated BRANCH: linked issues (your link type) ACTION: Edit Issue Select all of the fields you wish to copy and set to copy from trigger issue), you can also create an **additional rule to keep your issues in sync** which could look like this. This assumes that you have created an **issue link** when you initially cloned the issue.

* TRIGGER: Issue Updated
* BRANCH: linked issues (your link type)
  * ACTION: Edit Issue
    * Select all of the fields you wish to copy and set to copy from trigger issue

If this sounds too messy or error-prone to you, I'd recommend to either go for **sharing the issue** as [@Alex Koxaras _Relational_](/t5/user/viewprofilepage/user-id/4150197) mentioned or **syncing the issue** using an issue sync app like [@Mathieu Lepoutre _Exalate_](/t5/user/viewprofilepage/user-id/4856931) and [@Diana_Architect_ZigiWave](/t5/user/viewprofilepage/user-id/4803013) mentioned. For a full list of the different issue sync apps, check out the [Atlassian marketplace](https://marketplace.atlassian.com/search?query=issue%20sync).

Cheers,  
Matthias.

PS: Please note that I'm part of the team behind [Backbone Issue Sync](https://marketplace.atlassian.com/apps/1215199/backbone-issue-sync-for-jira?hosting=cloud&tab=overview). If you'd like to get a demo, feel free to [book one here](https://www.k15t.com/products/backbone-issue-sync-for-jira#backboneissuesyncforjira-demo).


author: Mathieu Lepoutre _Exalate_
body: Hi [@Raabe Tatiane Barbosa _DHL Supply Chain_](/t5/user/viewprofilepage/user-id/5010246)

I'm working as a pre-sales engineer with [Exalate](https://marketplace.atlassian.com/search?query=issue%20sync).

Cloning issues between projects, is a perfect use-case for a bi-directional integration of Exalate. Through triggers this syncronization can easily be done automatically.

Exalate will work as an add-on and act as an integration tool.

The ticket will out-of-the-box be fully bi-directionally syncronized, which means, if a field gets updated on either side, it will automatically update on the other side, you can change this to make it uni-directional if you so please.

Exalate is easy and straightforward to set-up and you can control exactly which data you want to send and/or receive.

If you would like to see a [customized demo](https://exalate.com/book-demo/) of the product, please book a slot with us.

There is a trial periode which we can use to set-up your POC.

Cheers


author: Diana_Architect_ZigiWave
body: [@Raabe Tatiane Barbosa _DHL Supply Chain_](/t5/user/viewprofilepage/user-id/5010246) hello. You can easily achieve your use case with synchronization between the projects. If you're open to using a 3rd party tool for this, feel free to look at ZigiOps. It's a no-code tool that can be customized so it can fit various use cases. It can help you connect the two projects bi-directionally, sync their data, and keep them up-to-date in real-time ( a change in one of them will immediately show up in the other). Check it out and if you think it might be useful for your project, you can [book a demo](https://bit.ly/3pXlpg3).

Regards, Diana (ZigiWave team)