Issue fields information sync in Jira Cloud

Christian Isaza

Hello, everybody,

I administer a Jira Cloud instance for my company and I was asked to see the possibility to Sync some issues linked to others across multiple projects in the same instance.

I have been trying to get an automation rule working with no success and would like to get your help on this. Thanks in advance.

The information I have:

We have a "source" project which has many issues linked to other issues in other multiple projects. The targets. The issues in the source are linked as "Blocks" to the Target's issues.

The request is that everytime fields as Status, Assignee, Comments and Due Date are updated, changed, added, deleted, those same changes are reflected from the Source issues to the Target's issues.

At the moment, it would be only issue to issue, and not issue to many.

I have tried the rule as you can see in the screenshots. Including changing the Edit issue action from current issue to trigger issue, and the condition from linked issues present directly to issue fields condition Link is not empty.

Additionally tried the FOR to be set as all issue operations, edit, create, and nothing seems to trigger although I see in the audit logs sometimes that the rule runned successfully or that runned with no actions taken.

Nothing seems to work, so I would like to get your help on how to resolve this.

Thanks.

 

Also tried "For all issue operations" and specific operations as well, but the result is always the same.

Robert DaSilva_a432as

Hey @Christian Isaza , welcome to the Community!

If I understand your challenge correctly, you're looking to do the following:

1. You want to watch all issues inside your Source Project, Project A, for any changes to the following fields:
   1. Assignee
   2. Due Date
   3. Status
   4. Comments
2. Any time one of those fields changes in any way (either data is added, deleted, or updated), you want to copy the change to a linked issue. Of note, that issue is linked as "Blocks" on the source issue.

 

If I've got that right, then your automation rules are close! You're missing the "For: Linked Issues" action branch. Here's a screenshot of what your automation should look like.

A couple things to note:

• You'll want to use the "For: Linked Issues" condition block
• I would recommend adding in conditions before the "For" block to restrict this to the project that triggers these changes
• Both projects should be "Company Managed" and sharing the same Statuses. It's important they share the same back-end Status IDs. The best way to accomplish this is to ensure both projects are using the exact same Workflow, or ideally Workflow Scheme.
  • If the statuses are different between the projects, the transitions may pose a challenge.
  • In the workflow, you will want to make sure any status can transition to any other status. If the transition cannot resolve, then the automation rule will not properly execute.
• You may want to consider locking down the permissions on the destination projects, so that only the Automation for Jira app can make changes, and your trigger project ends up being the "source of truth"
• When selecting the values to copy, you want to select "Trigger Issue", as this will copy the data from the issue that started the automation, in your case, from the triggering project.

Let me know if that works!

Robert