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

Filter is broken

Michelle Harris1

Issues I know should show up in my filter do not. They are there when I do not filter out any resolutions, but if I filter out duplicates and won't fix, issues that are "Unresolved" are not showing up. If I search for the one issue I know is not showing up but should using id=... then it only shows up if I use "\"Unresolved\""versus just plain Unresolved. But when I remove the id=... parameter, even when I search on "\"Unresolved\"", my issue doesn't show up.

In the simple search, it adds Unresolved without the escaped quotes and then my issue doesn't show up. So that's a bug that should be easy to fix. But why oh why is my issue just not showing up in my filter at all?? Please help!

Accepted answers

Nic Brough -Adaptavist-

Three possibilities

Your filter is not doing what you expect because you're misunderstanding how they work (there are a few quirks that make them less than intuitive sometimes)
Your filter is referring to data that is doing something odd
Your index is broken

To debug all those cases, could you tell us exactly what your filter says, and tell us about the issue that should be shown. We need to know what the values of any fields the JQL is using are - for example if you're searching for "project = ABC, unresolved, and due date > now", then tell us the issue key, the resolution and due date. Finally, when your issue is shown in a list, is the ID struck out at all?

In this case, pay particular attention to the resolution - what you've said is suggesting a certain problem, but I can't be sure..

All comments

Nic Brough -Adaptavist-

Three possibilities

Your filter is not doing what you expect because you're misunderstanding how they work (there are a few quirks that make them less than intuitive sometimes)
Your filter is referring to data that is doing something odd
Your index is broken

In this case, pay particular attention to the resolution - what you've said is suggesting a certain problem, but I can't be sure..

Michelle Harris1

Hi Nic - I was able to get it to show up by using BOTH "\"Unresolved\"" AND Unresolved in the filter. There is indeed some bug that is making the issue (Video-4210) not show up when I use simple search and it just uses Unresolved. The filter I used (that accurately picks up Video-4210) is now:

project in (ACE, News, VIDEO) AND issuetype in (Bug, Epic, Story) AND resolution in ("\"Unresolved\"", Unresolved, Fixed, Incomplete, "Cannot Reproduce", Completed, Passed, Failed, "On Hold", "Working As Designed", "User Error", "Forwarded to other team", "Unit Tested", "Pushed to QA", "In Development", "Pending QA") AND created >= 2013-04-01

Can you let me know where the other quirks are so that I don't lose any issues? We are using a filter to track all stories in a huge redesign and it's critical that we don't lose track of any issues due to a bug with the way Jira filters work.

Thanks!

Nic Brough -Adaptavist-

I'm not sure why you are using two "unresolved"?

Nic Brough -Adaptavist-

Ok. Can you do two things now

As hinted before, go to the issue view of video-4210 and look at the area where resolution normally appears. What exactly do you get for the resolution (or confirm that it does not appear at all)
Look at your search - is video-4210 struck out?

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud