Automation to find duplicate issues

[Rasa]

Hi 

I want to create problem from duplicate event (ITIL Process).

So i need to find duplicate issue that are create. (Like lookupissues in cloud)

Can someone help me please...

[Dick · Accepted solution]

Hi @Rasa 

You first need to define what you rank as a duplicate. Which fields are important and in what way should the comparison between two issues on that field yield you a yay or nay identical?

Do know you can start a string comparison with ~ it reads as "like".

Try to put your query into normal words first. Syntax of the automation comes later.

Hope we can help you once your question is a bit more clear,

Dick

By voting for helpful posts and marking answers to your question, you're helping people with similar questions find a solution more quickly. Sharing is caring applies to knowledge as well :)

[Rasa]

I want to write an automation which start when an issue create 

When issue create automation search and find issues with simailar summary like triger issue and then create a problem with the same summary and link the all similar issues.

In cloud i can search for thos issues with "lookup issues " in automation but in datacenter i can not find enything for this search.

[Dick]

Hi @Rasa 
Your question has become a lot clearer due to your added text. 

• We're talking about an on create trigger
• The comparison field is summary
• LookupIssues are available in datacenter, so that's hopeful

Can you post a picture of the cloud automation, so we can adapt that to datacenter Jira?

Hope this helps,

Dick

By voting for helpful posts and marking answers to your question, you're helping people with similar questions find a solution more quickly. Sharing is caring applies to knowledge as well :)

[Rasa]

[Rasa]

I want anything like this automation in datacenter

The picture is on cloud version

[Dick]

Thank you Rasa,

The problem is in your JQL where you construct the lookup issues:

There is no need to escape the quotes: 

"{{triggerissue.summary}}"  suffices. 

Hope you get it to work now,

Dick

By voting for helpful posts and marking answers to your question, you're helping people with similar questions find a solution more quickly. Sharing is caring applies to knowledge as well :)

-------------------------------------------------------------------------------------------------

example at datacenter Jira

[Rasa]

There is not lookupissue action in jira automation on DC as second line in picture you send.):

[Dick]

Well, I'm sorry to have to disagree with you, but I'm really quite sure we're running the datacenter version of Jira. But maybe it's a different version than yours:

We're on long term version 9.12.11. 

Maybe you're running a different version of Jira?
You can find that data on: Administration - Applications - Versions & Licenses

Just trying to help you here

Dick

By voting for helpful posts and marking answers to your question, you're helping people with similar questions find a solution more quickly. Sharing is caring applies to knowledge as well :)

[Rasa]

Thank you so much dear Dick

---

The puzzle is solved. 

My jira version is 9.2:)

[Bill Sheboy]

Hi @Dick 

An FYI about your statement:

There is no need to escape the quotes: 

"{{triggerissue.summary}}"  suffices. 

Using the CONTAINS ~ operator like this"

summary ~ "{{triggerIssue.summary}}" 

Will fuzzy match on any of the words in the summary, in any order, and may include other words.

When a more exact match is needed, the exact phrase syntax is used by adding the escaped quotation marks:

summary ~ "\"{{triggerIssue.summary}}\"" 

That could still have additional matches, with leading or trailing text around the match text.  For example, if the trigger issue summary was "this story is about squirrels", matches could be on the following:

• this story is about squirrels
• here is some leading text and this story is about squirrels
• this story is about squirrels and here is some trailing text
• here is some leading text and this story is about squirrels and here is some trailing text

When a true, exact match is needed, the rule will also need a smart value condition to test "equals" between the values.

Kind regards,
Bill

[Rasa]

Hi Bill

Your suggestion was very useful. 

Thanks. 

[Dick]

Thank you @Bill Sheboy for clarifying.

I'm happy to see that it acts the same as in the Google search bar. (only need to remember a single syntax)

For @Rasa the usage of the quotes would depend on her needs. (exact match: use quotes, fuzzy match: do not use quotes).

It all comes together happily,

Dick

[mararn1618 _secretbakery_io_]

Hey @Rasa, I just wanted to link an article I recently wrote about how to write an automation rule to manage duplicate tickets.

• Jira Using Automation Rules to manage Duplicate Tickets 

It's very similar to the accepted solution, but I think other people could benefit from the additional detail and illustrating images in that article.

I hope that's ok.