Get started with Jira Service Management for admins
Your first stop for learning how to get started with Jira Service Management.
The Jira Cloud products (Jira, Jira Service Management and Jira Product Management) are standalone applications built on the Jira platform and can be used on its own or in any combination on the same site.
Jira Service Management and Jira can be added to the same cloud site for optimal integration benefits. Our Jira integration page shows the relationship between Jira Service Management and Jira and how it allows for both IT and DevOps to collaborate on issues. Our Jira family page shows the difference between our four flavors of Jira Cloud products.
When it comes to licensing, Jira is licensed based on total users. Jira Service Management is licensed based on total agents (users able to edit/work on requests). Customers (users submitting requests) can access the product for free and do not need a license.
Depending on your setup, users can be licensed to one, all, or any combination of these products. Read on to understand how Jira licensing and roles affect what agents, customers, and other Jira users can do.
Each product delivers a tailored experience to its users, and has an associated project type that in turn offers product-specific features. Here's a list of the project types and their associated features.
Application | Project type | Application-specific feature set |
---|---|---|
Jira Product Discovery | Discovery project |
|
Jira | Business projects |
|
| Software projects |
|
Jira Service Management | Service projects |
|
All users who can log into a Jira site will be able to see all the projects in that instance (pending permissions), but they will only be able to see the product-specific features when they have access.
For example, a software project is able to display information from linked development tools, such as Bitbucket and Fisheye, as well as agile boards, but this information is only viewable by a Jira user. A Jira Service Management user would be able to see the software project, but wouldn't be able to see the software-specific features, like agile boards or the information from linked development tools.
Likewise, a Jira user would not be able to see any Jira Service Management-specific features in a service project (they'll see only a basic view of the project and its issues).
Only a Jira administrator can create a project for an installed product. They don't need application access to create the project, but they do need application access if they'd like to view or use the project.
Anonymous users (people who haven't logged in) will have access equivalent to a business project user. In other words, they can view issues and work in any type of project, but they won't see product-specific features like agile boards, which are software project specific. To know how to allow anonymous users access to projects, see Managing anonymous or public access.
A list of the products, their user roles, and their project-specific features can be found below:
Project-specific feature | Permission | Business project user | Software project user | Service Management agent | Customers | |
---|---|---|---|---|---|---|
Service projects | Customer portal | Create | ||||
View | ||||||
Comment | ||||||
Transition | ||||||
Project level | Create | |||||
View | ||||||
Issue level | Create | |||||
View | ||||||
Internal comment | ||||||
Comment to customer | ||||||
Transition | ||||||
SLA level | Create | |||||
View | ||||||
Queue level | Create | |||||
View | ||||||
Jira Service Management gadgets | View |
By default,