How can I move an issue from a team-managed project to a company-managed project?

[Shryock, James]

When I attempt to move an issue from the team project to the company project, I keep receiving a notification that I will lose some of my fields because they don't match exactly. If the names of the fields are exactly the same, it creates an error with my automation. How can I do this without losing the data?

[Jack Brickey]

Have you attempted a single move operation to assess what happens?

[Rajesh Kumar Reddy]

Seems the source Project and Target Project have different Screen Schemes (with different fields) and so the error. May be you should configure both Projects with same Screen Schemes in order not to loose data.

[Bill Sheboy]

Hi @Rajesh Kumar Reddy 

I do not believe that always works, as the Team-Managed projects each can have their own custom fields which are independent of the ones from the Company-Managed ones...and so some fidelity can be lost.  Please see here for more information:

https://confluence.atlassian.com/jirasoftwarecloud/migrate-from-an-next-gen-project-to-a-classic-project-957974933.html

Best regards,

Bill

[Jack Brickey]

Precisely. That is why I suggested you try a sample to understand what day do you might lose and see if there’s a means of working around it. For example let’s say there’s a certain field that you lose data on and let’s say that Field, is a drop-down with three choices. Then you could move all of the issues with value A and then edit those issues after they move to set the value to A. Repeat for B and C