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

Two dimensional filters

Lorenzo Ferguson

I have what I think is an issue with two dimensional filters.

The total count for the rows (counting left to right) seem to accurately reflect the total.

However, the count for each column (top to bottom) does not add up to the correct total count.

Have I found a problem with the filter or is this how it's supposed to work?

See my screenshot below.

Thanks, MicrosoftTeams-image (4).png

Accepted answers

Hana Kučerová

Hi @Lorenzo Ferguson ,

it't not a bug, it's a feature :-). This is how it should work - numbers in the last column/row don't represent the total count, but how many issues have the attribute set.

I would recommend you to click on all the numbers - it will show you the JQL, which is used to count the number.

If I take the last row and the second column - number 1 - it means how many issues have the Severity = 0-Blocker (it doesn't matter which components they have). The fifth column then - number 15 - how many issues have the Serverity = 3-Minor.

It seems strange, but basically the numbers are so, because a lot of issues have more than one component.

The numbers for the rows equals to the total count, because all the issues propably have the severity set and it has only one value in each issue.

Nic Brough -Adaptavist-

Note the word "unique" in that last row's name.

You have chosen to display a list of issues by Status and Component. Status is working fine, as you expect and is intuitive, but Component is not necessarily a single value field. So, an issue can have many components, and that's what this gadget is showing you.

Taking the very first column (as it is a perfect example of the most simple case) - status = 0-blocker, which gives you that column. You then have

Component: DMCLI : 1
Component: WIFI : 1
Total unique issues : 1

This tells me that you have one single issue with the components DMCLI and WIFI on it. If you click the 1 on the bottom line, Jira will tell you which issue it is, so you can check that.

All comments

Hana Kučerová

Hi @Lorenzo Ferguson ,

it't not a bug, it's a feature :-). This is how it should work - numbers in the last column/row don't represent the total count, but how many issues have the attribute set.

I would recommend you to click on all the numbers - it will show you the JQL, which is used to count the number.

It seems strange, but basically the numbers are so, because a lot of issues have more than one component.

The numbers for the rows equals to the total count, because all the issues propably have the severity set and it has only one value in each issue.

Nic Brough -Adaptavist-

Note the word "unique" in that last row's name.

Taking the very first column (as it is a perfect example of the most simple case) - status = 0-blocker, which gives you that column. You then have

Component: DMCLI : 1
Component: WIFI : 1
Total unique issues : 1

This tells me that you have one single issue with the components DMCLI and WIFI on it. If you click the 1 on the bottom line, Jira will tell you which issue it is, so you can check that.

Lorenzo Ferguson

Hello @Hana Kučerová ! Thanks for your feedback. After doing more investigation on this, I confirmed exactly what you said! I was happy to report to my manager and executives that my filter is correctly displaying the information based on the components being used.

Lorenzo Ferguson

Hello @Nic Brough -Adaptavist-

Your correct. I was in the middle of a different task -- when I was asked about this yesterday. So while I researched it myself I also reached out to the community for help.
I'm happy we all came to the same conclusion.

Now I just need you guys to fix the issues we've reported with v8.4.1 :-)

tejashree avinash aringle_nfkfnd

@Lorenzo Ferguson : I had question, add the same gadget in my project dashboard to get the label counts used in the particular project , i was interested to know what does Total unique issue represent ? Are they issues having multiple label value associated with them or are these the total count of the table.

Nic Brough -Adaptavist-

I can't explain it better than I did last January - it's the same answer.

tejashree avinash aringle_nfkfnd

@Nic Brough -Adaptavist- : the query states project= Projectname,

Now i have changed the query to project= porjectname and lables !=None

Welcome!

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

Quick Links

Find more posts tagged with

server

jira

jira-server