Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


I'd like to configure a quick filter to show all issues related to any of several different componen

I'd like to configure a quick filter to show all issues related to any of several different components. For instance the components are named like AB1, AB2, AB3, CD1, CD2, CD3, EF1, EF2, EF3, etc. Can i write a JQL "OR-statement" that includes all components that have AB or CD or EF in their names or do I have to list all components i full name?

1 answer

0 votes
Tim Kopperud
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Oct 07, 2023 • edited

Hi @kusum kishore 

I don't think this is possible without a third party app. I have done something similar using third party, but not on cloud though. Since components doesn't support "~" you must use the full component name. 

A workaround might be to add a label (or you might setup a hidden customfield) on the issue using automation. Automation can fetch e.g., the first two characters of the component name, and apply it as a label. Then you can make quick filters on labels instead.

Example on the rule below.




You will need a rule triggered by Field value changed (component). The rule above is ment as a simple guide about the idea, and you would need to adjust it for your exact need.

If you go for this approach make sure you filter correctly when you do you first bulk update (adding the labels on existing issues).


Forgot to mention that you need to take care in case an issue have multiple components. You might filter away component names you don't want a label for. In smart values you can do string comparisons to make sure only wanted components are prosessed.


Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events