Creating automation between 2 spaces

Question

Hi,

In Team-Managed space i'm trying to create an automation that will do as follows:

when a work item is created in this space (the team managed) it will also automatically open a ticket in a different space (company managed space) simultaneously.

Up to this point all good - the problem is that the ticket in the company managed space is opened under a certain status, a default one, and i'm trying to make it automatically open at a different status.

When I try to branch the automation and pick the "Transition" option so it will transtion to the status I want, it won't let me pick the statuses of the company managed space, only the statuses of the team managed (the original).

Somebody succeeded with controlling tickets between different spaces?

Trudy P Claspill · Answer

Hello @Eliya Sarfarti

There can be two problems involved here.

The first one is as mentioned by other responders - the rule Scope. To do more than Create an item in another project the rule Scope has to include both the source project and the other project. Multiple-project Scoped rules can be created only by Jira Admins from the Global Automation interface. If you are not a Jira Admin you will need to get help from a Jira Admin.

The second possible problem is that the rule may get confused about the status that you want to use. I have read in previous post that rules that are scoped to include both Team Managed and Company Managed projects have had issues with getting values that are available from all the scoped projects. I'm not sure if that is still an issue. I did a very simple test myself and did not encounter that problem so maybe it has been resolved.

John Funk · Answer

Hi Eliya,

You need to add the Company-managed project to the scope of the automation rule. You need to go to Settings > System > Global automations

Search for the rule, then modify the details to be a multi-space rule. Then add in both of the spaces.

Nikola Perisic · Answer

Hello @Eliya Sarfarti

This is because the scope is only limited to that team-managed project. In order to see more statuses, you need to create the global automation rule instead.