Learn how company-managed and team-managed projects differ

We have two types of service projects: company-managed and team-managed. Company-managed projects come with power-user levels of configuration for expert users, but team-managed projects are easier to set up and simple to use.

What are Jira Service Management team-managed projects?
Team-managed service projects are simpler to set up than company-managed service projects.
Is my project company-managed or team-managed?
How to identify which project I'm in - a company-managed or team-managed project?
What makes the set up of team-managed projects different?
Company-managed projects share configuration across projects on a site. Team-managed projects are independent.
How issue and request types differ in team-managed projects
In company-managed projects, request types are based on issue types. In team-managed projects they're independent of issue types.
How do company and team-managed workflows differ?
Workflows are independent of request types in company-managed projects but are attached to request types in team-managed projects.
How does the role of admins change in team-managed projects?
Jira admins create configurations across all company-managed projects. Project admins create and configure team-managed projects.
Approvals in company and team-managed service projects
Compare how approvals work in team-managed vs company-managed service projects.
Migrate between team-managed and company-managed projects
Migrating between team-managed and company-managed projects is complex, but possible.

Was this helpful?

It wasn't accurate

It wasn't clear

It wasn't relevant

Still need help?

The Atlassian Community is here for you.

Ask the Community