Get started with Jira Service Management for admins
Your first stop for learning how to get started with Jira Service Management.
By default, anyone can create team-managed projects. Out of the box, Jira Service Management gives end users the Create team-managed projects global permission. Jira admins can prevent users from creating team-managed projects by managing which groups are granted this permission. Read more about global permissions.
To find out if you can create your own project, choose Projects in the navigation bar. If you see the Create project option, then you're all set. If not, check with your Jira admin for help creating a project.
To create a team-managed service project:
Choose Projects > Create project.
Select Service Management under Project templates or Jira Service Management under Products.
Learn more about the available templates and select a template.
View the detailed information on the template and choose Use template.
Choose project type: Team-managed.
Give your project a name. You can change your service project template by selecting Change template.
Choose who can access your project.
Select Create.
We automatically generate a project key when the service project is created.
In team-managed service projects, you can edit the following project details:
icon, which helps teams across your Jira site visually identify your service project
name, which appears when people in your Jira site search, browse directories or use the project switcher
key, which is typically the shorthand version of the service project's name
category, which helps larger organizations label and filter similar projects and service projects in directories
project lead, who is usually the project administrator for your team-managed service project
default assignee, which is a role to which all requests created in the project are assigned to
To change these details: From your project's sidebar, select Project settings > Details.
Icons help give a face to your service project's name. They appear in the service project sidebar and in your site's list of all other Jira projects.
To change your service project's icon:
From your project's sidebar, select Project settings > Details.
Under the current icon, select the Change icon.
Choose from a default icon or upload your own.
Select Save details.
Only organization, site, and Jira admins can edit a project key.
Project keys provide a shorthand for the requests in your service project. Together with an request's sequential number, they form a unique identifier called an “issue key”. This abbreviation is the foundation of how work is tracked and referred to in Jira Service Management. You’ll see issue keys:
On requests themselves, as a label
In search results and saved filters
In your queues and reports
In links connecting pieces of work
In the request's URL
Anywhere you need to reference the work you're tracking
Before making any significant changes, it’s a good idea to back up your Jira site to ensure important information isn’t lost.
You won't be able to create a new project with the previous project key. The previous project key will only become available if you delete it from the project it was previously associated with, or if that project is deleted.
If you change a project key, all issues associated with the project will be updated with the new project key.
If you use Confluence with Jira, the Jira issue macros in Confluence will continue to work. If you don't see the change straight away, allow some time for the cache to refresh.
Links containing the old project key will continue to work; however, link aliases within descriptions will not be updated with the new project key.
For example, if you have a link to an issue 'EXAMPLE-1' in the description of an issue, and you change the project key from 'EXAMPLE' to 'DEMO', the alias 'EXAMPLE-1' will not be updated to 'DEMO-1'. But the link will still direct you to DEMO-1.
After you change a project key, we recommend communicating the change to your users. You will need to update any links, filters, and queries with the new project key.
To change your team-managed project key:
Select Project settings, then Details.
In the Project key field, enter your desired project key. It must:
be at least two characters long
start with an uppercase letter
contain only uppercase letters or numbers
Select Save.
Only organization, site and Jira admins can delete a previous project key.
Whenever you change your project key, we automatically save your previous project keys. This ensures any links, filters, and queries using your previous key continue working.
In some cases, you may need to delete a previous project key from its associated project so you can use it for a new project. Deleting a previous project key can impact anything that is still using that project key, including:
links
board filters
dashboard filter gadgets
JQL queries
We recommend letting users know before you delete your previous project key so that they can update any links, filters or queries using the previous project key.
To delete a previous project key:
Select Project settings, then Details.
In the Previous project keys field, delete the relevant project key.
Select Save.
Project categories help group similar software, service, and business projects across your Jira site. They can be used in advanced search, filters, reports, and more. Your Jira admin creates and manages the categories that are available. Learn more about adding and deleting project categories.
To assign or change your project's category:
From your project's sidebar, select Project settings > Details.
Under Category, use the dropdown to assign your project a category.
Select Save details.
The project lead in a team-managed project is usually the project administrator, who controls and manages a project's settings.
You may want to change the project lead as people move in and out of your team in a longer-term project.
To change your project's lead:
From your project's sidebar, select Project settings > Details.
In the Project lead field, set a new person to lead the project.
Select Save.
When requests are created in your project, you can set a default assignee. This is useful for open projects where everyone on the site can report tasks to your project.
The default assignee is typically a team member who prioritizes or validates that reported requests are meant for their team and distributes these tasks to their team members accordingly. By default, they receive a notification when someone creates a request in the project.
If you’re not able to change the default assignee, then check if you’ve enabled Allow unassigned issue under system Jira’s general configuration. Learn more about configuring Jira application settings.
To change your project's default assignee:
From your project's sidebar, select Project settings > Details.
In the Default assignee field, nominate your project's default assignee.
Select Save.
The default assignee can only be either Unassigned, or the Project lead. If you want a specific person to be the default assignee, you'll need to change the Project lead.
As Jira admins or project leads, you can get rid of service projects that you don't need by moving them to the trash. The service project along with its requests, queues, automation rules, SLAs, and reports will be available in the trash for 60 days after which they will be permanently deleted.
From the trash, Jira admins can:
View when a project was moved to trash
View the user who moved the project to trash
View when a project will be permanently deleted
Restore a project that was moved to trash
Permanently delete a project
Learn more about trash, archive, restore, and delete service projects.
Was this helpful?