I'm trying to set up a JQL to show all of the service desk tickets which have been Answered, Deployed and Closed in the last 7 days. This needs to include Bugs, Feature Requests and Questions from the client.
I have used the following query which I believed worked:
project = TKSERVICE AND status changed to (Done, Answered, Closed, Deployed) after -7d
However there are request which I know have been closed which are not showing on the list, I can only see questions but the bugs and feature requests that have the status changed seemed to be missing.
I've tried other more complex queries where I state the the Issue Type but I then seem to get a list of 1000 results but can't get the date filter to work.
Any help would be appreciated!
I'm not good with JQL, so I can suggest an alternative solution from my team – Issue History for Jira. It allows you to filter tickets by the date range. Just select appropriate dates from the calendar – and you can monitor all past status changes.
Hello @rob_vandersteen
Are you filtering issues in a Company Managed project or a Team Managed project? Are you filtering a Software, Business, or Service project?
If you make more constrained filters, say for CHANGED TO just one status at a time, do you get all the issues you expect?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
So it's a service project which we use to manage service desk tickets for one of our clients.
I did a more focused set of queries and it returned a lot more results but for some reason also included the tickets which had been resolved beyond 7 days so I had about 1000 results instead of the 6 or 7 I was expecting.
If I manage to get the date range right I don't get all of the types I'm expecting and when I manage to get all the types I'm expecting the date range doesn't seem to work and I get 1000 results.
Rob
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
So far I have not been able to recreate the issues you're seeing, but I am working with a Free instance that has a very small (<100) total issue count across the instance.
This is a difficult problem to debug without access to the actual (or comparable) data set.
Can you tell us the details of the "more focused" queries you are trying?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
So I basically stated what the project was and then broke the state down by each individual one status = deployed OR status = Closed etc and then at the end of the query I tried to set the date to -7 days by using status date changed but that didn't work
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Is the following similar to a more focused filter that you tried?
project=X and status CHANGED TO "Closed" AFTER -7d
And did that give you more issues or fewer issues than you expected?
If I did not accurately represent your filter, please paste a specific example of the actual filter you used when creating a more focused filter.
If you are missing issues that you expected to get, can you show a History entry for such an issue that shows that it was changed to the specified status within the specified time frame?
If you are getting an issue you think you should not, can you provide an image that shows the full status change History for such an issue?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If I use the following string
project = TKSERVICE AND status changed to Closed AFTER -7d
I don't return any results at all and I know I have at least one bug that was reported and Closed in the last 2 days.
The results seem to pick up everything except Closed and Deployed
I'm not sure how to show the history but this is what I can see on the bug
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.