Jira lets teams link issues as clones, duplicates or blockers, but finding all of them from the issue navigator usually means clicking through issues one at a time. CelesteCS JQL Extensions adds dedicated functions for exactly these three relationships, plus a way to spot suspicious duplicate data before it turns into a linked duplicate in the first place.

Following a specific relationship

• issue in jqlxClonesOf("key = APP-100") – every issue cloned from APP-100.
• issue in jqlxDuplicatesOf("project = SUP and status = Open") – open duplicates of the matched issues, useful for a weekly support triage.
• issue in jqlxBlockersOf("project = APP and status = \"In Progress\"") – whatever is blocking today’s in-progress work, a natural stand-up query.

Catching duplicate data before someone links it manually

Sometimes the same request comes in twice under different summaries, with nothing linking them yet. jqlxIssuesWithDuplicateFieldValues flags issues that already share a field value someone would expect to be unique:

• issue in jqlxIssuesWithDuplicateFieldValues("project = SUP and status != Closed", "Customer Reference") – two open tickets referencing the same customer ticket number, a likely duplicate report.

The mirror function, jqlxIssuesWithUniqueFieldValues, is handy for a data-quality sweep in the other direction – for example confirming that every issue in a migration batch really does carry a distinct external ID before the import is trusted.

All of these accept the same jqlQuery-first pattern as the rest of the plugin, so they combine freely with ordinary JQL clauses and with the other jqlx-prefixed functions functions described in the Functions reference.

Try it in your own Confluence: CelesteCS JQL Extensions for Jira on the Atlassian Marketplace – free trial for Data Center.

JQL Extensions saves you time? A review on the Marketplace helps other teams find it.