Community Announcements have moved! To stay up to date, please join the new Community Announcements group today. Learn more
×Hello community.
I would like some help on how to identify duplicate activities based on the summary field or a custom field.
I would like some insight into how to implement one of the two solutions mentioned above.
I greatly appreciate your help in advance.
Atlassian Cloud already detects similar work items on our site using Rovo (Atlassian AI).
I haven't explicitly turned on anything, yet it is there. Now, I tried to find this in the official Jira documentation, but this post is the best I found:
If I were you, I'd try to get more info about this.
Hello @Orlando Cando
You must first defined exactly what you would compare between items to identify that the new one is a duplicate of an existing one.
Would it need to have an exact match on the Summary?
What type of custom field would you use? How would it get set during the item creation process so that it could be used to find if other duplicate issues already exist?
Regarding #2:
You could create an automation rule that uses the Work Item Created trigger.
You could add a Lookup Work Items action to execute a JQL to see if there are any duplicate issues based on the criteria you define for identifying a duplicate.
You add a condition to check if the Lookup returned any results.
You add an action to transition the issue if the previous condition indicates results were returned.
I am not aware of a method for identifying duplicates and blocking the issue from being created. There may be such a method which I haven't discovered.
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.