When importing issues from a CSV file, some field values are not imported
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Problem
When importing issues from CSV, not all fields are imported. Some fields are blank/not set in all the imported issues.
No import-related errors are logged.
Diagnosis
In the workflow associated to the issues and issue types you're importing, look for post-functions in the "Create" transition.
Cause
Issues imported from CSV are created via the REST API. The "Create" transition is run before the statuses of the issues are flipped to the ones in the CSV.
In some cases, this transition has post-functions that clear certain fields, especially the ones that are set on other transitions.
Workaround
- Temporarily disable the post-function(s) from the workflow.
- Import the issues from CSV.
- Enable back the post-function(s) from the workflow.