-
Bug
-
Resolution: Fixed
-
High (View bug fix roadmap)
-
8.16.0, 8.16.1, 8.17.1, 8.18.0, 8.19.0, 8.19.1, 8.20.2, 8.20.3
-
8.16
-
42
-
Severity 3 - Minor
-
8
-
-
Issue Summary
"Due Date" system field and all "Date Picker" type custom fields are recalculated to UTC in CSV export file. Both "CSV (All fields)" and "CSV (Current fields)" export methods are affected. All other export methods available on the Issue Search page are not affected (HTML and XML export). The problem can be reproduced only in Jira 8.16.0 and 8.16.1, all older versions (including 8.15.1) are not affected.
Steps to Reproduce
- Edit Jira issue and set some date in the "Due Date" system field. Alternatively, you can set some date in any "Date Picker" type custom field.
- Go to Search Issues page and enter JQL that will list issue from step 1 as one of the results.
- Export the results using the "CSV (All fields)" or "CSV (Current fields)" method.
- Look into an exported CSV file to verify exported data.
Expected Results
Assuming that the date set in the "Due Date" system field or "Date Picker" custom field was 6th May 2021, the value in CSV export file should be: 06/May/21 12:00 AM.
Actual Results
Assuming, that Jira environment is configured for Sydney AEDT timezone (GMT+10), the actual result is: 05/May/21 2:00 PM. 10 hours are subtracted from the correct date (06/May/21 12:00 AM), so the time is recalculated from GMT+10 to UTC (GMT+0). Data stored in the database is the same across all impacted and not impacted Jira versions.
Attached Files
- Data from Jira 8.15.1 (date set in "Due Date" system field and "Test Date" date picker custom field was 6th May 2021):
- "Database_data_8151.txt
" - stored data is correct and the same as the one from Jira 8.16.1. - "JIRA_8151_CSV_export.csv" - exported data is showing the proper values in the "Due Date" system field and "Test Date" date picker custom field.
- "Database_data_8151.txt
- Data from Jira 8.16.1 (date set in "Due Date" system field and "Test Date" date picker custom field was 6th May 2021):
- "Database_data_8161.txt" - stored data is correct and the same as the one from Jira 8.15.1.
- "JIRA_8161_CSV_export.csv" - exported data is showing the wrong (recalculated) values in the "Due Date" system field and "Test Date" date picker custom field.
- "Database_data_8161.txt
Workaround
Custom fields using date time pickers are not affected by this (only date pickers). Using custom fields with date time pickers will export with the expected time.
[JRASERVER-72382] Due Date system field and all Date Picker custom fields are recalculated to UTC during CSV export
Dear Customers,
We’ve investigated the bug and decided to lower its priority. For this decision, we’ve considered the number of votes and watches on this ticket.
Next steps:
We will keep you informed on any new developments related to this issue. If you have additional questions, feel free to contact Team Raid (#team-raid).
The workaround for this bug is as follows:
Custom fields using date time pickers are not affected by this (only date pickers). Using custom fields with date time pickers will export with the expected time.
Best regards
Grzegorz Kulinski
Jira DC developer
Hello,
Sorry for the delay in communication and a bit of confusion here. Based on feedback we have been receiving we have to take a deeper look again into that problem. We are investigating it and will keep you posted.
Cheers,
Jakub
After investigation we can confirm that the issue is no longer reproducible with Jira 8.20.4 and further versions. If you still experience the issue please check if you are on a version containing the fix.
Cheers,
Jakub
Hi Thomas,
As we've checked, 8.22.0 and 8.20.6 don't have this issue.
So now, only 8.21.1 hasn't fix this issue, right?
Best regards,
Jacky Zhou
Hello pprzytarski
This bug is still present, I just tested on the version that the fix was applied on 8.20.4 The date is still wrong and the versions after this still have the problem. This ticket still needs to be open.
Kind regards
Thomas - Atlassian
It seems that the problem still appear in the version 8.21.1
Could you please double check
Atlassian Update – 30 Nov 2023
Dear Customers,
We’ve investigated the bug and can confirm that the issues with Due Date system field and Date Picker custom fields were fixed in Jira 8.22.0 and backported to 8.20.4. Note that the fix isn’t included in 8.21. Some of the comments in this ticket refer to similar issues with Target Start and Target End fields but they are tracked in separate tickets (
JSWSERVER-21994andJRASERVER-76364). We’re happy to announce that Target Start and Target are also fixed now and will be included in 9.13 release.Best regards,
Shushan Ulubabyan
Jira DC developer