-
Bug
-
Resolution: Fixed
-
Low
-
None
-
17
-
Severity 3 - Minor
-
4
-
Summary
When we set the Date Time Picker default value to the current date, it will show fine in the JIRA issue create screen but in the Service desk portal it uses GMT timezone. Once the issue is created through the portal, it would not convert back to the user time zone but instead, it will remain with the time the default value has selected.
Environment
- JIRA Service Desk Cloud
Steps to Reproduce
- Set the Default user time zone of the instance to i.e. GMT-5;
- Set the default value date in a Date Time Picker custom field to the current date.
- Go to the Service Desk portal and try to create an issue in the request type that has the date time picker field with the default value set as the current time.
Expected Results
- Date time picker field shows the correct time
Actual Results
- Date time picker field shows the time in GMT timezone
Workaround
None at the moment.
- mentioned in
-
Page Failed to load
[JSDCLOUD-8076] The default value in the date time picker field uses GMT instead of the user time zone in JIRA Service Desk portal
two and a half years in the backlog...not sure if "agile" is an accurate description of this life cycle process
I'm also having this issue and it would be helpful if it was solved!
Hi! Is it possible to raise the priority on this issue? These fields are critical to a large portion of one of our workflows.
Thank you!
Very annoying