Get started with Jira Service Management for admins
Your first stop for learning how to get started with Jira Service Management.
Jira Automation docs have moved
All content related to Jira Cloud Automation, previously under the Automate your Jira processes and workflows section, have moved to the new Cloud Automation docs.
What are Jira Service Management team-managed projects?
We currently support both company-managed and team-managed projects in Jira Service Management Cloud. The main functionality between the project types are the same, but there are key differences you should know to decide what’s right for your organization.
The difference between company-managed and team-managed projects
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). Both project types have Enterprise Service Management (ESM) templates: Customer service, HR, Facilities, and Legal service management.
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. In team-managed projects, you can only copy workflows within a project and not to another project on your site. Company-managed projects can also be created using the latest IT service management template. Learn how to Migrate between team-managed and company-managed projects.
Feature list
Team-managed and company-managed projects also don’t currently have the same features. Check the feature list below to determine which project type suits your needs:
Company-managed service project | Team-managed service project |
|---|---|
Advanced setup and configuration | Easy setup and reimagined features |
Classic look and feel | Updated look and feel |
Great for expert Jira users | New features added regularly |
Expert configuration | Easy and fast to set up |
Managed by Jira admins | Managed by project members |
Detailed permissions | Simplified permissions |
Advanced workflow editor | Easy to use workflow editor |
Asset management | Asset management |
Language support | Language support |
Approvals | Approvals |
Agent notifications | Agent notifications COMING SOON |
Customer transitions | Customer transitions COMING SOON |
How to choose between a company-managed or team-managed project
Choose a team-managed project if:
Your team wants easier project configuration to get started quickly.
You need an independent project for each team in your organization.
You’re an ESM team who wants to use a project template.
Choose a company-managed project if:
You need consistent workflows across teams.
There are features in company-managed projects that aren’t available in team-managed projects.
You want to use an IT service management template.
Join the Atlassian Community to ask questions, provide suggestions, or find out what's coming soon.
Was this helpful?