I would like to know if it's possible to check for duplicate "Summary" field value when a new issue is created?

We have HelpDesk sending ticket to mail handler. Some times, HD sends same ticket 3,4 times. Which are created as duplicate tickets in JIRA.

I would like to compare new "summary"(JIRA issue field) field(HelpDesk ticket#) with existing fields in workflow function.

If it's same, I would like to delete the issue as it's created. So, only first time it creates issues not after that.

Thanks for you help..

7 answers

1 accepted

0 votes
Accepted answer

No, there doesn't exist a JQL which will help you. But there exists a plugin (SuggestiMate for JIRA) on the market place which helps you to find duplicates: https://marketplace.atlassian.com/plugins/com.suggestimate

Please check also this interesting articles:


I hope this will help you!

Thank you again for this. I saw both these plugins. But these good when a new issues is created manually..

But we have Mail handler to create issues. So, I was thinking is there any way to check in the workflow function ?

Thank you for your information..


did you ever resolve this? We have a similar need for issues coming in from a third party system.



Hi, you could use Script Runner to create a custom validator for the Create action to achieve this. In the code, check using JQL if the same summary exists and reject as required.

Good idea. I have the pluign already, don't know why I didn't think of that!

any updates on this

Hi @Chaya Reddy nagella and @J Starbird did you guys resolve this thing? Can you tell me how to solve this, maybe without those Suggestimate plugin.. is it possible? Please let me know.. I appreciate your answer.. Thank you!! Cheers!

We ended up getting the Suggestimate plugin which works really well. The nice thing about the plugin is that while you're creating it, before you submit, it shows you possible dupe summaries.

The field they use can be added to other screens as well so even on old issues when you're grooming your backlog you can see possible dupes.

You could do all of that in code but then you have to maintain that code yourself so every upgrade will mean you having to work on it, this is why we bought the plugin.


Sorry I should have read the rest of the old post. For the Third Party incoming programmatic issues we did not get a solution. For now our Support folks just bring up Jira and do searches before they submit the new issues through their program.

My Solution, because I have this problem as I'm typing this answer, is to create the JQL filter for the timeframe and project, in which duplicates were created. I then sort by 'Summary' and look at the matching summaries. I then purge the duplicates.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Jan 08, 2019 in Jira

How to Jira for designers

I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...

1,123 views 4 9
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you