-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
5.4.7
-
5
-
Severity 3 - Minor
-
1
-
Issue Summary
The Due date field saves the date like the following in the instance database:
2023-08-22T00:00:00Z
In the issue view, this shows correctly as Aug 22 (e.g., for a user in GMT-7 and the instance timezone set to GMT-7), but the Customer Portal view for that same user shows as Aug 21 instead of Aug 22. 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
- Set the Due date field in a ticket in the issue view
- Configure the Due date field to be visible
- View My requests page and toggle the Due date field
- Observe that the field shows a different date than what it shown in the issue view (e.g., issue view shows Aug 22, but the Customer Portal shows Aug 21)
System parameters
jvm.system.timezone: Etc/UTC
jira.default.timezone: America/Vancouver
user.timezone: Etc/UTC
The user is using the jira.default.timezone
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
Ensure that both "Default user time zone" and JVM timezone match or use a date picker custom field.
- is duplicated by
-
-
- Gathering Impact
-
- is related to
-
-
- Closed
-
- links to
- mentioned in
-
Page Failed to load