Assets for JSM: Setting Date Attributes is misrepresented in Issue HIstory since it is aware of Timezones and alters the presented information based on them. This makes the value appear incorrect.

Issue Summary

When setting Date Attributes, Assets stores the Timestamp at Midnight GMT.
This breaks presentation of the Date in the Object History, since that converts the Timestamp to the User's timezone, which then misrepresents the value.

Steps to Reproduce

1. Create an Object with a Date Attribute the User can set.
2. Set the Date Attribute to a Value.
3. Change the Date Attribute's Value.
4. Make sure your Timezone is negative relative to GMT, such as GMT-5, GMT-6, GMT-7, etc.
5. Review the Issue History to see that it shows the Date as the day before you set it to in step #2 & step #3

Expected Results

The Date change information should be presented correctly in the Object History.
i.e. it shouldn't change based on User Timezone. It should always show exactly the date the User set it to.
It shouldn't be aware of Timezones.

Actual Results

It is aware of Timezones for Date Attributes, which causes this mismatch to occur, misrepresenting the data in the Issue History when viewed via the User Interface.

Workaround

There is no currently known workaround, except to use a DateTime attribute instead to be able to set the Time, and thereby, avoid this issue.