Jira Insight
The JSM Insight connector integrates with Jira Service Management's Insight (Assets) module on on-premise Jira Server instances. It synchronizes asset and configuration item data from Insight object schemas into the Brinqa platform. The connector uses dynamic schema discovery — object types and their attributes are resolved at runtime from the configured Insight schema, meaning the data model is entirely driven by the Insight configuration rather than being hardcoded.
This document details the information you must provide for the connector to authenticate with Jira Insight and how to obtain that information from Atlassian. See create a data integration for step-by-step instructions on setting up the integration.
Required connection settings
When setting up a data integration, select Jira Insight from the Connector dropdown. 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 Insight with Brinqa:
- Jira Server URL: Jira Server URL.
- Username: Username with Insight access.
- Password: Password for the user.
- Insight schema name or key to sync: Insight schema name or key to sync.
The connector authenticates using Basic Authentication with preemptive credential submission. It establishes an AuthCache with a BasicScheme to send credentials preemptively on every request, avoiding an additional round-trip for authentication challenges.
Additional settings
The Jira Insight connector contains additional options for specific configuration:
- 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.
- Parallel requests: The maximum number of parallel API requests. The default setting is 1.
- Maximum retries: The maximum number of times that the integration attempts to connect to the Jira Insight API before giving up and reporting a failure. The default setting is 10.
- Use cached schema when available: Use cached schema when available. The default setting is true.
- Skip SSL/TLS certificate verification: Skip SSL/TLS certificate verification. The default setting is false.
Types of data to retrieve
The Jira Insight connector can retrieve the following types of data from the Jira Insight API:
Table 1: Data retrieved from Jira Insight
Unlike other connectors with fixed models, the Insight connector uses dynamic schema discovery. The object types (models) and their attributes are determined at runtime based on the configured Insight schema. Each ObjectType defined in the Insight schema becomes a separate model, and each ObjectTypeAttribute becomes an attribute on that model.
| Connector Object | Required | Maps to Data Model |
|---|---|---|
{ObjectType.name} (dynamic) | Yes | {ObjectType.name} (same as connector object) |
For detailed steps on how to view the data retrieved from Jira Insight in the Brinqa Platform, see How to view your data.
The Jira Insight connector does not currently support operation options for the types of data it retrieves.
Data Discovery Flow
The connector discovers the Insight schema in the following order:
Model Relationship Diagram
Attribute mappings
Expand the sections below to view the mappings between the source and the Brinqa data model attributes.
{ObjectType.name} (dynamic)
Each object type within the configured Insight schema is synchronized as an independent model. Common examples include Business Service, Host, Application, Network Device, etc. — but the actual types depend entirely on the Insight schema configuration.
Table 2: Standard attribute mappings
These attributes are always present on every synced object, regardless of the schema configuration:
| Attribute Name | Source Field | Description |
|---|---|---|
objectId | ObjectEntry.id | Object numeric ID |
objectKey | ObjectEntry.key | Object key (e.g., SCHEMA-123) |
UID | ObjectEntry.id | Unique object identifier |
Table 3: Dynamic attribute mappings
All other attributes are resolved from the Insight schema at runtime. Attribute names are normalized — converted to uppercase with spaces replaced by underscores (e.g., IP Address → IP_ADDRESS).
| Attribute Type ID | Type | Java Type | Value Resolution |
|---|---|---|---|
0 (Default) | Text | String | Direct value |
0 (Default, id=1) | Integer | Integer | Parsed as integer |
0 (Default, id=2) | Boolean | Boolean | Parsed as boolean |
0 (Default, id=3) | Float | Double | Parsed as double |
0 (Default, id=4,5,6) | Date/Time/DateTime | Long (epoch ms) | Parsed as Instant → epoch millis |
1 | Object Reference | String | Display value or referenced object ID |
2 | User | String | UserObject.name |
3 | Confluence | String | Direct value |
4 | Group | String | GroupObject.name |
5 | Version | String | VersionObject.name |
6 | Project | String | ProjectObject.key |
7 | Status | String | StatusObject.name |
APIs
The Jira Insight connector uses the Insight REST API. Specifically, it uses the following endpoints:
Table 4: Jira Insight API Endpoints
| Connector Object | API Endpoint |
|---|---|
{ObjectType.name} (dynamic) | GET /rest/insight/1.0/objectschema/list |
GET /rest/insight/1.0/objectschema/{schemaId}/objecttypes/flat | |
GET /rest/insight/1.0/objecttype/{objectTypeId}/attributes | |
GET /rest/insight/1.0/iql/objects |
Changelog
The Jira Insight 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 Insight Changelog
| Version | Description | Date Published |
|---|---|---|
| 3.1.25 | Initial Integration+ release. | May 15th, 2026 |