Limit Automation Usage: Which trigger should I use to identify duplicate issues?

[Meredith]

I have a project that has issues created by a third party. The third party was producing duplicate issues and the bug was fixed. However, the org wants an automation that identifies and cancels a duplicate issue if created.

I created the automation outlined here: Solved: How to avoid duplicate issues being created by an ... (atlassian.com)

However, this runs every time an issue is created. With Atlassian limiting automation usage based on subscription level, I need to reduce the amount of times that this automation runs. Is there a way to have a trigger that identifies a duplicate BEFORE running? TIA!

[John Funk · Accepted solution]

Hi Meredith,

Turn the rule into a Schedule Trigger instead of Issue Created. Then have it run a couple of times a day or however often is critical to find the duplicate. 

[Meredith]

Great idea, thanks, John!

[John Funk]

You are welcome! If that helped you, can you click on the Accept Answer button above to close this one out? Thanks!