Trying to migrate from team-managed project to company-managed tripping up on Epic Name

[Ken Collins]

I am trying to migrate (Move) all issues from a team-managed project over to a company-managed project by using the Bulk Move operation. When I attempt to move epics, I get the dialog to enter Epic Name, if I choose Retain field value then the bulk operation stops there, requiring me to enter an Epic Name. This forces me to do the move Epic by Epic which is very painful.

I have tried to use Scriptrunner built-in script to copy the Summary over to the Epic Name field, however that fails because "Epic Name is not on any screen" and I cannot add Epic Name to the screens in the team-managed project.

Also I have a custom field Acceptance Criteria in both projects and on all screens, yet when I move an issue, the Move operation removes the Acceptance Criteria. In the new project I am able to use the issue history to see the old value and then manually copy/paste into the field but this is not possible to do manually when working with 100's and 1000's of issues. I am on Jira Cloud so I am unable to use a script in Scriptrunner to take advantage of the changeHistoryManager

Surely there has to be some better method of moving from a team-managed project to company-managed.

[Walter Buggenhout]

Hi @Ken Collins and welcome to the Community!

Moving between project types is a painful experience. It just is like that. For the Epic name, I would suggest you just fill out a hard coded value and then update the Epic names manually after the migration in your company managed project.

For the acceptance criteria, I saw a similar question earlier today. You could consider exporting your data to csv and then import them again after the move. Have a look at that thread over here.

Hope it helps! 

[Ken Collins]

Thanks for the speedy response Walter!

I did try as you suggest with Epic Name and this seemed to mess up the Epic-story(child) relationship as then all the stories in the project pointed back to the one epic. Do you know of a trick to mitigate that?

otherwise I fully agree that converting from team to company project is just going to be painful. I have done similar moves between projects but all on Server version of Jira and none of those tricks work on Jira Cloud ie I cant directly access the database and the only tools available are via REST API