How to sync custom release fields between two separate Jira instances based on an Epic ID?

[Hari Shankar]

Hi everyone,

I am looking for advice on how to automate data syncing between two completely separate Jira Cloud instances (Instance A: Digital Team, Instance B: Platform Team).

Our Setup & Use Case:

• Instance A (Digital): Contains our main Epics and Stories.
• Instance B (Platform): Platform developers work on dependent stories here.
• To link them, we have a custom field in Instance B where we manually paste/tag the corresponding Instance A Epic ID.

The Goal:
Whenever a Platform team member updates the following custom fields in an Instance B story:

1. Aspired Quarter
2. Planned Release
3. Revised Release Date

I need those exact values to automatically trigger an update and sync over to the corresponding story/Epic in Instance A based on that tagged Epic ID field. Logging into two instances to manually copy dates is causing massive reporting overhead.

What is the best way to achieve this? Can Jira Automation native webhooks handle this cross-instance lookup, or do we absolutely need a third-party syncing tool like Exalate or Backbone? 

Any examples or rulesets would be greatly appreciated!

[Arkadiusz Wroblewski]

Hello and welcome to the Community @Hari Shankar 

Does your custom field in Instance B store the actual Instance A issue key like ABC-123, or only another internal ID/reference? The implementation is much simpler if it stores the issue key directly.

In general, that should be easily doable with automation and a web request.

Depending on the scale, Exalate or Backbone would be the safer option. If the scale is small, automation should be fine.

Best,

Arkadiusz 🤠