JQL query to get unresolved bugs on some date.

[Misha]

Hi, I'm trying to get issues with type bug, that was open on some date. I don't want to relay on the status field, because it can change, so I decided to use resolution field instead.

I created the query:

issuetype = "Bug" and resolution WAS empty ON "2020-06-16" //(today)

but it selects only around 30 issues in my project, while the query, that should do the same for today:

issuetype = "Bug" and resolution is empty

selects 400+ issues, and that's correct.

I checked the issues from the first query, and looks like that query only selects the issues, for which resolution field was changed back to empty (kind of reopened issues), and don't select issues for which resolution field was initially empty (just open issues).

So, the question is how to correctly get the issues with empty resolution field on some date.

[Misha · Accepted solution]

For those, who are looking for a solution of that issue, i found the alternative way of getting unresolved bugs on some date, but it's a little bit more complicated, and uses resolutiondate field. Here is the query:

issuetype = "Bug" and (created <= "2020-06-16") and (resolutiondate >= "2020-06-16" or resolution = unresolved)

 Looks like that query is working fine for that case, but, anyway, if somebody knows why the history search query is not woking like expected, or knows how to make it working, please let me know.

[Andy Heinzer]

Hi Misha,

Sorry to hear about this problem.  I believe the behavior you have found here is actually a bug in regards to how Jira Cloud is looking up resolution values (or lack of values) via JQL.  We are tracking this over in JRACLOUD-70967.

Sorry again for the inconvenience, but I'm glad to see that you have found an alternative method to find the issues you want here.

Andy

[John Funk]

Hi Misha - Welcome to the Atlassian Community!

Is this a Next-gen project or a Classic Software Project? 

[Misha]

Classic Software Project

[John Funk]

I get the same results. I am submitting a support ticket with Atlassian to see what they say. I will report back here.  :-)

[Misha]

Thanks.

[John Funk]

Well, a bug has been filed. :-)

You can "vote" by clicking on this affects my team link. You can also become a watcher. 

https://jira.atlassian.com/browse/JRACLOUD-74652

[John Funk]

Hi @Misha - Just a quick follow-up here. Can you accept one of the answers so we can close this out for future users?

[yahacom]

+1

[Jorden Van Bogaert]

Hi @Misha 

Which version of Jira are you running?

Kind regards
Jorden

[Jorden Van Bogaert]

Never mind, I thought it was running fine on my version, but it's also acting out, only in the opposite way... I have more results for query 1 than query 2 :p

[Misha]

@Jorden Van Bogaert I believe i'm using Jira Cloud, so it should be the latest version.

[Jorden Van Bogaert]

Ah sorry, didn't see the tag yet. We'll on server I'm seeing weird results as well.