nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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

Chaya Reddy nag

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..

Accepted answers

codelab expert

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:

http://blogs.onresolve.com/2010/03/audo-duplicate-search-in-jira/

I hope this will help you!

All comments

codelab expert

Please check also this interesting articles:

http://blogs.onresolve.com/2010/03/audo-duplicate-search-in-jira/

I hope this will help you!

Chaya Reddy nag

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..

Jon Starbird

Chaya,

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

thanks,

Jon

Harry Chan5

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.

Jon Starbird

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

Dinesh Dhinakaran

any updates on this

hrzadnn

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!

Jon Starbird

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.

Jon

Jon Starbird

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.

Jose Ramirez

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.

Tony Nerd

Is it automatic ?

Avidan Izaks

What JQL are you using?

Simon Wong_5l1oyg

It wasn't available when the OP asked the question, but you can now use the new Lookup Issues action under Automation https://support.atlassian.com/jira-software-cloud/docs/automation-actions/#Automationactions-Lookupissues. You can run a JQL to identify if there are already existing records with the same Summary field as the new issue. If so, cancel (or deleted if you'd like) the new issue automatically.

See the example below.

SHADOW_y8z94h

In which version was this "new action" added? I have a full paid version of Automation 7.2.3 and I do not have a "Lookup" action.

SHADOW_y8z94h

OK, this "Lookup" action is only available for the cloud version, and it looks like we can wait another 10 years, adding for the server version

Simon Wong_5l1oyg

@SHADOW Yea, we're on Cloud. Sorry to hear that the feature isn't on Server. 😓