As per the title of this bug ticket, the CSV import feature only respect the time zone of the server which in the case of On Demand customers, they have no control over the server time zone and causes discrepancy on their instance.

Example Use Case
Customer generate csv file from the local instance/applications and the time exported is based on customer time zone (GMT+8) and customer import this generated csv file to an On Demand instance.

Expected, the time zone will be respected based on the setting of General Configuration > System Time Zone which user have access to.

Actual, it disrespect and actually stored the time on the default time zone of the server (UTC+0), so having configuration of GMT+8 will cause discrepancy on the On Demand instance.

Steps to Reproduce

1. Set the time zone of the JIRA On Demand instance to any time zone (+8)
2. Perform a CSV import with the created time (2013-11-26 11:30)
3. Notice that the time updated on the issue is (26/Nov/13 7:30 PM) instead

Note

This should not be a high priority issue for self installed version of JIRA as this can be worked around by setting the server time zone to respect the time. But for On Demand customers this is not possible.

Suggestion

To have a drop down for selection on csv import that can choose the time zone accordingly for On Demand customers.