Issue Summary

It is possible to update a Sub-task's issue type via CSV, but even though you change its issue type to a Standard one, the parent/child relation will be kept between the parent issue and the Sub-task you've just updated.

Environment

Jira Cloud.

Steps to Reproduce

• Create a CSV file with the columns that will reffer to:
  • Issue type: the name of a standard issue type (non-sub-task;
  • Issue key: the key of the Sub-task you want to update;
  • Summary: this column will be empty;
  • Here's an example file: update issue.csv

Expected Results

Either it should not be able to directly change the issue type of a Sub-task (which the UI does not offer as an option unless there is another Sub-task issue type), or the parent/child relation should not be kept.

Actual Results

Jira keeps a parent/child relation between the two issues.

See the example:

Workaround

Moving the child issue to a different project will remove it from the parent view as a sub-task.

But, that may still cause other problems, such as this one: Cannot move issue if there was a parent/child relation with another non-sub-task issue.