JQL operators for the Component/s System field are unavailable

Question

Hi Community, I tried to filter all components containing the word "Global" in their names, but this is impossible because this field does not allow all operators like "Summary," for example, or some other fields in Jira. Why is that so, and how can I achieve the desired result easily? If a component has two or more words in its name, this is crucial, but currently not possible. What doesn't work: component in ("*global*") component ~ "global" component = "Global*" component CONTAINS "global" component LIKE "_ _ global%" component ~ "^global .*" Thanks for your help in advance. Best regards, Jurica

Marc -Devoteam- · Answer

Hi @Jurica Petricevic

The component field doesn't work with the operators you are mentioning.

Hannes Obweger - JXL for Jira · Answer

Hi @Jurica Petricevic

I don't think that the component field supports text-based filtering natively. The only thing I can think of is to use Jira Automation to write the component name(s) into a text-based custom field, and filter this field - but obviously, this will add a fair bit of complexity to your system.

Alternatively, if you're open to solutions from the Atlassian Marketplace, you'll find options there. There's a number of apps that either extend JQL by additional functions, or use different, more powerful filtering techniques altogether.

As an example, my team and I work on an app in which your use case would be easy to solve, 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 advanced features, including support for (configurable) issue hierarchies, issue grouping by any issue field(s), sum-ups, or conditional formatting - as well as the ability to filter any issue field via text search.

This is how it looks in action:

(For more advanced use cases, you can also use regular expressions.) Once you've narrowed down your list of issues, you can work on your issues directly in JXL, trigger various operations in Jira, or export your issues with just one click.

Any questions just let me know,

Best,

Hannes