Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Prevent Duplicate Issues Creation

How to prevent duplicate main issues based on Summary in Jira in Issue Created through Script Validator

1 answer

0 votes

The pseudo-code for this validator is:

  • Look at the summary for the current issue
  • Run a search for that string in the summary
  • For each returned issue, read its summary and look at how close a match it is to the new one
  • Return false (and a friendly error message) if one or more results are too close to it

There's some example code for validators over at which can help you with the basics of a validator, and is good for running a search.

This makes sense. However, how would we avoid performance issue? Because originally, it is just a create operation, now it is search and create. If there is a script that creates tickets in my Jira very frequently, the performance will be horrible.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Service Management

JSM Jira Automation: How to Send SLA Breached Notifications

Hi Everyone, In   this tutorial,  we will show you how you can monitor an SLA, and send notifications before or after the SLA has been breached.   SLA Threshold Trigger The SLA t...

647 views 5 12
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you