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; } } }

When I searched in Jira's advanced filter, I faced a problem.

Ozlem Kesici

Hi,

For example:

Without any filtre I have totally 2925 matching issues.

project=Mailing has 932 matching issues.

component = banner 12 matching issues. (Project named YS, includes banner component.)

project != Mailing AND component != Banner has 826 matching issues.

But mathematically,

2925-(932+12)= 1981

and this solution does not match the result of project != Mailing AND component != Banner filter.

Did I make a mistake or is this a bug?

Accepted answers

All comments

Nic Brough -Adaptavist-

Possibly - needs a bit more investigation - could you try the following filters and see what numbers you get?

project != Mailing
component = Banner
component = banner
component != Banner
component != banner

(I'm suspecting case sensitivity and the components in your projects not quite matching, but I'm not sure)

Ozlem Kesici

project != Mailing 1994 matching issues.
component = Banner 12 matching issues.
component = banner 12 matching issues.
component != Banner 827 matching issues.
component != banner 827 matching issues.

Nic Brough -Adaptavist-

Thanks, that neatly rules out my first thought :-(

But it doesn't look at all right. component = banner (12) + component != banner (827) does not add up anywhere close to your total number of issues, so there's something else happening here.

Next, I'd try

project = Mailing (so we know how many are in there)
project = Mailing and component = banner (Obviously, if you haven't got banner as a component in there, you don't need to worry about this one)
project != Mailing (to get a current accurate count of the reverse)

Ozlem Kesici

Hi,

First of all, I would like to thank you very much for the time and effort.

I tried also :

project = Mailing 932 matching issues.
project = Mailing and component = banner no matching issues.
project != Mailing 1994 matching issues.

Jobin Kuruvilla [Adaptavist]

I don't think it is a bug. Basically, you are doing an AND on 2 NOT operations.

project != Mailing 1994 matching issues

component != Banner 827 matching issues.

An AND of both will return only the common issues between them. ie. 827 issues.

What happens when you try this?

project != Mailing OR component != Banner

I would expect 1994.

Ozlem Kesici

Yes, you're right. When I search for

project != Mailing OR component != Banner ı get 1994 matching issues.

But, should I not use the formula that I used before ? Let me check...

2925-(932+12)= ( 2925 - 932) + (2925- 12)

=("Without any filtre"- "project=Mailing") + ("Without any filtre"- " component = banner ") =NOT( "project=Mailing") + NOT( " component = banne ")

= NOT( "project=Mailing") AND NOT( " component = banne ")

= project!=Mailing AND component != banner

Jobin Kuruvilla [Adaptavist]

You are confusing yourself. It doesn't work that way.

project!=Mailing AND component != banner

It finds all issues not in Project (1994) and all issues not with component Banner (827). Then takes the common issues in both the results since the operator used is AND. It combines both when OR is used.

The key thing is, you are doing AND on negation (!).

onkeldom

Your just using the wrong numbers:

component != "JIRA Core" : 1158

That's every issue in the whole system, where the component is NOT set to "JIRA Core".

Now to check, how much issues in a certain project do NOT have this component:

project = "Atlassian Products" and component != "JIRA Core" : 56

56 Issues in the project Atlassian Products have NOT set the component.

Now to check, if all other issues in the system with the component NOT set to "JIRA Core", except those in the Atlassian Products project, sum up correctly, you do a search like:

project != "Atlassian Products" and component != "JIRA Core" : 1102

Works like a charm here ...

Ozlem Kesici

But, in my situation the related component is not included in Mailing Project.

(The Banner component is included in another project.) Does this condition make a differenece?

Ozlem Kesici

I think the issues is about EMPTY components

When i search for "component != Banner" 828 results fetched but

when i search for "component != Banner or component is EMPTY" 2916 rows fetched.

As far as i understand, component != Banner also filters not EMPTY ones.

Ramiro P

I think these one is the problem. It has something to do with the operator.

As far as i understand, component != Banner shows every issue with any component different from Banner, including the empty ones.