Jira Insight
Asset Management- Overview
- Setup
- Data & mappings
- Operations & API
- Changelog
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.
Data retrieved from Jira Insight
| Connector Object | Required | Maps to Data Model |
|---|---|---|
| Dynamic Object Type | Yes | Dynamic Object Type |
Model relationships
For detailed steps on how to view the data retrieved from Jira Insight in the Brinqa Platform, see How to view your data.
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.
Connection settings
When setting up a data integration, select Jira Insight from the Connector dropdown and provide the following:
| Setting | Required | Default | Description |
|---|---|---|---|
| Server URL | Yes | Default - (user input, Required) | Jira server URL |
| API token | No | Default - (user input) | API token for bearer token authentication. When provided, username and password are not required. |
| User name | No | Default - (user input) | User with proper access to query, create, and delete insight objects. Required only when not using a personal access token. |
| Password | No | Default - (user input) | Credentials for the user. Required only when not using a personal access token. |
| Schema | Yes | Default - (user input, Required) | Insight schema name or key |
| Page size | No | 100 | Maximum number of records to get per API request |
| Parallel requests | No | Available processors (capped at 4) | Maximum number of parallel API requests |
| Schema Cache | No | true | Use cached schema when available |
| SSL / TLS | No | false | Skip certificate verification |
Authentication
The connector supports two authentication methods:
Method 1 — Personal Access Token (Recommended)
Bearer token authentication using a Jira Personal Access Token (PAT). This is the recommended method for environments where basic authentication is disabled or restricted for security/compliance reasons.
Authorization: Bearer {apiToken}
When a PAT is configured, username and password fields are not required.
Method 2 — Basic Authentication (Username + Password)
HTTP Basic Authentication with preemptive credential submission. This is the legacy method retained for backwards compatibility.
Authorization: Basic base64({username}:{password})
The connector establishes an AuthCache with a BasicScheme to send credentials preemptively on every request, avoiding an additional round-trip for authentication challenges.
Sync Behavior
Insight objects are synchronized incrementally through a sync token that carries the timestamp of the last successful sync (syncToken, epoch millis). When a sync token is present, the per-object-type IQL query is constrained with Updated >= "<yyyy-MM-dd HH:mm>", so only objects modified since the previous sync are retrieved. On the initial run — when no sync token exists — every object of each type in the configured schema is fetched.
How to obtain Jira Insight credentials
Obtain the required credentials (url, schemaNameOrKey) from your Jira Insight administrator or the Jira Insight admin console, then enter them in the connection settings above.
If both a Personal Access Token and username/password are provided, the PAT takes precedence and bearer token authentication is used.
† Either apiToken or both username + password must be provided. When an API token is configured, username and password are ignored.
Attribute mappings
Expand the sections below to view the mappings between the source and the Brinqa data model attributes:
Dynamic Object Type
| Source Field Name | SDM Attribute |
|---|---|
(text) | Default |
| 1 | Default |
| 2 | Default |
| 3 | Default |
4, 5, 6 (Date / Time / DateTime) | Default |
| :-------------------------------------- | :----------------- |
| Default Type ID | Attribute Type |
| ObjectAttribute / ObjectAttributeValue | {Normalized attribute name} (dynamic) |
ObjectEntry.id | UID |
ObjectEntry.id | objectId |
ObjectEntry.key | objectKey |
| — | Object Reference |
| — | User |
| — | Confluence |
| — | Group |
| — | Version |
| — | Project |
| — | Status |
Operations & API
Expand each connector object to see its operation options, delta-sync behavior, and the API it uses. See connector operation options for how to apply operation options (keys and values are case-sensitive).
Dynamic Object Type
Operation options
This object does not support any operation options.
Delta sync
Supported.
API
- Type: REST endpoint · Endpoint:
GET /rest/insight/1.0/iql/objects
Changelog
The Jira Insight connector has undergone the following changes:
| Version | Description | Migration Steps |
|---|---|---|
| 3.2.3 | No changes in this release. | N/A |
| 3.2.2 | No changes in this release. | N/A |
| 3.2.1 | No changes in this release. | N/A |
| 3.2.0 | New Features - Added support for Personal Access Token (PAT) / Bearer token authentication, enabling use in environments where basic username/password authentication is disabled or restricted. - When a PAT is configured, the connector sends a Bearer authorization header instead of using HTTP Basic Auth. - Username and password fields are now optional when a PAT is provided. | N/A |
| 3.1.26 | No changes in this release. | N/A |
| 3.1.25 | No changes in this release. | N/A |
| 3.1.24 | No changes in this release. | N/A |
| 3.1.23 | No changes in this release. | N/A |
| 3.1.22 | No changes in this release. | N/A |
| 3.1.21 | No changes in this release. | N/A |
| 3.1.20 | No changes in this release. | N/A |
| 3.1.19 | No changes in this release. | N/A |
| 3.1.18 | No changes in this release. | N/A |
| 3.1.17 | No changes in this release. | N/A |
| 3.1.16 | No changes in this release. | N/A |
| 3.1.15 | No changes in this release. | N/A |
| 3.1.14 | No changes in this release. | N/A |
| 3.1.13 | Improvements - Object attribute values are now keyed by the same normalized attribute names used in the schema, keeping each object's data consistent with its attribute definitions. | • Insight objects: Attribute values are now stored under normalized attribute names. Action: re-sync Insight objects so existing data is realigned to the updated attribute identifiers. |
| 3.1.12 | Improvements - Insight object attributes are now identified by normalized names (uppercased, with spaces replaced by underscores) instead of raw numeric attribute IDs, making mapped attributes easier to recognize and reference. | • Insight objects: Attribute identifiers have changed from numeric IDs to normalized names. Action: re-sync Insight objects and update any mappings that referenced the previous attribute identifiers. |
| 3.1.11 | No changes in this release. | N/A |
| 3.1.10 | No changes in this release. | N/A |
| 3.1.9 | No changes in this release. | N/A |
| 3.1.8 | No changes in this release. | N/A |
| 3.1.7 | No changes in this release. | N/A |
| 3.1.6 | No changes in this release. | N/A |
| 3.1.5 | Overview The JSM Insight connector integrates with Jira Service Management Insight (Assets) to synchronize the objects defined in an Insight object schema, along with their attributes. Category: Asset Management Models | N/A |
| 3.1.4 | No changes in this release. | N/A |
| 3.1.3 | No changes in this release. | N/A |
| 3.1.2 | No changes in this release. | N/A |
| 3.1.1 | No changes in this release. | N/A |
| 3.1.0 | No changes in this release. | N/A |
| 3.0.4 | No changes in this release. | N/A |
| 3.0.3 | No changes in this release. | N/A |
| 3.0.2 | No changes in this release. | N/A |
| 3.0.1 | No changes in this release. | N/A |
| 3.0.0 | No changes in this release. | N/A |