Note: This early access program has concluded. Team-managed projects are available for all Atlassian customers on Jira Service Management cloud.
Hello Jira Service Management Community!
You may already be familiar with team-managed projects as they’re currently available in Jira Software and Jira Work Management. We’re now giving you an opportunity for early access to team-managed projects in Jira Service Management.
Much as the name implies, these projects are set up and maintained by your team (project admins), unlike company-managed projects which require site/org admins to manage.
Team-managed projects are great for teams with basic request management use cases who want to get started quickly and create their own service project without impacting settings or shared configurations across the organization.
I’ve outlined the main differences between team-managed projects and company-managed projects in the table below:
Team-managed service project (early-access) |
Company-managed service project (default) |
---|---|
Simplified configuration to get started quickly |
Advanced configuration that can be customized and shared across projects |
Projects that are set up and maintained by your project admins |
Projects that are set up and maintained by your site/org admins |
Role-based permissions |
More granular permissions |
Ideal for basic request management use cases |
Ideal for more robust incident and change management use cases |
Once enabling team-managed projects for your instance, every time you create a new project, you’ll have the option to create it as either a team-managed project or company-managed project.
See how easy it is to get up and running with a team-managed project:
While a major benefit of team-managed projects is that agents and project admins can be empowered to easily spin up their own service desks, you can restrict who can create them by navigating to System > Global Permissions and editing the Create team-managed projects setting.
Some other things to note:
For team-managed projects, workflows and statuses can be copied to other request types within a project, but not between projects.
If you decide to switch project types (team-managed to company-managed or vice versa) after you create a project, you’ll need to create a new project.
Shared fields for Assets is not currently supported in team-managed projects, but will be in the next few months.
If you’re a site/org admin who configures Jira Service Management and would like to be a part of this program, please sign up via our service desk.
We’ll be keen for your feedback as you help us shape the future of team-managed projects.
Best regards,
Jehan
Product Manager, Jira Service Management
P.S. Team-managed projects are already enabled in Jira Service Management instances created before April 2020. If you already have access, feel free to leave feedback in the comments here.
Jehan Gonsalkorale
4 comments