Unable to set a field in a cross project cloned ticket based a value imported during cloning

[Nathan Yam]

I have an automation rule (below) set up to clone a ticket one service desk project (A) to another service desk project (B). Along with the cloning, values in certain fields in the cloned ticket in project B are to be set exactly the same as they are in the original ticket (in project A). For this question, I will focus on the field FSD Priority.

Project B has it's own priority field called CISD Priority, which is empty when a ticket is created as a result of the above automation, but the FSD Priority field will have a value from the cloning. So I have automation rule set up in project B (below) to set the CISD Priority field in the event that a created ticket has an empty CISD Priority field and the FSD Priority field has a certain value. 

However, for some reason the automation in Project B is never triggered when a ticket is created due to the top automation. I have tried removing the "If: Linked issues present" condition from the Project B automation as well as switching the order of the 2 "If: all match" conditions within the branch but that didn't fix the issue. 

Anyone can point out where I went wrong? 

[Trudy P Claspill · Accepted solution]

Hello @Nathan Yam 

On the Rule Details page for the second rule make sure you have checked this box:

[Nathan Yam]

That did the trick, thank you!