How to choose the right project in Jira cloud

Hi Community,

II want to share an article I wrote that explores the differences between team-managed and company-managed projects in Jira cloud and provides insights on how to choose the best one that fits your needs.

As a Jira administrator on the cloud platform, you are probably familiar with the two project types offered by Jira: Team-managed project (previously known as "next-gen project")  and Company-managed project (previously known as "classic project"). 

While the core functionality of both project types is the same, there are significant differences that you should consider to determine which type is best suited for your team's needs.

Team-managed projects are ideal for teams looking to quickly launch and manage projects on their terms, from start to finish, within a self-contained environment and basic configuration.

When using team-managed projects, the project manager is authorized to customize and establish the project configuration that best suits his team's unique requirements. For example, a Project manager can add new screens, fields and develop custom workflows that fit the specific needs of his team.

While team-managed projects provide the benefits of simplified and efficient processes, they may lead to lack of standardization because the team is free to customize it’s project as they see fit, which can result in variances across multiple organizational projects.

Company-managed projects are the best choice for teams who want to work with other groups across many projects in a standard way, while sharing the main schemes like workflows, permissions, fields and more. It can also be a good fit for teams that want to use complex configurations and the more advanced settings and features Jira offers.

Company-managed projects require Jira admins to configure the schemes and the shared configuration. When a Jira admin changes a scheme or screen, every company-managed project that uses that configuration will change accordingly. Project admins can only execute some of the changes – like managing versions and components and configuring boards. Most of the work – like creating and maintaining schemes and custom fields – is done by Jira admins. Change requests often require collaboration between team members, project admins, and Jira admins.

Choosing the right project type is crucial since switching to another type is impossible once you have selected your preferred project type. If for any reason, you need to change the project type, you’ll have to create a new project, manually transfer all the issues between the projects and resolve the variant mismatch. For example, if you would like to move from a team-managed project to a company-managed project and you created new custom fields, the Jira admin will have 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.

It can be a complicated and time-consuming task that is generally not recommended. It is, therefore, crucial to comprehensively understand the differences between the project types before deciding which one to choose.

So, what are these differences, and how can you determine which one best fits your team's needs?

See the full article at the following link

How to choose the right project in Jira cloud 



Log in or Sign up to comment
AUG Leaders

Atlassian Community Events