Jira Automation - how to create a rule to block creation issues with the identical summary

[Jiri Pik]

I am unable to get the conditions right. 

The trigger is Issue created but am not sure how to get the condition "if the issue's summary is already present in the project" work.

[Jack Brickey · Accepted solution]

you can't prevent the creation but you could create post-creation automation to close as duplicate. Automation works post-creation not pre-creation.

[Jiri Pik]

Thank you for the answer.

So the trigger is Issue created?

What is the condition? I have tried JQL with Project = XXX and it did not work.

[Bill Sheboy]

Hi @Jiri Pik 

Yes, the trigger would be Issue Created...and due to potential timing issues you might want to add a re-fetch so the item is fully loaded.

Your JQL would check for any issues in your project which have the triggering issue's summary.

Perhaps something like this.

• Trigger: Issue created
• Action: re-fetch
• Action: lookupIssues, with JQL like (note the ~ and the quotation marks)
  • project = myProject AND summary ~ "{{issue.summary}}"
• Advanced compare condition:
  • First value is {{lookupIssues.size}}
  • Condition is Greater Than
  • Second value is 1
• Action to close and comment on the duplicate, as @Jack Brickey noted

Best regards,

Bill

[Jiri Pik]

@Bill Sheboy : THANK YOU