Details
-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
1
-
Minor
-
Description
Issue Summary
Updating a date-time field type through bulk update doesn't respect user's Timezone instead it shows 'Default user time zone' from Jira setting on bulk edit page, and converts that time per 'User profile timezone' setting.
Steps to Reproduce
Refer to the below scenarios to reproduce the problem:
| Jira default user time zone | User Profile timezone | Timestamp on DateTime type field | Observations |
|---|---|---|---|
| It should be equivalent to GMT-7 per daylight saving because Jira doesn't auto converts the DST | GMT+5:30 | Jun 03, 2023, 2:30 AM | During bulk operations time selected 'June 02, 2023, 2:00 pm';
|
| It should be equivalent to GMT-7 per daylight saving because Jira doesn't auto converts the DST | PST8PDT(GMT-7) | Jun 02, 2023, 2:00 PM | correct time. Because both Jira default user settings and 'user account' settings are correct. No need to convert. |
| (GMT+03:00)Amman | PST8PDT(GMT-7) | Jun 02, 2023, 4:00 AM | The time visible on Jira ticket after the bulk update is in PST. But the timestamp 2nd June 2023, 2:00 p.m. selected during bulk update was in (GMT+03:00 =Amman). Time visible on Jira issue is converted to (GMT-7 = PST). Refer to the conversion: 2:00 p.m. Thursday, in Amman, Jordan is 4:00 a.m. Thursday, Pacific Time (PT) |
| It should be equivalent to GMT-7 per daylight saving because Jira doesn't auto converts the DST | GMT+3:00 | Jun 03, 2023, 12:00 AM | Calendar selects the timestamp from Jira default settings. This means 2nd June 2023, 2:00pm is the time from Jira default setting(GMT-7 = PST).The time visible on Jira tickets is from user profile which is GMT+3 = AMMAN. Refer to the below conversion: 2:00 p.m. Thursday, Pacific Time (PT) is 12:00 a.m. Friday, in Amman, Jordan |
Expected Results
Bulk edit operation should consider 'User Profile timezone' while editing 'Date-Time' field type.
Actual Results
Bulk edit operation considers 'Jira default user time zone' while editing 'Date-Time' field.
Workaround
The possible workaround is to set the 'Jira default user time zone' matching 'User Profile timezone' but this is not feasible if customer has global userbase.
Attachments
Issue Links
- is related to
-
JRACLOUD-80353 [Tracking in issue links] Date time format issues (system, custom, all views and inputs)
- Gathering Interest