Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


How Delete Issue with the same name

I did the integration Zabbix+Jira and now I've automatic Issue from monitoring, but when some issue is trigged twice in Zabbix we have a duplicate issue in Jira.

It is possible to delete that duplicate issue? 




May the automatization be with you !!

2 answers

2 votes
Angélica Luz
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Oct 01, 2020

Hello Pedro,

Thank you for reaching out to Atlassian Community!

Testing on my local site and also checking some similar cases, I found a workaround that may help automatically delete duplicated tickets. 

It's not possible to do using only one automation rule, but two. One will link both duplicated issues and the other rule will delete the duplicated one. 

If the duplicated tickets are all created in one project, please create the automation on Project settings > Project automation (Classic) or Project settings > Apps > Project automation (Next-gen).

First automation rule:

When: Issue created

For JQL summary ~ "{{triggerIssue.summary}}":

Screen Shot 2020-10-01 at 14.10.42.png

Then Link issue to:

Screen Shot 2020-10-01 at 14.11.17.png

Screen Shot 2020-10-01 at 14.11.50.png

Second automation rule:

When: Issue linked

Screen Shot 2020-10-01 at 14.12.37.png

For Linked issues:

Screen Shot 2020-10-01 at 14.13.03.png

Then Delete issue:

Screen Shot 2020-10-01 at 14.13.51.png

Note: Before saving this rule, go to "Rule details" and select the option "Check to allow other rule actions to trigger this rule. Only enable this if you need this rule to execute in response to another rule."

Screen Shot 2020-10-01 at 14.23.47.png

After that, publish the rule.

For all new issues, the duplicated ones will be automatically deleted.

Please, give it a try and let us know how it goes.


Hello Angélica !!

Tks for replay.

I followed the instruction but something happens, I still have duplicate tickets in my project.

take a look...





There is some way to block a new issue with the same name? 

Like this: Check if the issue has the same name and blocking before creating a ticket in the project?

If this not possible maybe there is a way to merge all the duplicates issues in just one ticket.


Pedro Schawirin

Angélica Luz
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Oct 09, 2020

Thank you for the details, Pedro.

The automation will work for future tickets. 

You can uncheck the option "Only include issues that have changed since the last time this rule executed", so the automation will run for existing tickets. 

This option appears on Branch rule / related issues on the first automation rule.

Screen Shot 2020-10-09 at 10.47.09.png

Currently, it's not possible to merge tickets, it's possible only to link them. There is a feature suggesting this option:

Please, take your time to test and let us know how it goes.

i just wanted to thank you that it saved my life!

Like Angélica Luz likes this

This is an old thread and I am trying to get this running for mine as well. I have it setup exactly as above but getting this error:
Error searching for related issues. This is most likely because the following issues don't have a related issue of the type you specified. Try narrowing your search to only include issues that contain links to related issues:

EOB-89: "((summary ~ "Task: [Offboarding] Send shipping label to return hardware James Bond Due: 2023-01-27") AND (key != EOB-89)) AND (project in (10008))" - The text query 'Task: [Offboarding] Send shipping label to return hardware James Bond Due: 2023-01-27' for field 'summary' is not valid: probably your range query is incorrect.

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events