We're using two Custom Fields and trying to filter for their results. However when I run this filter (below) Jira returns results for Epics and Tickets that don't even have these Custom Fields in their form. I've tried reading about Custom Variables and how they work in filters but I haven't been able to find anything that would indicate why this filter wouldn't work. Does anyone have any insight to why this filter below would return thousands and thousands of results that do not qualify for the filter's requirements.
("AdOps Issue Type" = Trafficking OR "Yield Issue Type" = "IO Change")
(Also, I've never asked a question on here before so if there's anything else I could provide, let me know.)
Thanks - Matt
I had to read this a couple of times, as "issue type" has a distinct structural meaning, and putting it in field names can be confusing. However, I do know what you've done.
You have a couple of *fields* called "AdOps Issue Type" and "Yield Issue Type". Your query is only asking about these fields, so it's returning all the issues with those field values set.
The problems you have with this are:
There's a simple test:
Hi Nic - you're test worked! By showing the columns for 'AdOps Issue Type' I found that the default value for this custom variable was set to 'Trafficking' instead of BLANK, even though that custom variable was not being used in many of the projects. Thank you for the suggestion, time, and help - I really appreciate it.
Hello, Community! My name is Gosia and I'm a Product Manager on Jira Server and Data Center here at Atlassian. Since 2002 when we launched our public issue tracker, jira.atlass...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs