Hi Atlassian Community,
Apologies I'm still somewhat a beginner on the automation side of things for Jira!
I'm looking to add an automation rule to our Jira Service Desk in order for it to pick up any duplicate tickets based on the summary field contents and then to transition the ticket into a resolved/cancelled status.
Example from my screenshot:
I have 3 tickets created which are under the same "request type" and contain the same summary (in this case summary = "123456789") with the status "waiting for support". I want the initial ticket (PSP-70) to be the original and any others the come through after with the same summary field (not pre-defined if possible) to be moved to resolved/cancelled status.
Below is what I have currently for the Automation rule.
It looks up the issues fine, but I think where I'm stuck at is the compare part of the rule...
I'm wanting the flow to be like below:
-Lookup issue- If Jira Ticket:
-Compare- Then check other tickets that are with the above same criteria:
-Actions- If those match then:
If anyone has any advice on this it would be greatly appreciated :)
Thanks Jono
Hello @Jonathan Lewis
Can you try this one in lookup issue jql part ?
project = "PSP" and issuetype = "Service Request" and status = "Waitting for Support" and resolutiondate is empty and summary ~"\"{{triggerIssue.summary}}\""
Normaly, that will cancelled all new ticket with exact same summary
Thanks for your response, this one worked perfectly, appreciate your response on this :)
Screenshot to show confirmation on the Audit log:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Jonathan Lewis Glad that helped you :) , in this case you can maked as accepted response
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.