Jira Cloud
Jira is a platform for a software team to track and manage their work. You can bring the issues created in Jira into Brinqa to construct a unified view of your attack surface and strengthen your cybersecurity posture. You can also push the remediation tickets created in Brinqa Platform to Jira.
This document details the information you must provide for the connector to authenticate with Jira Cloud and how to obtain that information from Jira. See create a data integration for step-by-step instructions on setting up the integration.
Required connection settings
Jira Software can be hosted in the cloud or in a data center. If your company uses Jira Cloud, select Jira Cloud from the Connector dropdown when setting up a data integration. If you cannot find the connector in the dropdown, make sure that you have installed it first. You must provide the following information to authenticate Jira Cloud with Brinqa:
-
Service URL: The Jira REST interface URL.
-
Email: The email address of your Atlassian account, which must have permissions to
query,create, anddeleteissues in Jira Cloud. -
API token: The API token created for your Atlassian account.
Create an API Token for your Atlassian account
For the Jira Cloud connector to use the Jira Cloud platform REST API, you must provide an API token. Atlassian does not allow retrieval of an active token, therefore, you must generate a new token instead. To do so, follow these steps:
-
Log in to your Atlassian account.
-
Navigate to API Tokens at https://id.atlassian.com/manage-profile/security/api-tokens.
-
Click Create API token.
-
Enter a label for the token and click Create.
A new API token displays. You cannot view the token again. Copy the API token and save it in a secure location.
-
Set the timezone for the account to UTC. This ensures accurate synchronization of data between Jira and Brinqa, as all data is stored in UTC time.
For additional information on managing API tokens for your Atlassian account, see the Atlassian documentation.
Additional settings
The Jira Cloud connector contains additional options for specific configuration:
-
Project key: The 3- or 4-letter abbreviation of your project name. You can specify multiple projects separated by commas, or you can leave this field blank to bring in all Jira projects.
-
Default issue type: The issue type to use when creating new issues in Jira. The default setting is Bug.
-
Page size: The maximum number of records to get per API request. The default setting is 100. It is not recommended to go over 100. Reducing this value lowers the number of rate limit points consumed per request. See Rate limiting for details.
-
Parallel requests: The maximum number of parallel API requests. The default setting is 4. Higher values increase throughput but also increase the risk of exceeding Jira Cloud rate limits. See Rate limiting for details.
-
Request timeout (secs): The maximum time allotted, in seconds, before a request times out. The default setting is 120 seconds. Although it is not recommended, you can also enter zero (0) to disable timeouts.
-
Maximum retries: The maximum number of times that the integration attempts to connect to the Jira API before giving up and reporting a failure. The default setting is 5.
-
Supports issue linking: Select this option to allow for linking between issues. This option is not selected by default.
-
Convert field values from html to wiki markup: Select this option to convert formatted fields from Jira to wiki markup so that they can be displayed in Confluence. This option is selected by default.
Rate limiting
Jira Cloud enforces rate limiting to protect its APIs from excessive usage. When a rate limit is exceeded, the API returns an HTTP 429 response. Starting in version 3.1.24, the Jira Cloud connector automatically detects these responses and retries the request after the delay specified in the Retry-After header.
Jira Cloud uses three independent rate limiting mechanisms:
-
Points-based quota: Each API call consumes points based on the number of objects returned (1 base point + 1 point per object, or 2 points per user). Quotas reset at the top of each UTC hour. The default shared quota is 65,000 points per hour, though tenants with Standard, Premium, or Enterprise plans may have higher per-tenant quotas.
For example, a single search page of 50 issues costs approximately 51 points, and a full sync of 10,000 issues at that page size consumes approximately 10,200 points. Additionally, the users sync endpoint uses hardcoded large page sizes (up to 5,000 users per request at 2 points each), so a single users page can consume over 10,000 points — roughly 15% of the shared hourly quota.
Because the 65,000-point quota is shared across all applications and integrations on the tenant, conservative settings help avoid contention.
-
Burst rate limit: Limits the number of requests per second to each API endpoint, using a token bucket algorithm with approximately 10 requests per second steady-state and a burst buffer of approximately 100 tokens. Concurrent requests to the same endpoint (controlled by the Parallel requests setting) can drain the burst buffer faster than it refills during heavy sync operations.
Burst limits are per endpoint (e.g.,
/rest/api/3/searchand/rest/api/3/issuehave separate buckets). Hitting the limit on one endpoint does not affect others. -
Per-issue write limit: Restricts how frequently a single issue can be modified. This is relevant when using ticket sync to push or update issues in Jira Cloud.
For additional information on Jira Cloud rate limiting, see the Atlassian documentation.
To manage the Jira Cloud connector's API consumption, adjust the Parallel requests and Page size settings. Use the following recommendations based on your Jira Cloud tenant:
Table 1: Recommended rate limiting configurations
| Tenant Type | Parallel requests | Page size | Notes |
|---|---|---|---|
| Large (per-tenant quota of 100K–500K points/hour) | 4 | 100 | Higher throughput acceptable with dedicated per-tenant quotas. |
| Standard (shared 65K points/hour quota) | 2 | 50 | Conservative settings to stay within the shared hourly quota. |
| Shared environment (multiple integrations on same tenant) | 1 | 25 | Lowest API footprint to avoid contention with other integrations. |
If you experience frequent rate limit errors during data synchronization, try reducing the Parallel requests and Page size values.
Types of data to retrieve
The Jira Cloud connector can retrieve the following types of data from the Jira REST API:
Table 2: Data retrieved from Jira
| Connector Object | Required | Maps to Data Model |
|---|---|---|
| Issue | Yes | Ticket |
| Issue Field | No | Not mapped |
| Issue Status | No | Not mapped |
| Issue Type | No | Not mapped |
| Project | No | Not mapped |
| User | No | Not mapped |
For detailed steps on how to view the data retrieved from Jira Cloud in the Brinqa Platform, see How to view your data.
Operation options
The Jira Cloud connector supports the following operation options. See connector operation options for information about how to apply them.
Table 3: Jira Cloud connector operation options
| Connector Object | Option | All Possible values | Description | Example |
|---|---|---|---|---|
| Issue | issueType | Any Jira issue type. Examples include: Bug, Improvement, or Task | A comma-separated list of Jira issue types. | Key: issueType, Value: Task.This key and value combination only retrieves from Jira all issues of the Task issue type. |
| project | Jira project IDs or project keys | A comma-separated list of Jira project IDs or project keys. | Key: issueType, Value: DEV,OPS. This key and value combination retrieves from Jira all issues from the 'DEV' and 'OPS' projects. | |
| query | A JQL query | A query written in the Jira Query Language (JQL). For additional information on JQL, see Atlassian documentation. | Key: query, Value: reporter = jdoe AND project = DEV. This key and value combination retrieves from Jira all issues reported by 'jdoe' in the 'DEV' project. |
The option keys and values are case-sensitive as they are shown in this documentation.
APIs
The Jira Cloud connector uses the Jira REST API v3. Specifically, it uses the following endpoints:
Table 4: Jira Cloud API endpoints
| Connector Object | API Endpoints |
|---|---|
| Issue | GET /rest/api/3/field |
GET /rest/api/3/issue/{issue.uid} | |
GET /rest/api/3/issue/{issueKey}/editmeta | |
POST /rest/api/3/issue/{issue.uid}/transitions | |
PUT /rest/api/3/issue/{issue.uid}/transitions | |
POST /rest/api/3/issueLink | |
GET /rest/api/3/issueLinkType | |
POST /rest/api/3/search/jql | |
| Issue Field | GET /rest/api/3/issue/createmeta/{projectIdOrKey}/issuetypes/{issueTypeId} |
| Issue Status | GET /rest/api/3/project/{projectIdOrKey}/statuses |
| Issue Type | GET /rest/api/3/project/search |
| Project | GET /rest/api/3/project/search |
| User | GET /rest/api/3/users/search |
Changelog
The Jira Cloud connector has undergone the following changes:
This connector is part of a bundled release with other connectors from the same vendor. If a version shows "No change", it means that the connector version was updated for consistency as part of the bundle, but no functional changes were made to this specific connector. You can update to or skip this version without affecting your existing configuration.
Table 5: Jira Cloud connector changelog
| Version | Description | Date Published |
|---|---|---|
| 3.1.24 | Added support for handling Jira rate limiting (HTTP 429) with automatic retry using the Retry-After header. | March 4th, 2026 |
| 3.1.23 | No change. | February 26th, 2026 |
| 3.1.22 | - Added support for syncing five new object types: Project, Issue Type, Issue Status, Issue Field, and User. - Code refactoring and general maintenance. | February 26th, 2026 |
| 3.1.21 | Changed the endpoint for retrieving issue updates from Jira REST API v3 to v2. | October 27th, 2025 |
| 3.1.20 | The Jira Cloud connector has fully transitioned to the Jira REST API v3. As a result, several deprecated v2 endpoints have been replaced with their v3 equivalents, and the connector now uses the rest/api/3/search/jql endpoint for JQL-based queries. These changes ensure continued compatibility with Atlassian's supported API versions. For a full list of API endpoints, see APIs. | September 15, 2025 |
| 3.1.19 | Fixed an issue where the Issue object sync was failing due to a deserialization error. The connector now properly handles custom fields where the value is returned as a JSON object instead of a string. | March 22nd, 2025 |
| 3.1.18 | Fixed an issue where pushing data to version fields, such as 'Affected version' or 'Fixed version,' from Brinqa to Jira resulted in errors. The connector now properly handles multi-valued fields for versions. | November 18th, 2024 |
| 3.1.17 | Fixed an issue where the status category for issues was not being retrieved by the connector. As a result, the ISSUE_STATUS_CATEGORY attribute was added to the Issue object. | October 28th, 2024 |
| 3.1.16 | Code cleanup and general maintenance. | October 17th, 2024 |
| 3.1.15 | Fixed an issue where only a limited schema was displayed in Brinqa when no project key was defined in the integration configuration, even though the full schema was visible in the Brinqa Agent logs. | September 25th, 2024 |
| 3.1.14 | Code cleanup and general maintenance. | July 2nd, 2024 |
| 3.1.13 | Code cleanup and general maintenance. | May 27th, 2024 |
| 3.1.12 | Code cleanup and general maintenance. | May 20th, 2024 |
| 3.1.11 | Improved parent-child relationships in Jira projects by enhancing the linking of Issues to Epics. | May 10th, 2024 |
| 3.1.10 | No change. | April 8th, 2024 |
| 3.1.9 | Fixed an issue where the connector was timing out when retrieving the schema. | March 28th, 2024 |
| 3.1.8 | Code cleanup and general maintenance. | March 13th, 2024 |
| 3.1.7 | Added more logging for troubleshooting. | December 22nd, 2023 |
| 3.1.6 | Added a date formatter for pushing Date and Date Time attributes. | December 19th, 2023 |
| 3.1.5 | - Fixed an issue where the connector was not pushing all ticket fields to Jira environments. Code cleanup and general maintenance. | October 26th, 2023 |
| 3.1.4 | Enabled you to specify no project or a list of projects when connecting to a Jira server. | August 25th, 2023 |
| 3.1.3 | Code cleanup and general maintenance. | August 11th, 2023 |
| 3.1.2 | Code cleanup and general maintenance. | August 11th, 2023 |
| 3.1.1 | Fixed an issue where the connector sync was failing. | August 9th, 2023 |
| 3.1.0 | Added support for Jira Software version 9.x. | August 8th, 20223 |
| 3.0.3 | Code cleanup and general maintenance. | July 13th, 2023 |
| 3.0.2 | Code cleanup and general maintenance. | February 27th, 2023 |
| 3.0.1 | Added the UID attribute to the Issue object. | January 5th, 2023 |
| 3.0.0 | Initial Integration+ release. | January 3rd, 2023 |