Updating custom fields in existing jira issues via CSV import in Team Managed projects results in the error: "At least one given IssueParentAssociations must not be empty"

Issue Summary

Updating custom fields in existing jira issues via CSV import in Team Managed projects results in the following error message:

Unexpected failure occurred. Importer will stop immediately. Data may be in an unstable state: At least one given IssueParentAssociations must not be empty!

Steps to Reproduce

1) Create a CSV file with 40 entries in the following format:

Summary, key
Test 1, TEAM-1
Test 2, TEAM-2
.
.

2) Import the issues via the above CSV file into a team managed project using the External System Importer

3) Create a date custom field in the team managed project

4) Update CSV file such that all 40 issues have date field populated

Summary, key, Date
Test 1, TEAM-1, 21/JUL/21
Test 2, TEAM-2, 22/JUL/21
.
.

5) Import the CSV file again to the same project such that the date custom field in the issues are updated.

Expected Results

The CSV import operation is successful and the date field values are updated.

Actual Results

The following error message is seen on screen and only the first issue in the CSV file has the date field updated:

Unexpected failure occurred. Importer will stop immediately. Data may be in an unstable state: At least one given IssueParentAssociations must not be empty!

Workaround

The importer seems to look for a Parent Association for the imported issue and if it does not exists, it fails. To workaround this behaviour:
1) Create a test epic in the team managed project
2) Perform bulk operation to link the issues that are updated via CSV to this test parent epic
3) Import CSV file to update the date custom field successfully