How to sync to Spaces on JIRA Cloud?

[Satyam Mooloo]

Action 1:

When a card is created in Space A and labelled "COS", an automation rule will be triggered copy the card to Space B.

Action 2: When an update is effected on an existing Card in Space A, how will it find the linked card on Space B and move the updates?

Note: no JIRA admin privilege, only space admin

[Arkadiusz Wroblewski]

Hello @Satyam Mooloo 

@Marc -Devoteam-  Provided you already good Solution.

Alternative if you need a real two-way sync, an app like Backbone Work Sync is a reasonable option for that use case, especially when the requirement is to keep issues aligned across projects or sites.

[Marc -Devoteam-]

Hi @Satyam Mooloo 

This can be done using automation(s), but as the automation(s) need to span multiple spaces, you need to have access in both spaces and the automaton(s) scope need to be on multiple spaces.

This last action can only be done from the Global automation option and done by a Jira administrator or higher ranked admin.

This can't be done by a space admin, so you need to work with your Jira admin.

[Matthias Gaiser _K15t_]

To answer the part "how will it find the linked card on Space B":

When you create a card in your Action 1, I would also add a work item link between these issues with a specific link type like "created by".

Whenever a card is updated (Action 2), you can then add a branch component Branch rule / related work items and select your link type and perform the updates as you want it to.

As @Arkadiusz Wroblewski said, if syncing via automations gets too cumbersome for you, there are specific work item syncing solutions in the Atlassian Marketplace. I'm happy to help you further with Backbone Work Sync, if needed, since I'm part of that team. :)

[Gor Greyan]

Hi @Satyam Mooloo

Welcome to the Atlassian Community!

You should have 2 automations.

1. Issue Creation

Trigger: Issue Create
Condition: Labels contain COS
Action: Create an issue in Space B
Branch Rule: Most Recently Created Issue
Action: Add Issue Link (e.g., “relates to”)

2. Issue Update

Trigger: Issue Updated in Space A
Branch Rule: Linked Issues "relates to"
Condition: label contains COS
Edit Issue: Space B issue

Also, check that you or the actor of that automation can create and link issues in Space B. Also, the automation should be multiproject, so you should be a Jira Admin or it can be done with Jira Admin privileges. With Space admin permission, you can't do that.

Let me know if you have any questions.