Issue Summary

When we are bulk moving issues from TMP Business Project to CMP Business Project, the parenttoSubtask association is broken due to the backend not being able to find the parent's issue ID while moving the subtasks.

The parent association is broken only for TMP Business -> CMP Business projects. It is working as expected for TMP -> TMP and CMP -> TMP in business projects and for all combinations of software projects. 

Steps to Reproduce

1. Create a couple of task issues with subtasks in a team-managed business project.
2. Perform bulk operations to move all the issues from the team-managed business project to the company-managed business project.
3. During Bulk operations, select all the Parent issues. The Subtasks will automatically get selected for the movement. 

Expected Results

All the parent issues and their child/subtask issues should get moved to the Company-managed business project and the Parent to Subtask relation/link will exist, post bulk movement of issues, in the Company Managed project. 

Actual Results

The Parent to Subtask link/relation breaks resulting in orphaned Subtasks in the Company Managed project. 

Workaround

Pre requisites: having both a Company-managed project already created in the site.

Steps : The easiest approach to move issues from a team-managed project to a Company-managed project, while maintaining the relationship between STORY and the newly converted SUBTASK, is to use a CSV export. To do so, please follow these steps:

1. Export your issues to a CSV file;
2. Change the Task issue type to Subtask in the CSV
3. Make sure the Issue ID and Parent
4. Regarding structuring relationships and subtasks, please see the following topics in this documentation
   • Creating parent / child relationships
   • How to import issue links from a CSV file in Jira

• Another option would be to look for Marketplace apps, that might have additional features, related to bulk operations.