Issue Summary

Currently, if a date picker or date/time picker custom field's value is set by someone in Timezone A, its value will be automatically adjusted when viewed by a person in Timezone B. It should be possible to set an absolute timezone. 

On top of all that what has become an issue for us in one particular scenario is that we cannot create a datetime field that is fixed to a timezone (utc) - when person A has a different timezone set than person B then they will see a different value even though we need them to speak the same dates and time to each other. 

Steps to Reproduce

1. Have a person A, in AEDT, set a date picker custom field to a certain time, which they intend to set as UTC.
2. When person B, in JST timezone, views the custom field, its time will have been adjusted even though it should remain the same UTC timezone. 

Expected Results

Have the ability to set date picker custom fields to timezones other than the one the user is currently in.

Actual Results

date/time picker custom field changes based on end-user's timezone

Workaround

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