JQL filter to display overdue issues

[Juan Manuel Ramos Taboada]

Hi Community,

I am trying to find a JQL filter to display all overdue issues at any given time. I have tried using the "resolutiondate" field (because it shows you when a user has moved the issue in the Kanban Board to the "Done" status) and comparing it with the "Due Date" field in order to do so, but so far unsuccessful. 

Can anybody help me, please?

Thanks in advance!

[Nic Brough -Adaptavist- · Accepted solution]

Welcome to the Atlassian Community!

What is "unsuccessful"?  And why are you comparing the due date when trying to display overdue issues?  All you need to find overdue issues is look for "resolution is empty and due-date < now"

[Juan Manuel Ramos Taboada]

Hi Nic,

What I meant by "unsuccessful" is that I have not been able to find the correct JQL filter using the combination of "resolutiondate" and "Due Date" fields.

I am using the "due date" field because it is the date when a certain issue is supposed to finish.

I am looking at your proposed JQL. When you say "resolution is EMPTY", does that mean that the issue is currently sitting at any status except "Done"?

[Nic Brough -Adaptavist-]

What do you mean by combination of dates?  Why are you looking at the resolution date?

The definition of "overdue" means "gone past the due date", which you can do with "due-date < now". 

The reason I added "resolution is empty" to it is that I suspect you have no interest in issues that have been dealt with.  There are going to be a lot of closed issues that are now past their due-date, even if they were closed before them.  Done issues should have a resolution, open ones have an empty resolution.

[Dean Capp]

Likely means he wants to see the Due Date and the Resolution Date fields to see how long past the due date a ticket was resolved. A simple request that I have myself, but alas, Atlassian???
I want to see Due Date (Target Completion Date) and Resolution Date (Actual Completion Date) per ticket. This is a common reporting metric to determine team's performance.  Ideally, Jira could calc the diff as excel does not handle due date after completion date i.e. team were efficient at resolving a ticket before it was due (and I am sure Google sheets has the same issue)