Incorrect Results On A Query

A query incorrectly returns issues where Status = Open and Resolution = Unresolved after having been previously resolved. 

The below statement returns issues with a resolution of unresolved although it specifically should not. 

project = QM AND resolution != Unresolved AND status != Closed

Is this a bug?

 

2 answers

try

project = QM AND resolution is not empty AND status != Closed

The displayed "unresolved" on your view screen is a sort of translation of an empty resolution. So this is not a Bug.

Edit: added the "not"

0 vote

Ah, hang on, no, it could be an issue with your data.

Concentrate on the resolution field.  Can you go into the list of global resolutions and just check that there is NO resolution called "Unresolved" on the list? 

If there is, you have a structural problem to unpick because someone has broken your Jira.  We need to rule that out first.

Edit - apologies, I posted at the same time as Udo.  You do need to be aware of that too - your workflow should be setting the resolution via screen or post-function, and clearing it on re-open (have a look at the default workflow to see how that handles it).  So "resolution is empty" is the correct search as Udo says.

Hi Nic, I can see the option Unresolved. So you mean I have to set the Resolution to "None" instead of "Unresolved" in the post function? (Closed to Open or Reopen)

If so then Udo's query will work?

If you use the update issue field post function simply leave the new value empty (don't enter anything). That will set the resolution again to Unresolved (with empty database field). My original query will not work since it should be "is not empty". I'll update my answer accordingly

If you use the update issue field post function simply leave the new value empty (don't enter anything). That will set the resolution again to Unresolved (with empty database field). My original query will not work since it should be "is not empty". I'll update my answer accordingly

Sorry, mixed up update issue field and update issue custom field post function. Yes, set it to "None"

Hi Guys, I will make the changes and test

Ah, good, Udo is on it :-) Yes, it's "none" in the post function, that will stop your data from going wrong. However, you MUST remove that "unresolved" resolution because it is breaking your data as far as the humans are concerned. If resolution is set to anything (e.g. fixed, duplicate, unresolved, penguin, - really does not matter what the value is), then Jira sees the issue as closed. Having "unresolved" as a resolution is nonsense because the issue is, by definition, resolved because that is set on the issue.

This makes 100% sense

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,308 views 14 20
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot