I was working with a team-managed Work Management project and needed to copy the data from the Category field (team-managed field) to an actual Jira Custom Field.
To do this I exported the affected tickets to a csv using only
I modified the name of the Category column to be the name of the new field and proceeded to do a CSV import using Issue Key as the mapping field.
I was not trying to alter the Parent field at all, so I did not include it in the export or the import. The import file consisted only of those three fields.
After the import the new custom field was populated correctly, HOWEVER the parent field for all issues was deleted. All Epic links were removed.
I cannot find anything in the documentation that would indicate this is expected. The documentation, as far as I can see, does not REQUIRE the Parent field to be part of an updated import.
Has anyone else experienced this? Is this because it was a team-managed project? Or because it was a Work Management project?
When trying to correct the problem, I tried to use a JQL WAS statement to find what the Parent of each issue was before the update, but WAS is not an allowed function to use with the Parent field. I ended up having to look at the history of each ticket, find the Parent ID and update manually.
Was there an easier way to go about finding and fixing the Parent field after the damage was done?
