Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
  • Community
  • Q&A
  • Jira
  • Questions
  • Setting a Filter for all tickts accross all JWM projects with a component that has "social" as term

Setting a Filter for all tickts accross all JWM projects with a component that has "social" as term

Isabelle Jakubeit
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
March 31, 2022

Hi there,

I would love to set a filter for tickets (existing and future ones) with a component that have a special term included.

Example:

Components in JWM projects might be 

- Social DOOR

- XTR social

- social Planet

 

This means, selecting them manually is not a solution, or I would have to adjust the filter every time a new project is created. This I am doing right now - but I would love to have a "automated" filter setting that does not have to be changed manually to guarantee that the results show all tickets that exist. 

 

Can anyone help. I really tried most of JQL ideas I could find.

Thanks a lot!

bella

2 answers

2 accepted

0 votes
Answer accepted
Nic Brough -Adaptavist-
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.
March 31, 2022

The search for fields that have options (like components) does not have a text search of the component names.  So, no, there's no way to do this, you're going to have to add each new component name to your filter when people create a new component.

The request makes me think that you might be using the field incorrectly though.  Maybe the project should consider changing their component list so that it reads

  • Social
  • DOOR
  • XTR
  • Planet

Then people can add a "social" component alongside the main component name.  

Or ask people to label things with social (which you could even automate - when component-x added to issue, add label social automatically)

Isabelle Jakubeit
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 4, 2022

We are using the component to add valid information regarding a team or a main technology and it automatically adds the assignee to it. 

This is a must have information for our tasks (we are working mainly with JWM on our Agency Clients and used Asana before). So using labels seemed to be to random and not unique enough. Also using labels would mean to use a mix of individueal and global automations where we do have a daily limit with 500.

We wanted a kind of norrow process for this selection. But at that point I did not know that filtering would be such a problem.

 

I might think about changing our component names to Social, SEA, SEO and so on, without mentioning the company. This would only affect dashboards where we than neet to displan keys to se the project where a ticket is coming from as the component won't show anymore. I will discuss that with my collegue. 

 

THANKS. 

0 votes
Answer accepted
Jack Brickey
Community Champion
March 31, 2022

Hi @Isabelle Jakubeit , So as you probably have already observed you cannot use the approximate operator with component unfortunately. One thing you could potentially do is set up an automation rule to add a label that copies the value from component. Then you could use JQL with the approximate operator on labels - labels ~ social. Just a random idea here. You might also move away from Component altogether and create a custom text field.

Suggest an answer

Log in or Sign up to answer