When using a quick filter in backlog view more issues are shown than when quick filter is turned off

[Allen D]

Using the same board, in the same project. All quick filters off shows 827 issues total. If I turn ON a filter to show only bugs, a see the correct lower number of bugs (60) but I see a higher total number of items (1458). Shouldn't the filtered version be showing 60 of 827?

[Jack Brickey · Accepted solution]

ha! one would think. I just did a quick test on one of my projects. I'm using scrum and here is what i see....

Active Sprint:

• 3 issues are displayed as they are still in To Do status
• 1 of the issues is a Bug

Backlog:

• count shows "33 issues"... so technically there are 36 issues in the backlog view (Backlog + Sprint)
• none of the 33 are bugs

I have a "bugs only" filter and if select I get:

Active Sprint:

• 1 issue displayed as it is a bug

Backlog:

• no issues displayed
• count show 0 of 35 issues visible...my theory here is that this count is accounting for the two issues in the Active Sprint that are not bugs. if this is correct I find that odd since w/o the filter it does not account for them. Why wouldn't the Active Sprint show "1 of 3 issue visible"

In any event your delta is huge and inexplicable by me. Can you share your board and filter JQLs?

[Jack Brickey]

Also, your QFs appear different than mine. yours seems to be a drop down while mine is a list across the top. I didn't think drop down still existed. hmmmm

[Bill Sheboy]

Hi,  Jack...  I believe the quick filter drop-down is now just a toggle for displaying the list.  It appears more relevant when you have enough quick filters to wrap to additional screen rows.

[Jack Brickey]

Thanks Bill. Where is the setting?

[Bill Sheboy]

I haven't found a setting... it appears to auto-magically detect the number/width of quick filters, and so then wrap to the next line.

[Allen D]

The quick filter automatically turns into a drop down when I have about 30 filters.

Quick filter: type = Bug

Board Filter: project in ("Project1", "Project2", "Project3", "Project4", "Project5") AND type not in (subTaskIssueTypes(), epic) ORDER BY Rank ASC

[Jack Brickey]

i'm suspicious that the multi-project aspect of the filter is somehow at the root of the anomaly. Just a guess. The only way to figure it out for sure is to do a bunch of troubleshooting tests.

[Bill Sheboy]

@Allen D  I found this defect which seems related to the symptom:

Applying a quick filter at the backlog changes the count of issues on backlog section

https://jira.atlassian.com/browse/JSWCLOUD-17957

[Allen D]

Ahh, I missed that somehow when trying to find an answer. Thank you @Bill Sheboy