Skip to main content

Jira

Visualize Jira projects, users, and issues, map Jira users to employees, and monitor changes through queries and alerts.

Installation​

To use this integration, JupiterOne requires the hostname for your Jira organization. JupiterOne also requires the username/email and an API key for a user having the correct permissions granted.

note

The integration supports Jira Cloud with Jira API v3 and Jira Data Center with Jira API v2. Other setups may work.

Configuration in Jira​

Configure an User for API Access​

Option 1 - Create a New User

  1. Create a new service account for JupiterOne use or use an existing account.
  2. Log in to Jira and navigate to User Management.
  3. Send an invite to the service account.

Option 2 - Leverage an Existing User

Before you use an existing user, you should verify the appropriate permissions are configured/can be added to the account (see the Permissions section below).

Ensure you have the ability to log in to the user's Jira account.

Permissions​

  1. Authorize the user to read groups and users by granting the "Browse Users" global permission. This allows JupiterOne to provide visibility into Jira access.

  2. Authorize browse access to projects configured in JupiterOne. Use group, project, role, and issue security features of Jira to manage the user's access. Note that restricting to read-only access will require explicit removal of write permissions. Please see the Jira article on How to Create a Read Only User.

  3. Authorize "Create Issues" permissions in projects that serve as JupiterOne Alert Rule action targets.

Create an API Token​

Log in to Jira as the JupiterOne user and follow the Jira guide to create an API token.

Configuration in JupiterOne​

To install the Jira integration in JupiterOne, navigate to the Integrations tab in JupiterOne and select Jira. Click New Instance to begin configuring your integration, providing the following:

  • The Account Name used to identify the Jira account in JupiterOne. Ingested entities will have this value stored in tag.AccountName when the AccountName toggle is enabled.

  • Description to assist in identifying the integration instance, if desired.

  • Polling Interval that you feel is sufficient for your monitoring needs. You may leave this as DISABLED and manually execute the integration.

  • Hostname of your organization.

  • User Email used to authenticate with Jira.

  • User Password associated with the user email, or the API Key if the password requires MFA.

  • Project Keys that the integration will retrieve data from.

Click Create once all values are provided to finalize the integration.

Next steps​

Now that your integration instance has been configured, it will begin running on the polling interval you provided, populating data within JupiterOne. Continue on to our Instance management guide to learn more about working with and editing integration instances.