-
Bug
-
Resolution: Unresolved
-
Low
-
17
-
Severity 2 - Major
-
0
-
Summary
CSV Reports containing the field 'Date of first response' does not obey to the selected timezone as other fields do (like created, updated). This can cause inconsistencies like reports having 'Date of first response' field being lower than the creation date.
Environment
Tested within cloud environemnt
Steps to Reproduce
- Create an issue.
- Comment on it.
- Download a first csv report.
- Go to user profile settings and change your timezone setting.
- Take another report with the same issues.
- Compare Date of first response with other date fields on both reports.
Expected Results
The 'date of first response' field should obey to the same rules as other date fields like 'created' (get converted to the selected timezone)
Actual Results
Date of first response is not converted to the timezone settings (remains unchanged)
Workaround
Select Export HTML reports instead of CSV. For HTML reports the timezone works as expected.
- relates to
-
JRACLOUD-68017 Date fields are not converted to the user timezone when exporting an issue
-
- Gathering Impact
-
Hello!
We’re looking to improve the import experience in Jira and are keen to understand how our community is using the Jira Import Module (JIM). If you’ve used JIM to migrate/move data into Jira recently, we’d love to hear about your experience. Please take a few minutes to fill out this survey. Your feedback will help us learn how we can improve your experience in importing data.
Survey link - https://forms.gle/NYNkmS92r96z42QV9
Thanks!
Prashanth M
Product Manager, Jira Platform