Is it possible to migrate Team Managed Project to Company Managed project without last any history

[kanaka prasad ponnuru]

Hi Team,

We have  a team managed project and now this project has to be migrate to company managed project without last any history.

Can someone help me with this?

Regards,

Kanaka

[Alexander Bondarev · Accepted solution]

Hi @kanaka prasad ponnuru !

Some information you have to lose (report history, story point estimations, versions and releases). 

Like told in the official documentation:

Team-managed projects and company-managed projects are technically quite different. Here's a few things to consider when you migrate from a team-managed software project to a company-managed software project:

• Board statuses: If you customized your team-managed board, you'll need to set up the same statuses in your company-managed project's workflow. Only Jira admins can create and modify statuses and workflows. Learn more.

• Custom fields: If you use custom fields in your team-managed project, a Jira admin needs to recreate the fields and add them to screen schemes and field configurations in your company-managed project. Custom field data will need to be recreated, otherwise it will be lost.

• Issue types: If you added your own issue types to your team-managed project, you'll need to have a Jira admin recreate these using an issue type scheme that they associate to your new company-managed project. Learn more.

• Project access: Access to company-managed projects is controlled by a permissions scheme. Only your Jira admin can update your company-managed project's permission scheme. Learn more.

• Project and issue keys: Project keys are unique and can never be reused in Jira. If you migrate your issues to another project, they will get new keys and the new project must have a different key of its own. If you migrate your issues using the process above, Jira will automatically redirect any links to your old issue keys.

• Reports: Reports data won't be saved. Even though your issues will be retained, data for your project's Velocity and Burnup reports won't transfer over, and will be lost.

• Story points estimation: This data will be lost. This is because the custom field that Jira uses to store estimates in company-managed projects (Story points) is different to the custom field used in team-managed projects (Story point estimate). 

[kanaka prasad ponnuru]

Thank you @Alexander Bondarev for your support. This is really helpful.

And one more question without having manage sprint permission at project level can someone will be able to Start/ Stop the sprint?

Why because cloud permissions seems to be bit difficult.

Ex: I am not having manage sprint permission and I am able to starting the sprint this looks wierd. I don't understand without having manage sprint permission how I can able to start/stop sprint.

I am the site admin will this is the issue?

Regards,

Kanaka

[kanaka prasad ponnuru]

Hi @Alexander Bondarev one quick question can we have all lost information in offline mode? We just want to keep them for record purpose 

[Alexander Bondarev]

Hi, @kanaka prasad ponnuru ! 

sorry for my pause, 

your case with permissions sounds strange, are you sure you're not using the free plan?

here you can find details.

[Carlos Garcia Navarro]

Hi @kanaka prasad ponnuru ,

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

[John Funk]

Hi Kanaka,

What do you mean by "without last any history"?

[kanaka prasad ponnuru]

@John Funk, I mean I need to move everything from Team Managed Project to Company Managed project and also history to new project.

Is it possible to do this?

Regards,

Kanaka

[John Funk]

The history of the issue will still be visible when you move it. I would suggest you move one issue and see what happens and if it is what you want to happen. Then also check the history to see if you still have that.