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

Jira filter for resolution = Unresolved does not include all issues.

Paul Brand_mksq5m

There is a difference in the following two filters:

resolution = "\"Unresolved\""

and:

resolution = Unresolved

The first only finds the issues where the resolution is specifically set to "Unresolved".

In the database these jira issues have "11000" in the resolution field, which is the id of the Unresolved resolution in the resolution table.

The second finds the issues that are newly created where the resolution field is untouched.

In the database these issues have "NULL" in the resolution field. Unresolved is then selected because its default.

I would expect to find all the issues with the second filter.

Am i doing something wrong?

Accepted answers

Paul Brand_mksq5m

Thomas,

I did not know it was custom. The table for resolutions in the database contains "Unresolved" with id 11000. I guess this should not be there than right?

All comments

Thomas Deiler_db00h3

Dear @Paul Brand,

I repeated your search queries. The first filter returned

The value '"Unresolved"' does not exist for the field 'resolution'.

Searching with either

resolution = "Unresolved"

resolution = Unresolved

returns the same amount of issues. Is it possible, that you Jira has a custom resolution named Unresolved?

So long

Thomas

Paul Brand_mksq5m

Thomas,

I did not know it was custom. The table for resolutions in the database contains "Unresolved" with id 11000. I guess this should not be there than right?

Ollie Guan

Hi @Paul Brand,

Have you ever tried the following JQL?

resolution is EMPTY

Paul Brand_mksq5m

Yes. This also does not include the issues where the resolution field is "11000" in the database

Thomas Deiler_db00h3

Dear @Paul Brand,

Jira replaces a resolution of NULL (resolution is EMPTY) with the word Unresolved. Of cause you can create a custom resolution named same, but it really does not make sense.

So long

Thomas

Nic Brough -Adaptavist-

Correct - this is breaking your system because it means "resolved". Jira does not know or care what any resolution option's label is, the rule is "field empty/null = unresolved, field with any value = resolved"

I would first change the name of "unresolved" to "broken resolution - do not use", that will fix your searching, and give you an easy way to spot issues that might be broken.

Then go through your screens, making sure that only "transition" screens include resolution, and those are only used on transitions that go from an open status to a closed one (usually not-green colour to green), and also check that "reopen" uses a post function that says "clear resolution"

Finally, you will want to have a look at the list of issues with the broken resolution - any that are in a non-closed status should really be fixed, blanking out the resolution.