Deep Clone - Issues with moving Subtasks

[Robert.Ogden]

I have been using Deep Clone for sometime to move content from team managed project to company managed projects and have run into the issue where the tool will not move sub-tasks - when I project to project clone I receive the message that states Subtasks cannot be used with the Same as Original Issue Type.

I have even tried do a issue clone that has sub-tasks and the software ignores all sub-tasks - i have contacted the vendor and they said this was by design. Does anyone know exactly what that means  i have attached a screenshot of the issue i am seeing.

Thank you in advance

[Robert.Ogden · Accepted solution]

So figured out what the issue was that was preventing me from using Deep Clone to move Team Managed Subtasks to Company Managed Sub-tasks.

The problem when you create a team managed project it creates subtask but when you create a company managed project you are using sub-tasks, especially in my instance.  This instanced was setup before I started with the company.

So by going into the Team Managed project and adding the hyphen between sub and task I was able to get Deep Clone to not only recognize the issue type but move them.

[Luka Hummel - codefortynine]

Glad you found the problem.

When Deep Clone for Jira clones between team-managed and company-managed projects, it tries to match values like issue type and custom fields by their name. This only works correctly if the names are identical.