-
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
-
-
- Closed
-
[MIG-342] Unable to set Due Date field using the Look and Feel configuration
| Resolution | New: Timed out [ 10 ] | |
| Status | Original: In Progress [ 3 ] | New: Closed [ 6 ] |
| Labels | New: timeout-bulk-close202309 |
| Component/s | New: Jira - Import - From External System [ 58290 ] | |
| Component/s | New: Jira - Import - From External System [ 58290 ] | |
| Component/s | Original: Backup & Restore - Import From JIRA Cloud [ 46548 ] | |
| Component/s | Original: Issue - Create [ 46596 ] | |
| Key |
Original:
|
New:
|
| Project | Original: Jira Cloud (including JIRA Core) [ 18514 ] | New: Migration Platform [ 19710 ] |
| Status | Original: Long Term Backlog [ 12073 ] | New: In Progress [ 3 ] |
| Attachment | New: Screenshot 2020-05-26 at 2.03.26 PM.png [ 388852 ] | |
| Attachment | New: Screenshot 2020-05-26 at 2.03.50 PM.png [ 388853 ] | |
| Attachment | New: Screenshot 2020-05-26 at 2.05.41 PM.png [ 388854 ] | |
| Attachment | New: Screenshot 2020-05-26 at 2.06.25 PM.png [ 388855 ] |
| Status | Original: Needs Triage [ 10030 ] | New: Long Term Backlog [ 12073 ] |
| Component/s | New: Backup & Restore - Import From JIRA Cloud [ 46548 ] |
| Description |
Original:
h3. 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. h3. 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 h3. Expected Results The import should finish with success mapping the Due Date field as expected. h3. Actual Results It gives an error that Jira was unable to parse the date format. h3. Workaround Use the format 03/Mar/20 12:00 AM and at the import wizard leave the default format suggestion: dd/MMM/yy h:mm a |
New:
h3. 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. h3. 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 h3. Expected Results The import should finish with success mapping the Due Date field as expected. h3. Actual Results It gives an error that Jira was unable to parse the date format. h3. 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 |
| Description |
Original:
h3. 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. h3. 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 h3. Expected Results The import should finish with success mapping the Due Date field as expected. h3. Actual Results It gives an error that Jira was unable to parse the date format. h3. Workaround At the CSV file, you must use the yy/MMM/dd format to be able to successfully import the data for Due Date field. |
New:
h3. 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. h3. 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 h3. Expected Results The import should finish with success mapping the Due Date field as expected. h3. Actual Results It gives an error that Jira was unable to parse the date format. h3. Workaround Use the format 03/Mar/20 12:00 AM and at the import wizard leave the default format suggestion: dd/MMM/yy h:mm a |
| Support reference count | New: 1 |