• Products
  • Documentation
  • Resources

Manage and administer team-managed projects

This page is for team-managed projects

If the lower-left of your project sidebar says you're in a company-managed project, check out these company-managed project articles instead.

Learn more about the difference between company-managed and team-managed projects.

By default, anyone with product access to Jira Software can create a team-managed software project. Unlike company-managed projects, team-managed projects don't share their configuration with any other project on your Jira site. And, you make updates without worrying about affecting other software projects on your Jira site.

With team-managed software projects, anyone can manage their own work, their team’s work, and their working processes, without having to reach out to a Jira admin for help.

In this section:

Jira administrators can control who's allowed to create a team-managed project in their global permissions settings. Learn more about global permissions.

If you want to migrate an existing company-managed project to a team-managed project, or the other way around, check out our tutorial on converting a project to a different template or type.

Here’s what’s different in your team-managed project:

Issue types. You can define your team’s work by creating issue types unique to your team’s working process. These issue types have their own workflows, which are unique to your project. You can quickly update or change the fields your team uses to describe each type of work.

Fields. Fields you create for your issue types are available to every issue type in your project. They’re unique to your project only. You can still use them to filter for issues across your Jira site or in dashboard gadgets. But, they belong solely to your project.

Access and permissions. Team-managed projects prioritize access based on project roles that are unique to your project. You can assign individual people and groups to roles in your project to control their access.

Features. You can experiment with different working styles by enabling and disabling agile features, like backlogs, sprints, estimations, or releases and versions. Use as many as your team needs, whenever they need them, and turn off the rest to help you focus.

Last modified on May 24, 2021
Cached at 8:58 PM on Oct 23, 2021 |

Additional Help