Jira Cloud legacy automation works but not modern automation

[Michael Saeed]

Hi, so ive been trying to make an automation using the new automation tool but i cant get it to work, however if i setup the same rule in legacy this works.

I have an automation from project A when an employee stops in our business, then it automatically creates a ticket to project B service desk to inform the team at B there that a user that has stopped, in doing so i noticed that the request type is empty in project B when automation creates this ticket from project A.

So i create a new automation in project B to change the request type, however nothing happens, nothing in the log that indicates it has failed, but if i create the same rule in legacy this works. I prefer working in the new modern automation.

This is the rule in project B that doesn't work

This rule in project B legacy works

This is the rule from Project A that creates a ticket in Project B

[Trudy Claspill]

Hello @Michael Saeed 

The issue in Project B is being created by the execution of a rule.

The rule in Project B to update said issue is not getting triggered.

Look at the Rule Details of that rule in Project B. Confirm this box is checked.

[Rudy Holtkamp]

Hi @Michael Saeed ,

First of all, you need to be a Jira product admin (or get help from one).

Your rule should be created as global automation rule. After you created and published your rule, go to the Rule details > Scope. And set it to Multiple projects > project A and Project B

No go to the component where you create the ERP Service Request issue. After that component you need to add a Branch rule / related issues and choose 'Most recently created issue'.

In the branch you create the component Edit request type and choose the correct one.

That is it.

[Trudy Claspill]

That is one solution...