Issue Summary

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

2024-08-02T00:00:00Z

In the issue view, this shows correctly as Aug 2, but the portal view for that same user shows Aug 1 instead of Aug 2. This seems to be due to the portal using 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. Go to Requests in the portal and add the Due date column
3. Observe that the field shows a different date than what it is shown in the issue view (e.g., issue view shows Aug 2, but the portal shows Aug 1

Issue view

Portal

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

Add the due date field to the Request form, it should show the correct due date: