Suggestion on intricate migrations from team to company managed boards

Artattack Group Srl

hello folks,

we started 2 years ago with a series of  TEAM MANAGED boards while transitioning to Agile to keep transition easier and smoother.

After a year some teams became mature enough to evolve to COMPANY MANAGED boards to start using STORIES and a simplified board with less columns and more statuses inside the columns.

 

BIG PROBLEM:

1. is there any way to migrate a board to another, without loosing the previous one? (this to leave a rollback chance)
2. coming from the team managed board we do not have the correct nesting

   EPIC -> STORY -> SUBSTASKS
   but just
   EPIC -> TASK
   how shall I proceed? should I manually create stories to then convert tasks in subtasks and parent to them?

   1. why in the MOVING processe I end up with NO CHANCE to change parents to tasks/subtasks and therefore cannot move a subtask inside its own STORY parent?

can someone give me some hints?

ty vm!

 

 

Trudy P Claspill

Hello @Artattack Group Srl 

Welcome to the Atlassian community.

When trying to "migrate" from Team Managed projects to Company Managed projects you have four choices:

1. Move the issues from the Team Managed project to the Company Managed project.

Since issues exist in only one project at a time there would be no rollback option unless you create backups that you can restore.

2. Clone the issues and move the clones to the new project.

This will leave the original issues in the original project so you can rollback to it, but the clones will not have all the history and none of the Comments of the original issue.

3. Export the issue data from the Team Managed project to a CSV file format. Use the CSV Import to recreate the issues in the Company Managed project. This would enable you to bring all the Comments into the recreated issues, and you would have the "rollback" option that the original issues remained in the Team Managed project.

4. Start fresh with the Company Managed project. Leave all the original issues in the Team Managed project.

 

Your questions:

1. You will not be able to move the original issues from the Team Managed project to the Company Managed project and retain the information in the Team Managed project board. That board contains only issues in the Team Managed project. If you move those issue to a different project then they are no longer part of the Team Managed project board.

2. You do not have to convert your Team Managed project issue types of "Task" to "Story". In the Company Managed project you can change the Issue Type Scheme to include a "Task" type of issue and use that instead of "Story". You could even remove the "Story" issue type if you don't want to use it.

I am a little unclear about the subquestion you had under #2. It seems to be about moving subtasks, but you indicated that you don't use subtasks in your Team Managed project.

One thing to note is that Team Managed projects don't allow their Epics to have child issues in other projects. In this migration process (unless you use the CSV method) you will have to manually re-associate the Epics with their child issues in the Company Managed project.

 

For more information on the migration process refer to 

https://support.atlassian.com/jira-software-cloud/docs/migrate-between-team-managed-and-company-managed-projects/