Automation logic help

[Priyanka Agrawal]

Could someone help me achieve the below using automations : 

1. When there is an incoming webhook, it creates an issue in a project ABC with type Event and copy the payload data to description.
2. Search for issues in project XYZ where cfname = cfname in the payload
3.  Add comment to the searched issue in XYZ project.
4. Close the Event ticket that was created in ABC in step 1.

[Valerie Knapp]

Hi @Priyanka Agrawal , thanks for your post.

Have you tried to create something already? We are more of a troubleshooting / assistance forum than a place where we would create something for you based on your requirements. That is typically the work of an Atlassian Consultant / solution partner and is usually paid.

Please have a go at creating the automation you want and test it. When you have error messages, please share some screens of what you tried and we will help you fix it yourself, more than tell you, to get this, you need to do that.

Best wishes

[Priyanka Agrawal]

Hi @Valerie Knapp , Thank you for replying.

Yes, I have come here after trying lots of things myself.

Here is the automation I've built and is not working as expected.

The automation should terminate if no issue is found in project XYZ. It should only close the issue created in project ABC if an issue with the matching criteria is found in XYZ. Otherwise, the ABC issue should remain open, as it serves as a log for automation failures."

[Bill Sheboy]

Hi @Priyanka Agrawal 

Adding to Valerie's suggestions...

Please also include and review the audit log details with your rule to help understand what is not working as expected.  From what you posted we can see:

• The rule stops if no results are found in the Lookup Issues result, and so the if / else block is not needed; just run the steps, and...
• Why are you using the REST API to perform the issues searches when additional Lookup Issues actions could be used?  Are these issues all in the same Jira Sites?
• The way you structure the checks for the other issues could be done such that the rule halts when they are found, similar to your first Smart Values Condition on the Lookup Issues results
• Finally, rather than using a JQL branch to access the newly created issue, instead try using the related issues branch to Most Recently Created Issue

Kind regards,
Bill