Why are Due Dates on my Assignee's filter one day off from the actual Due Date?

[Matt Merola]

This issue seems to have recently started occurring, sometime in the last week or two it started. 

Due Dates are set on the issue, but when the Assignee look at their "my open issues" filter, the Due Dates are exactly one day behind. It seems like it could potentially be a time zone issue, but I'm not sure how thats possible. 

The reporter of these issues is setting the due date, and they are on Pacific time. The Assignee is looking at these due dates in a filter, and they are on Eastern time.

Is anyone having this issue? Anyone have any suggestions?

[Trudy Claspill]

Hello @Matt Merola 

Is this the built-in "Due date" field, or an additional custom field named "Due Date"? Note that the built in field has a lower case "d" on the "date" part of the name.

If it is an additional custom field is it a date picker field or a date/time picker field?

Have you gotten screen images of the users' Account Preferences settings to confirm the timezone preferences they have set?

Is the second user seeing the discrepancy when they view the details of the issues in Jira?

Have you looked at the actual value of the field in a given issue to confirm what it really is?

[Cynthia Freeney]

Greetings @Trudy Claspill

A colleague recently reported a similar issue as described by @Matt Merola.  The due dates that he sets for issues are off by a day when he views them from the "All Issues" list.   However, when viewing the issues, the dates appear as specified.  I was able to duplicate this behavior and observed that when I create a filter the “Due date” appears as it is specified in the issue.  We are using the built-in “Due date” field and are both located within the CT time zone. Values are assigned to the “Due date” field via a date/picker.  This issue seemed to began to occur about a week or so ago.   Are there any additional insights that can be provided? 

[Trudy Claspill]

Hello @Cynthia Freeney 

Welcome to the Atlassian community.

I have not been able to recreate this issue.

I encourage you to contact Atlassian support directly for more assistance. And it would be wonderful if you report back here what you learn.

[Matt Merola]

Still have not found a resolution to this issue. More details:

• This is the built in Due date field. 
• The user sees the accurate Due date when looking at the issue details
• The user sees the date one day behind when looking at it through a filter
• The user is in Denver (MST), the reporter is in Los Angeles (PST), and the system default time is NY (EST)
• The issue has only been observed for a few weeks, seems to have been timed with a system update of some kind. Was there anything changed related to timezones recently?

[Trudy Claspill]

@Matt Merola 

I encourage you to contact Atlassian support directly on this.

They know the details of updates that have been deployed.

Additionally, because you have a Premium subscription I believe you have access to Release Tracks, which could mean that updates are deployed to your environment in a different time frame than others.