-
Bug
-
Resolution: Timed out
-
Low
-
None
-
None
-
1
-
Severity 2 - Major
Issue Summary
Importing Due Date in the format set in the Global Settings (look and feel) causes the import to fail for Due Date field as it uses its own format YYYY/MMM/dd.
When importing the Due Date value, it gives a warning that Jira was unable to parse the value.
Steps to Reproduce
- Have the look and feel set to display and use dates in the format MMM/dd/yy
- Have a CSV file to import and set the Due Date
- At the CSV import wizard set the date format to match your data format MMM/dd/yy
Expected Results
The import should finish with success mapping the Due Date field as expected.
Actual Results
It gives an error that Jira was unable to parse the date format.
Workaround
Use the default format at the CSV file (I.e 03/Mar/20 12:00 AM) and at the import wizard leave the default format suggestion: dd/MMM/yy h:mm a
- is related to
-
JRACLOUD-68381 New Issue View does not respect Jira's Advanced Settings Date Format
- Closed