JIRA applications

The JIRA family of applications currently consists of JIRA Software, JIRA Service Desk, and JIRA Core. A JIRA application is built on the JIRA platform, and extends and modifies the base functionality provided by the JIRA platform. For example, the JIRA Software application provides software development features that are not part of the JIRA platform, such as agile boards, linked development tool information (e.g. commits, builds, etc), and software project templates. 

Application-specific information

Click the pages linked below to view more information about each application.

JIRA Software

JIRA Service Desk

JIRA Core 

JIRA Core is a streamlined issue tracker for business teams. Currently, JIRA Core does not have any application-specific functionality that you need to be aware of. JIRA Core's APIs, plugin modules, and project types are the same as those provided by the JIRA platform. There is no additional documentation for JIRA Core. 

Technical overview

An Application is a blob of add-ons that operate together on top of the platform to provide functionality. The add-ons can be divided into three types:

  1. Primary Add-on: The add-on that defines the product. Disabling this add-on will will disable the product. There is only one primary add-on per Application. The primary add-on may also provide Application functionality.
  2. Application Add-on: An add-on providing fundamental features for the Application. All product add-ons must be enabled and working for the product to be considered working. The product add-on is owned by the product (that is, the application add-on will not work without the primary add-on of the Application).
  3. Utility Add-on: An add-on that provides utilities to the primary and/or Application add-ons. A utility add-ons is not owned by the Application (i.e. the utility add-on will work without the primary add-on of the Application) and may be used by multiple Applications or other non-application add-ons.

An Application may be installed, upgraded, disabled, removed, licensed, and have its configuration cleared dynamically.

General information

If you are building for one of the JIRA applications, rather than on the JIRA platform itself, you will also need to be aware of the following:

  • Licensing — Each JIRA application can be licensed individually. You can install one or more applications in JIRA via the Manage applications page. The base JIRA application, JIRA Core, provides basic project tracking capabilities for business teams. All JIRA applications include access to JIRA Core, or you can license JIRA Core only for users that need basic access to JIRA.
  • User management — JIRA administrators can grant access to licensed applications to specific groups (e.g. jira-software-users), via the Application access page in JIRA. Users can then be added to these groups to grant them access to the JIRA applications. Granting access to a user for an application, consumes a seat in the license for that JIRA application. For example, a JIRA administrator could grant a user access to JIRA Software, which would consume one of the seats in the JIRA Software license for that instance.
  • Project types — Installing and licensing an application in JIRA provides additional project types that are specific to that application. For example, installing JIRA Software allows users to create a 'Scrum software development' project type, which has boards, its own workflow, and its own issue types.
  • APIs — The JIRA platform has a set of REST APIs. In addition, each JIRA application has its own REST APIs that allow programmatic access to functionality that is specific to the application. For example, the JIRA Software REST API includes methods to create, modify, and delete sprints.
  • Plugin modules — Plugin modules are UI extension points which add-ons can use to insert content into various areas of the host application's interface. The plugin modules are part of the JIRA platform and therefore are common to all JIRA applications. However, be aware that you can use these modules to access application-specific parts of the user interface. For example, you can add a dropdown to an agile board in JIRA Software by specifying a web-panel module that has a location of 'board-links'.
Was this page helpful?

Have a question about this article?

See questions about this article

Powered by Confluence and Scroll Viewport