nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Combining filters not working

Oh_ Me Too_

Hello

I have 2 filters that work fine separately, but when i try to combine them they don't. One filter keeps getting ignored.

My filters are as follows:
Filter 1 = project1 OR project2 AND != Component A
Filter 2 = Epiclink = Epic1 AND duedate <= 4w

I have tried every conceivable way to do this:
filter = "filter 1" AND filter = "filter 2"
filter = "filter 1" OR filter = "filter 2"
filter = "filter 1" | filter = "filter 2"

I have tried changing the order, putting everything in parenthesis both together and separately, everything in parenthesis both together and separately followed by another AND or OR to either filter.

What I'm trying to do is see everything in 2 projects except Component A and only things in Epic1 that is within 30 days of being due.

Are these just incompatible filters or something else? Filter 2 is the one that doesn't want to work. Thanks in advance for any help.

Accepted answers

Oh_ Me Too_

project in ("Workload Automation and Data Transfer", "Messaging Platform") AND component != "ITSME-Support/Maintenance" AND status not in (Done, Closed) AND issueFunction not in issuesInEpics("issuekey=WADT-137") OR issueFunction in issuesInEpics("issuekey= WADT-137 ") AND duedate <= 30d AND status not in (Done, Closed) ORDER BY updated DESC

All comments

Sachin_q0v8o8

Hello, can you try below filters

filter1: project in ("project1", "project2") AND component != componentname

filter2: project in ("project1", "project2") AND "Epic Link" = epiclink AND duedate <= 4w

or project in ("project1", "project2") AND "Epic Link" is not EMPTY AND duedate <= 4w

now to combine both saved filters:

filter = filter1 OR filter = filter2
or
filter = filter1 AND filter = filter2

Oh_ Me Too_

Ah, thank you for the suggestion! It didn't occur to me to try to change or optimize the original filters.

Unfortunately it didn't work, I'm getting the same results after i made the above changes to the original filters and verified that they work.:

filter = filter1 OR filter = filter2 -result is only filter 2 works

filter = filter1 AND filter = filter2- result is only filter 1 works

Sachin_q0v8o8

Thank you for trying out the filters I shared. Can you share the JQL that you are using.

Oh_ Me Too_

You bet, I appreciate your help!

Filter 1 = project in ("Workload Automation and Data Transfer", "Messaging Platform") AND component != "ITSME-Support/Maintenance"

Filter 2= project in ("Workload Automation and Data Transfer", "Messaging Platform") AND "Epic Link" = WADT-137 AND duedate <= 4w (i also tried just "Epic Link" = WADT-137 AND duedate <= 4w since it gives same results)

and i tested then:

filter = filter1 OR filter = filter2
(filter = filter1) OR (filter = filter2)
(filter = filter1 OR filter = filter2)
((filter = filter1) OR (filter = filter2))

and then all again with AND instead

Andrew Morin

Okay I think I got what your original ask was. I am not sure which direction you were looking at for the due date. I have it looking back 30 days but you can adjust that...

project in ("Workload Automation and Data Transfer", "Messaging Platform") AND resolution = Unresolved OR (component is EMPTY OR component != "ITSME-Support/Maintenance") AND duedate <= -30d AND issueFunction in issuesInEpics("project = WADT AND issuekey = WADT-137") AND resolution = Unresolved ORDER BY key ASC

Oh_ Me Too_

Hi Andrew

Thanks for taking a look at this. Unfortunately its still ignoring the 30 day till due date portion. But there is something interesting going on with your example though...

project in ("Workload Automation and Data Transfer", "Messaging Platform") AND resolution = Unresolved OR (component is EMPTY OR component != "ITSME-Support/Maintenance")

ran by itself doesn't work at all.. it pulls back everything in the system though JQL acknowledges that its a proper query. Yet when ran all together with the due date half as you gave it, then this first portion works but then the due date half isn't working.

duedate <= -30d AND issueFunction in issuesInEpics("project = WADT AND issuekey = WADT-137") ran by itself works fine. This duedate portion of the filter, no matter how we tried it so far stops working once combined with other filters.

So I don't know if that's indicative of anything, but I find it interesting that you found a filter format that only seems to work if combined with further filters. If anything it shows some weird idiosyncratic behaviors as they relate to combining filter strings giving me hope that a perfect combination might be out there to make this work.

Oh_ Me Too_

BTW- I also tried these filters separated into their own and then combining using filter = filter1 AND filter = filter2. It does the same thing, ignores the duedate filter.

Oh_ Me Too_

Now I'm thinking that our Jira is just all jacked up. Now suddenly I can't even get basic filters to work right.. like (status != done ) or status NOT IN (Done, Closed).. same if using resolved or anything else.

I'm going to have our projects reindexed to see if that helps at all.

Oh_ Me Too_

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira-core

jira-core-server