Issue: When customers are importing the data from CSV files, the due date on the issues is displayed as 1 days less than actual dates mentioned in CSV file. 

Currently this is due to the server timezone difference between server and client machines. As Jira converts the date/time to server timezone and saves the data, the same is displayed when users try to access imported issues.

Impact: When customers would like to merge projects or migrate data from different instances across different geographies, this results in data discrepancies.

Example: due date was "12/30/2019 00:00 +05:30" in .csv file, however, after import Jira shows as 29th Dec 2019while browsing through the issue. The server timezone is 10:30 hours behind as compared to client timezone in this case.

Suggestions for Improvement: Jira should retain the value of timestamps when using CSV imports or provide users with ability to select timezone for the import so that there data remains consistent.