What are team-managed and company-managed projects

Projects in Jira can be created as either team-managed or company-managed projects (formally next-gen and classic). The core functionality of these project types are the same, but there are key differences you should know in order to decide what’s right for your team.

The difference between team-managed and company-managed projects

Set up and maintained by anyone on the team, team-managed projects are ideal for autonomous teams who want to control their own working processes and practices in a self-contained space. Team-managed service projects have simpler project configuration and give project admins more control over set up without involving a Jira admin (unlike company-managed projects, where one is required to configure schemes and screens).

Set up and maintained by Jira admins, company-managed projects are the best choice for teams who want to work with other teams across many projects in a standard way, such as sharing a workflow. Company-managed projects require a Jira admin to configure screens and schemes that projects are based on. Hence, company-managed projects have greater complexity in project configuration, but also the ability to standardize workflows across projects that team-managed projects don’t have. When a Jira admin changes a scheme or screen, every company-managed project that uses that configuration changes accordingly. Learn how to Migrate between team-managed and company-managed projects.

Configurations and features

View the list below to learn the key differences between team-managed and company-managed projects, and determine which best suits your needs.

Team-managed

Company-managed

Set up and maintained by your team.

For teams who want to control their own working processes and practices in a self-contained space. Mix and match agile features to support your team as you grow in size and complexity.

Set up and maintained by your Jira admins

For teams who want to work with other teams across many projects in a standard way. Encourage and promote organizational best practices and processes through a shared configuration.

Simplified configuration

Get up and running quickly, with simplified configuration.

Expert configuration

Benefit from complete control with expert configuration, customization and flexibility.

Anyone on your team can set up and maintain

Set up and maintained by your Jira admins

Settings do not impact other projects

Standardized configuration shared across projects

Easy setup for issue types and custom fields

Complete control over issue types and custom fields

Simple workflow creation

Customizable workflows, statuses and issue transitions

Access level permissions

Detailed permission schemes

Essential features

A modern Jira experience for teams who don’t need advanced features.

Advanced features

All the power and features that Jira Software is known for.

Basic Roadmaps

Advanced Roadmaps (Premium only)

Only show your project’s issues on your board

Pull in issues from other projects on your board

Standard filters

Custom quick filters

Single active sprint

Parallel sprints

Essential agile reporting

Comprehensive agile reporting

How to choose between a company-managed or team-managed project

The fundamental difference between the two project types is how they are administered, and whether that occurs at the team level or at a company/Jira admin level. Choose a team-managed project if:

  • Your team wants easier project configuration to get started quickly.

  • You want a self-contained space to manage your team’s work.

Choose a company-managed project if:

  • You want to standardize configuration across multiple projects in your organization

  • You require advanced features that aren’t available in team-managed projects.

Join the Atlassian Community to ask questions, provide suggestions, or find out what's coming soon.



Last modified on Apr 23, 2021
Cached at 9:05 PM on Aug 2, 2021 |

Additional Help

Ask the Community