Automation of verification, cloning, and status changes between two projects

[heldergrune]

Hello everyone, how's it going?

I need the following help:

Today I have two projects, A and B, and I need that when a story in project A is moved to the testing queue, it checks if there is already an identical story in project B. If so, then only the story in project B should be moved to "in queue."

Now, if there isn't an identical story in project B, then the story from project A should be cloned into project B, and the story in project B should be related to project A.

I've tried several ways, and the most I can do is clone, but I can't implement this verification. I have access to global rules if necessary. Can someone help me, please?

[Aron Gombas _Midori_]

To me, your use case sounds like syncing issues between the two projects.

It may or may not doable with automation rules, but let me note that there are 3 popular apps built for this specific purpose! You may also want to try those.

[heldergrune]

Thank you, Aron. I can't acquire another application at the moment and need to do this using only automations. I believe the issue is not synchronization, but rather refining the rule I'm trying to use, since I've just started using them and don't know much about how to structure it.

[Trudy Claspill]

Hello @heldergrune 

Welcome to the Atlassian community.

How do you determine that an issue in Project B is identical to the issue in Project A?

Please provide screen images that show the entire rule you have constructed.

[heldergrune]

Hello Trudy, thank you.

Today I'm doing it this way; the first branch works properly, the second one doesn't. I've also tried other ways, directly with if-else, but I was not successful.

[heldergrune]

Note: I can handle the entire part of creating in project B and linking, now I just need the first part of checking if it exists and changing the status.