Installation requirements in Jira Service Management
Jira Service Management licensing overview
The Jira family of applications (Jira Software, Jira Service Management, Jira Core) are built on the Jira platform and can be used in any combination on the same instance. Depending upon of your setup, users can be licensed to one, all, or any combination of these applications. Read on to understand how Jira Service Management licensing and roles affect what agents, customers, and other Jira application users can do.
If you're a Jira administrator, check out more information on Licensing and application access.Application features and project types
Each application delivers a tailored experience for its users, and has an associated project type which in turn offers application specific features. Below is a list of the project types, and their associated application specific features.
| Application | Project type | Application specific feature set |
|---|---|---|
Jira Core |
|
|
Jira Software |
|
|
Jira Service Management |
|
|
All users that can log in to a Jira instance will be able to see all the projects in that instance (pending permissions), but they will only be able to see the application-specific features when they have application 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 Software user. A Jira Core user would be able to see the Software project, but would not be able to see the Software-specific features, like agile boards or the information from linked development tools. Likewise, a Jira Software user would not be able to see any Jira Service Management application-specific features on a service project, only a basic view of the project and its issues.
- Only a Jira administrator can create a project for an installed application. They do not 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 will have access equivalent to Jira Core users. In other words, they can view issues and work in any type of project, but they won't see application-specific features, e.g. agile boards, which are Jira Software-specific features. To know how to allow anonymous users access to projects, see Allowing anonymous access to your instance.
A list of the applications, their user roles, and their project's application-specific features can be found below:
Jira Core | Jira Software | Jira Service Management | ||||
|---|---|---|---|---|---|---|
| Jira-Core-user | Jira-Software-user | Jira-ServiceDesk-agent | Customers | |||
Service Projects | Project level | Create |  | |  | |
View | | | | | ||
| Issue level | Create | | | | | |
| View | | | | | ||
| Comment | | | | | ||
| Transition | | | | | ||
| SLA level | Create | | | | | |
| View | | | | | ||
| Queue level | Create | | | | | |
| View | | | | | ||
| Jira Service Management gadgets | View | | | | | |
