Jira sorts and filters due date incorrectly

[Rikard_Berg]

I have a new install (one month) of Jira core. I have 5 users, 30 issues, one project and a simple workflow. I use English and Swedish.

When I search for issues with overdue due dates it returns issues not overdue (due <= "0").

(image from the dashboard with a simple overdue filter. The date was 18th march.)

Also, which seems to be related, when I sort by due date, it sorts it incorrectly.

Or are there other parameters/factors I have missed?

It should just be a simple date sort, right?

Could there be some wrong with due date storage? I have no clue where to begin debugging.

As you see, the view date is changed from default - but I have also tried default date format.

This post comes from my original post here.

[Rikard_Berg]

I think I have found it.

I had changed the javascript.picker format for incorrectly for a short period of time which made it save the data in an incorrect format for some issues - but not others.

Setting the date/time in look and feel + advanced setting x4 correctly seems to have fixed it. Updating the due date on some issues might be needed.

[John M Funk]

Ah! That would probably do it. 

[Andrew Laden]

Check you make sure you aren't sorting on another field first. Jira allows sorting on multiple fields. (ie sort on field a, for all issues with the same value a, sort on field b)

[John M Funk]

Hi Rikard,

Maybe try Due <= now()

[Rikard_Berg]

Unfortunately that did not help. Is there some know issue with the default way Jira queries overdue dates? 

[John M Funk]

Maybe try the field duedate:

duedate <= now() and project = ABC

[Rikard_Berg]

No difference - tried "project = FS AND duedate <= now()"

I suspect there is something with date format in the system. Don't know how to proceed though.

[John M Funk]

Maybe do a re-index since you are on server? If that doesn't fix it then I would open a support ticket with Atlassian. 

[Rikard_Berg]

I have already re-indexed. Unfortunately we only have a starter license and there seem to be no way to get support for this issue.

[John M Funk]

Maybe try hardcoding the date just to see if that works.