Issue Summary

The Due date field saves the date like the following in the instance database:

2021-10-19T00:00:00Z

In the issue view, this shows correctly as Oct 19 (e.g., for a user in GMT-6 and the instance timezone set to GMT-5), but the portal view for that same user shows as Oct 18 instead of Oct 19. This seems to be due to the portal trying to account for the user's timezone and subtracting the timezone offset from the entry in the database.

Steps to Reproduce

1. Set the Due date field in a ticket in the issue view
2. Configure the Due date field to be visible
3. View My requests page and toggle the Due date field
4. Observe that the field shows a different date than what it shown in the issue view (e.g., issue view shows Oct 19, but portal shows Oct 18 or Oct 20 depending upon the customer's time zone)

Expected Results

The portal view shows the intended date.

Actual Results

The timestamp from the database is taken into account and the timezone offset for the user viewing the ticket is subtracted from that timestamp resulting in the incorrect day being shown.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available.