Installation and Authentication

Enhancing Jira with Diverse Installation and Authentication Choices


Explore the different installation options for Jira Assist—Extension, Cloud App, and Web version. Each option offers distinct advantages and authentication methods to suit your preferences. Choose from integrated single-click authentication, OAuth with Jira, or traditional username and password/API key authentication. Whether you prefer the seamless integration of the Extension, the convenience of the Cloud App, or the flexibility of the Web version, Jira Assist provides versatile solutions to enhance your Jira experience.

Types of Authentication

Jira Assistant offers multiple authentication options to cater to different security levels and user preferences. Each option has its own set of advantages and limitations:

1. Single Click Integration by reusing browser session

Single Click Integration is the most secure authentication option as it relies on the browser's authenticated session with Jira, ensuring that only authorized users can access Jira Assistant.


  • Utilizes the browser's default authenticated session with Jira, ensuring a secure connection.
  • Users don't need to provide credentials, simplifying the authentication process.
  • Allows quick and seamless access to Jira Assistant without the need to keep the Jira tab open.


  • Requires users to be logged in to Jira every time they use Jira Assistant.
  • Works only when browser extension is installed

2. OAuth with Jira

OAuth with Jira provides enhanced security through one-time consent and eliminates the need for storing user credentials, enhancing the overall user experience.


  • Requires one-time consent in Jira, enhancing security and user control.
  • Eliminates the need to store user credentials as authentication is managed via an API.


  • Auth tokens are stored in the browser cache for subsequent use
  • Currently supported for cloud Jira instances only; datacenter instances require custom solutions. Contact developer for assistance.
  • The Sprint Report feature is not available when using OAuth authentication.

3. Basic authentication using Username and Password / API Key

Basic authentication is a fallback option for cases where more secure methods are not feasible, but it should be used with caution due to security risks.


  • Allows users to authenticate using their Jira credentials or an API key.
  • Can be used when other authentication methods are not feasible or preferred.
  • Works with both Jira cloud and datacenter version


  • Considered the least secure option as it involves storing credentials (encoded) in the browser cache.
  • Recommended only when other authentication methods are not available or suitable.

Exploring Installation Options

1. Browser Extension

The Extension Version installation provides a convenient way to integrate Jira Assistant with popular browsers, offering Quick View functionality and support for various authentication methods. However, users need to install it individually.


  • Available for popular browsers like Chrome, Edge, Opera, and Firefox.
  • Supports all three authentication methods, providing flexibility for users.
  • Includes the unique Quick View feature for seamless access to dashboards.
  • Provides a centralized settings storage mechanism for better user management.


  • May not be officially supported in some chromium-based browsers like Vivaldi.
  • Requires installation for each user individually.
  • Not suitable if users are not allowed to install extensions

2. Jira Cloud App

The Jira Cloud App installation offers a seamless integration within Jira Cloud, providing secure storage for authentication related information. It eliminates the need for individual installations, making it immediately available to all users within the Jira instance.


  • Installed within Jira Cloud, eliminating the need for browser extensions.
  • Utilizes OAuth authentication for enhanced security with one-time user consent.
  • Accessible to all users once installed, without individual installations.


  • Settings and pending worklog data are still stored within browser cache only and so has to stick on to same browser.
  • Only applicable for Jira Cloud instances; not compatible with datacenter versions.
  • Does not support the Sprint Report feature due to OAuth authentication.
  • Requires admin access during installation, but subsequent usage doesn't need admin rights.

3. Web Version

The Web Version option offers flexibility for custom hosting, ensuring regular updates, and provides a browser-based interface to access Jira Assistant's features. It's easily accessible to all users, making it a suitable choice for those who need quick access without individual installations. Read more about benefits of Web version.


  • Hosted as a static web app, accessible via a browser.
  • Allows custom hosting if not interested to use public version
  • Receives updates for bug fixes and feature enhancements regularly.
  • Accessible to all users without needing individual installations.
  • Can stand alone and store its own setting or integrate with extension and share data settings from extension


  • Requires internet access at all times to use, unlike other options.
  • For datacenter instances using OAuth authentication needs self hosting and custom implementation.