Jira product overview

The Jira family of products are built on the Jira platform. Jira Core is the default product of the Jira platform, and is always part of your Jira site. You can add Jira Software and Jira Service Management to add extra functionality and project templates to your Jira site. A user may require access to one, all, or any combination of these products.

Product features and project types

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.

ApplicationProject typeApplication-specific feature set

Jira Core

Business projects
  • Available to all licensed users
  • Templates for HR, legal, and other business teams.

Jira Software

Software projects
  • Integration with development tools
  • Agile boards
  • Release hub for software versions

Jira Service Management

Service projects
  • Service Level Agreements (SLAs)
  • A customizable web portal for customers
  • Permission schemes allowing customer access

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 Software user. A Jira Core 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 Software 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 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 product-specific features like agile boards, which are Jira Software-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 featuresPermissionJira-Core-userJira-Software-userJira-ServiceDesk-agentCustomers
Business projects
Project levelCreate
(tick)
(tick)
(tick)
(error)
View
(tick)
(tick)
(tick)
(error)
Issue level


Create
(tick)
(tick)
(tick)
(error)
View
(tick)
(tick)
(tick)
(error)
Comment
(tick)
(tick)
(tick)
(error)
Transition
(tick)
(tick)
(tick)
(error)
Jira GadgetsView
(tick)
(tick)
(tick)
(error)

Software projects






Project levelCreate
(error)
(tick)
(error)
(error)
View
(tick)
(tick)
(tick)
(error)
Issue level



Create
(tick)
(tick)
(tick)
(error)
View
(tick)
(tick)
(tick)
(error)
Comment
(tick)
(tick)
(tick)
(error)
Transition
(tick)
(tick)
(tick)
(error)
View Development
Information
(error)
(tick)
(error)
(error)
View Release information
(error)
(tick)
(error)
(error)
Board levelCreate
(error)
(tick)
(error)
(error)
View
(error)
(tick)
(error)
(error)

Jira Software gadgets

View
(error)
(tick)
(error)
(error)

Service projects








Project levelCreate
(error)
(error)
(tick)
(error)

View

(tick)
(tick)
(tick)
(tick)
Issue level


Create
(error)
(error)
(tick)
(tick)
View
(tick)
(tick)
(tick)
(tick)
Comment
(tick)
(tick)
(tick)
(tick)
Transition
(error)
(error)
(tick)
(error)
SLA levelCreate
(error)
(error)
(tick)
(error)
View
(error)
(error)
(tick)
(error)
Queue levelCreate
(error)
(error)
(tick)
(error)
View
(error)
(error)
(tick)
(error)

Jira Service Management gadgets

View
(error)
(error)
(tick)
(error)