Find duplicate Jira issues with AI
Compare a reported symptom with existing issues and decide whether to add useful context to a ticket or create a distinct record.
To find duplicate Jira issues with AI, describe what actually happened. A blank invoice export and a button that never opens the invoice may sound alike in a title, yet they are different observations. The triage-issue guide extracts useful search terms and compares existing Jira records with the new report.
Look beyond matching words. Product version, affected area and the status of an earlier fix can change the decision. A new detail may belong on an existing ticket; evidence of a distinct failure deserves its own record. If the relationship is uncertain, document that uncertainty rather than silently treating it as a duplicate.
What it does
- Search a project for similar reports
- Compare the symptoms and affected version
- Identify details that distinguish two cases
- Draft a comment for an existing issue
- Prepare a new ticket when the issue is distinct
Install and use
- Install the skill, connect Atlassian Rovo MCP and authorise access to the relevant Jira project. Commenting or creating requires suitable write permission. Remove unrelated sensitive details.
- Ask “Find earlier reports of an empty invoice export. Compare the evidence and suggest whether to comment or open a new issue.”
- Check candidate records and choose the intended action before verifying the resulting ticket or comment.
FAQ
Source
Made by Atlassian. Original skill: triage-issue, published on GitHub under the Apache-2.0 licence.
View on GitHub