Is there a way to perform a query and EXCLUDE anything that has a ticket linked of a specific type?

[Roberto Benites]

I want to query a project for all tickets and exclude any tickets that already have a ticket linked to them that is of the TEST type.

[Charlotte Santos -Appfire-]

Hi @Roberto Benites

I’m Charlotte, a support engineer at Appfire and I’m here to help you.

Unfortunately, natively, you’ll not be able to do it dynamically.

In the app where my team works, JQL Search Extensions for Jira, you can use this query to get all tickets except the ones that have a Test linked to them: 

issue not in linkedIssuesOfQuery("issuetype = Test")

Please contact our support if you have any other questions about this query.

We’ll be happy to help you!

[Hannes Obweger - JXL for Jira]

Hi @Roberto Benites

to the best of my knowledge, this isn't available in Jira out-of-the-box; see (and consider voting for) this feature request: https://jira.atlassian.com/browse/JRACLOUD-63414.

the only native way I can think of is to use Jira Automation to check your issue's issue links and write data into a custom field, which you can then use to filter your issues in JQL. I haven't actually tried this myself, so I can't guarantee it would work.

Alternatively, if you're open to solutions from the Atlassian Marketplace, there's a number of apps that can help with this. E.g., your use case would be easy to solve in the app that my team and I are working on, JXL for Jira.

JXL is a full-fledged spreadsheet/table view for your issues that allows viewing, inline-editing, sorting, and filtering by all your issue fields, much like you’d do in e.g. Excel or Google Sheets. It also comes with a number of so-called smart columns that aren’t natively available, including the linked issue types.

This is how it looks in action:

As you can see above, you can easily sort and filter by your issues' linked issue types, and also use them across JXL's advanced features, such as support for (configurable) issue hierarchies, issue grouping by any issue field(s), sum-ups, or conditional formatting.

Any questions just let me know,

Best,

Hannes