Bidirectional Issue Syncing Across Projects

[Candelario]

Looking for free, easy to use, and top recommended choice!

Using server version!

[Trudy P Claspill]

Hello @Candelario 

Welcome to the Atlassian community.

Are you truly using Jira Server or are you using Jira Data Center?

If you are using Jira Server, new license sales for that and for Marketplace apps running on Jira Server have ended. You can now only get new app licenses to run on Jira Data Center.

Can you provide more information about you use case for synching data across Jira projects? Are you trying to synch all fields? If not all, what fields do you need to include in your synch? Are you trying to synch data between projects with identical configurations or different configurations?

[Kevin Yorston - Exalate]

Hello @Candelario ,

Welcome to the Atlassian Community!

The approach Matthias suggested using Automation could work, but it can be limited and sometimes difficult to maintain. I believe using a dedicated app would be a better long-term approach for this use case (Disclosure: I'm part of the Exalate team)

Whether you are using Jira Server, Data Center, or Cloud, Exalate can connect your two projects and keep them in sync. It automatically synchronizes comments, custom fields, and statuses. Since it uses Groovy scripting, you can create custom logic for your sync—such as custom status mappings or syncing a custom field on one side as a comment on the other.

Best,

Kevin

[Melika]

Two projects, one truth! no copy-paste, no drift, no "which one's current."

That's the whole point of Everview's two-way sync. It sits on top of Jira and connects your projects into one live surface and the sync runs both directions, in real time. Move a task, change a status, shift a date in one project, and the linked issue in the other updates the same moment not on a nightly job, not after someone remembers to mirror it. And it works the other way just as fast: a change made in Jira lands back on the canvas instantly. Both sides stay the same truth, always.

What that gives you:

Real-time, both directions an edit on either side propagates the moment it happens, so the two projects never disagree.

Your issues stay put Jira stays the source of record; nothing is migrated or duplicated, the link just keeps them in step.

Every change carries its author and timestamp so the sync isn't a black box; you can see exactly what moved, when, and who moved it.

It reads from the work itself, so what's synced is the real state of the issue not a stale mirror of it.


Every card on the canvas is a real Jira issue, carrying its actual key — PF-2, PF-4, OT-2, and so on. That key is the link, not a copy. So when you move a task, change its status, or edit it on the canvas, the change writes back to that exact Jira issue the same moment — and a change made in Jira lands on the card just as instantly. Same issue, same key, two views, one live state — never a mirror that drifts out of date.


Everview (demo data): a task moved in one project, reflected the same moment in the linked Jira issue — both directions, live.

The sandbox is open if you want to poke at it first (no signup) and it's on the Atlassian Marketplace if you'd rather try it on your own instance: Everview.ai 

[Laura Campbell]

Hi @Melika looks like you work for a Marketplace partner. Please check out the Partner guidelines for tips on how to update your profile to get the Partner badge as well as the rules of engagement for promoting apps on Community. https://community.atlassian.com/forums/App-Central-articles/Atlassian-Partners-Rules-of-Engagement/ba-p/2899328

[Rik de Valk _Brainboss_]

Hi @Candelario , 

Considering your 'easy to use' requirement, an app such as the Issue sync app @Matthias Gaiser _K15t_ suggested is probably the way to go. 

If you want to do without Apps, you can look into Flows (automations). There are limitations to what you can sync with Flows. But it can do a lot. 

But you need to consider things such as: 

• Do you want to sync all issues, so that you create a completely mirrored Space with 100% of the work items from Space A, replicated in Space B? 
• If not, how can we automatically recognise which work items need to be synced? 
• How do you store what the 'source work item' for a cloned work item is, so that you can keep updating them? 
• Do you want to sync one-way, or bi-directional? 

Cheers, 

Rik 

[Matthias Gaiser _K15t_]

Hello @Candelario

Adding to @Trudy P Claspill's questions:

• Are you interested in syncing attachments & comments?
• How about third party app data?
• Are you synchronizing within the same Jira instance or across different ones?

To me, it sounded like you're inside one Jira - and I think, you can either go for free or easy to use.

Free approaches can be:

• Jira Automation - you can define a couple of rules and control exactly which data is getting exchanged
  • WHEN: Issue Created, THEN: create issue in other project. Make sure to store a reference to the original issue in e.g. a custom field.
  • WHEN: Issue Updated, THEN: lookup the issue by the reference AND edit it
  • and some more fine-tuning in similar rules. In my experience, esp. attachments and comments have been tricky to get right with this approach.
• You can also vibe-code some scripts and run some periodically with an AI of your choice

For an easy to use approach, I'd recommed using a dedicated issue sync app. Please note that I'm part of a team behind such an issue sync app, Backbone Work Sync. These apps take away the burden of creating and especially maintaining different scripts or rules and offer the ease of a UI to set everything up.

Hope that helps a bit.