It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Possible to synchronize workflow status on issues between two jira projects

One project has an incident and you need to amsolve the incident in another project. You clone the issue and move the clone to the other project. Can you synchronize status between those two issues in some way?

4 answers

1 accepted

2 votes
Answer accepted
Hello, Kindly have a look at the Backbone Issue Sync pugin. It can synch statuses from different Jira instances, maybe you can make it work for one instance.

Hi @Ulrika Eriksson

As Alexey says (thanks for the mention by the way Alexey!), it's possible to use Backbone to synchronize issues between projects in the same instance.

It's possible to synchronize workflow statuses, and also other issue data – including fields, comments and attachments.

In fact, the Backbone documentation features a step-by-step guide on how to set up such a synchronization.

If you have any questions about Backbone, I'll be happy to help.

Cheers, Tom.


I'm part of Deviniti team. 

You can exchange data, tickets, comments, execute workflow transitions using IssueSYNC app. It is designed to synchronize either different Jira instances or single one.

In that case you can pass tickets from one project/team to another and let team communicate with each other. But if you are looking only for workflows synchronization I believe the more convenient will be to use Script Runner or Workflow Extensions if you already have one of these.

If you have questions, please contact us.



1 vote
Thomas Schlegel Community Leader Apr 11, 2018

Hi Ulrika,

not with plain Jira. You have to "connect" the workflows from both projects through workflow post functions. 

The "Jira Misc Workflow Extension" app comes with a postfunction "Transition linked issues".

If your issues are linked with a special issue link (do not use the regular standard links types, because there might be other linked issues that you do not want to transition remotely), you can trigger a transition on the linked issue. But you have to take care of both workflows. Every single workflow transition has to trigger the corresponding transition on the other workflow. This is not a trivial task.

There may also be other plugins with that functionality, but we use JMWE for this purpose and it works well.  


I'm Riddhi from the Exalate team, Exalate is made for the use case you described. As it allows syncing information bi- and uni-directionally between multiple Jira instances. Or separate projects in your local Jira.

It's mega flexible, you can sync all types of information, including comments, attachments and custom fields. You can control what to sync and what not, and much more ....

It can also cater to situations of dealing in a private to public sync, You can find out more about it here.


By the way, It might also be useful to set up a live video-discussion to demonstrate how Exalate would get set up for your use case

Would that be valuable to you? You can book a suitable slot here.



Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Jira

Demo Den Ep. 7: New Jira Cloud Reports

Learn how to use two new reports for next-gen projects in Jira Cloud:  Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...

314 views 1 3
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you