Migration from team managed to company managed project

[Sushmita Chakraborty]

Hi Team,
I have been trying to move one Team Managed Project to company managed project and while moving all the listed issues from team managed to company managed. I get an error as follows:

"You are moving some issues away from their parent epic" (Screen shot attached)

Upon investigating I see that some of the tasks and sub tasks in the project has been linked to some parent issue establishing a parent-child relationship (though I do not know how different it is from the epic-task/epic-story relation).

When I select the destination as CMP, the parent issue vanishes (screen shot attached).

As a test, I created a copy of the parent issue in the company project (manually) and then migrated the sub tasks and linked. But if this is the case then it will affect the sprint and the originality of the parent issues. Is there an alternate way to deal with this?

[Anusha A]

Hi Sushmita,

Thank you for your inquiry within the community.

I noticed that you've submitted a support ticket with us for this matter. Would you be willing to share the resolution with the community once the issue is resolved? This way, a broader audience can also benefit from the information.

Best Regards,

Anusha A | Atlassian Cloud Support

[Sushmita Chakraborty]

I will once I receive a resolution

[Sushmita Chakraborty]

I have been informed by Atlassian  that this is identified as a bug. And currently being worked upon by the Atlassian team

[Anusha A]

Hi Sushmita, 

Thank you for responding with the latest information.

Below are the bug details for a broader audience:

• JRACLOUD-84065- While bulk moving issues from Team Managed Business Project to Company Managed Business Project, parent-subtask association breaks

Kindly add yourself as a watcher to the bug case to receive additional updates as they are made available by our Developers and include any additional feedback you may have. For more details, check out our Bug Fix Policy. 

Have a good day ahead :) 

Best Regards,

Anusha A | Atlassian Cloud Support

[John Funk]

Hi Sushmita,

In your test, did you try to move the Epic and the child/children under it at the same time? 

[Sushmita Chakraborty]

Yes, that is what I am trying.

[Luka Hummel - codefortynine]

Hi @Sushmita Chakraborty

If you are having trouble with the standard Jira 'Move' feature and are willing to try a third-party app, you could try our Deep Clone for Jira. Deep Clone can clone your issues from your team-managed to your company-managed project and will match all custom fields as long as their names are identical.

If you want to emulate the Jira 'Move' feature further, you can delete the source issues after cloning.

[Sushmita Chakraborty]

i imported this tool (trial version), however while cloning the story-sub task relationship is retained, however the epic and the task relationship is lost. Additionally, the status of the tasks changes from "In Progress" to "To Do", "Done" to "To Do", etc.

Note that I have considered all the criteria while cloning the tasks.

[Luka Hummel - codefortynine]

Hi @Sushmita Chakraborty

Make sure you have checked Clone the issue status under More options and selected either Link to cloned parent, else keep original or Keep link to original parent, depending on your use case.

[Sushmita Chakraborty]

Screen shot attached for reference