Issue Summary

Updating any field in Team-Managed projects using the CSV import causes the Epic link between Epics and other issue types to be broken.

Steps to Reproduce

1. In a team-managed project create an Epic and a Story/Bug/Task
2. Link the Epic to a Story/Bug/Task using the blocks link OR create a new issue under the Epic
3. Update any field in the issue using the External System Import / Jira import wizard / CSV
4. By updating any field in the issue will cause the Epic/Story link to be broken

Expected Results

Updating any field in the issue will cause the Epic/Story link to be broken.

For team-managed projects, Epic/Parent Link data importing is not supported: https://jira.atlassian.com/browse/JSWCLOUD-17758

Actual Results

Updating fields in the issue should keep the Epic/Story link

Workaround

There's a workaround using Automation for Jira to address the bug. Here is an overview of the solution, The rule is triggered when the parent field is changed, then the rule checks if the issue key is one of the issues in the CSV import. If the condition is met, the rule will update the parent again with the old value.

To use this workaround, enable the rule before the import. Once all issues are imported and their parents are updated by the automation rule, Then, the rule can be disabled so it won't affect normal changes to the parent field on these issues.

Here's a screenshot showing the rule workflow:

And here's a quick demo video showing the import of one issue on a team-managed project where the parent field was wiped out by the CSV import, but then it was restored by the automation rule: