I am trying to create a filter to see all the unresolved tickets between 2 dates using DURING:
resolution was Unresolved DURING ("2019/10/01", "2019/10/25")
But this returns an empty result, and I am sure they were some that were unresolved.
I have also tried:
resolution was EMPTY DURING ("2019/10/01", "2019/10/25")
and
resolution was NULL DURING ("2019/10/01", "2019/10/25")
And they both return no results.
What am I doing wrong?
I agree, Payne's solution should work ... yet it doesn't. There must be something odd with my JIRA.
Marianne, wouldn't your answer omit the tickets that were not changed in between the period ("2019/10/01", "2019/10/25"), ie tickets that were unresolved and stayed unresolved?
So I am still stuck, my work around is to look for tickets in all statuses and excluding all different types of resolutions.
status was in (Backlog, open, ready, "In Progress", "To Review", "To Branch Test", "To Release Test", Resolved, closed, "To Do", "To Test", "Product Review", "Ready to Deploy", "To Tech Review", "Awaiting Test") during ("2019/10/01", "2019/10/02") AND resolution was not in (done, duplicate, "Won't Do") during ("2019/10/01", "2019/10/02")
I need to put the
status was in (Backlog, open, ready, "In Progress", "To Review", "To Branch Test", "To Release Test", Resolved, closed, "To Do", "To Test", "Product Review", "Ready to Deploy", "To Tech Review", "Awaiting Test") during ("2019/10/01", "2019/10/02")
if not JIRA gives me tickets that were created after the period I want!
resolution was EMPTY DURING ("2019/10/01", "2019/10/25")
works just fine in my server instance, though I see that you're using a cloud instance.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Another thought is perhaps your index is invalid? Perhaps try reindexing?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
How about a little of both?
project = XXXX AND resolution changed TO (done, duplicate, "Won't Do"') during ("2019/10/01", "2019/10/25")
OR
(project = XXX and createdDate <= "2019/10/25" and resolution is EMPTY )
Search for any issues that were resolved and search for any issues created before your end date that were/are still unresolved.
you could query them in two different sets, but I think that combined, it should give you the results you are looking for.
project = XXXX AND resolution changed TO (done, duplicate, "Won't Do") during ("2019/10/01", "2019/10/25") OR (project = XXX and createdDate <= "2019/10/25" and resolution is EMPTY )
We should start with the simplest query to get you a results set, then add on. if you try them separately and if you are still getting no results, it may be a Jira config issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This may help: If you're trying to see what was in an "unresolved" status during a certain period, then you're trying to see items that are now resolved.
Depending on what resolutions you use, this should be a pretty simple lookup. You will have to know the possible options to execute in the query.
Resolutions are typically something like Done, Completed, Duplicate, etc
project = XXXX AND resolution changed TO (Completed, 'No Longer a business need') DURING ("2019/10/01", "2019/10/25")
The logic here is that if the status changed to some type of resolution 'n this period, then it had to change from an UNRESOLVED status. The resulting set will tell you what was unresolved in that same timeframe.
Please let us know if this works for you. I Do think Payne's solution is probably more comprehesive, and simpler.
Good Luck,
Marianne
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.