You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
How to convert existing Team managed project to a company managed project ?
I do not want to migrate the issue but to change the project configuration to a company based project.
Hello @Eran Haskel
Welcome to the community.
It is not possible to convert a Team Managed project to a Company Managed project. The only option is to create a new Company Managed project and move the issues from the Team Managed Project to it.
Hi @Eran Haskel -- Welcome to the Atlassian Community!
Yes, and...to what Trudy notes:
Here is the same link she provided, but for Jira Software Cloud (not JSM): https://support.atlassian.com/jira-software-cloud/docs/migrate-between-team-managed-and-company-managed-projects/
Please ensure you read about the limitations of the switch, including settings and field impacts.
This seems like a basic configuration capability that is needed. When creating a new project, you cannot reuse the same name, issue key, etc.
Are you trying to create a new project that has the same name, issue key, etc. as a project that currently exists, is archived, or is in the trash? Or are you trying to reuse information for a project that has been fully deleted?
Ideally you could keep the same project and just make a simple settings update to switch from team-managed to organization-managed. Currently, you have to create an entirely new project, and for that you are not allowed to re-use issue keys, for example. You lose a ton of settings and work, all for a configuration change.
Team Managed and Company Managed projects use fundamentally different architectures.
Company Managed projects use schemes to store configurations:
Custom Fields, Field Configurations, Field Configuration Schemes
Issue Types, Issue Type Schemes
Screens, Screen Schemes, Issue Type Screen Schemes
Workflows, Workflow Schemes
The schemes are stored separately from, and can be modified separately from, the projects. The schemes can then be associated with 1..n Company Managed projects. The use of schemes makes these items reusable between Company Managed projects.
Team Managed projects store all the comparable information as part of the one project. They were not intended to be reusable or shared. The configuration of a TM project is intended to be manageable by Project Admins with no impact to any other project in the system. In some cased, such as workflows, the fundamental implementation of the functionality is also different. There is not a one to one correlation between the TM and CM configurations.
It would be, I assume, a huge amount of work to "convert" all the configuration elements from one architecture to another, when they were never designed to support that type of conversion.
It is like saying you should be able to make a few simple changes to your sedan car and turn it into an Indy race car.