Asset synchronization setup
In addition to synchronizing Customers and Contacts to Jira organizations and customers, DYCE Connector for Jira Service Management can synchronize Customers, Contacts, Projects and Service Assets to Jira as Jira Assets (Insight) objects. Asset synchronization builds on the same OAuth2 mechanism described in Setup, but needs its own scopes and one additional piece of configuration.
Prerequisites
- Jira Assets (Insight) enabled on the Jira Service Management site.
- The general DYCE Connector for Jira Service Management setup already completed, or being set up alongside asset synchronization.
- Rights to edit the OAuth 2.0 app used, in the Atlassian Developer Console.
OAuth2 setup for assets
Asset synchronization uses the same Jira OAuth2 Setup table as Organization and Customer synchronization, typically as its own setup record because it needs a different set of scopes. On the Jira OAuth2 Setup List, select Create Assets Setup to create a ready-to-use setup with setup code ASSETS-OAUTH, the default Base URL (https://api.atlassian.com), and all required scopes already applied. If a setup with this code already exists, confirm to overwrite it.
Add the same scopes to the OAuth 2.0 app in the Atlassian Developer Console - see Registering the OAuth 2.0 app in Atlassian for the general steps. A separate app can be registered for assets, or the existing one extended with the additional scopes below.
Required scopes
| Scope | Purpose |
|---|---|
offline_access | Obtain a refresh token so access tokens can be renewed automatically |
read:jira-user | Read Jira user information (used to test the connection) |
read:jira-work | General read access to Jira |
read:servicedesk-request | Read service desk requests |
read:cmdb-object:jira | Read Jira Assets objects |
write:cmdb-object:jira | Create and update Jira Assets objects (Customer, Customer Employee, Project and Service Asset synchronization) |
read:cmdb-schema:jira | Read Jira Assets schemas |
write:cmdb-schema:jira | Create and update Jira Assets schemas |
read:cmdb-type:jira | Read Jira Assets object types |
write:cmdb-type:jira | Create and update Jira Assets object types |
read:cmdb-attribute:jira | Read Jira Assets attribute definitions |
write:cmdb-attribute:jira | Create and update Jira Assets attribute definitions |
read:cmdb-config:jira | Read Jira Assets workspace configuration (used to look up the Workspace ID) |
Create Assets Setup on the Jira OAuth2 Setup List already applies all of the scopes above - add them manually only if the setup is created a different way.
Authorizing and finding the Workspace ID
Authorization works the same way as for any other OAuth2 setup - see Authorizing with Atlassian.
Jira Assets additionally identifies the target workspace by a Workspace ID, shown on the OAuth2 setup card. Once authorized, select Lookup Workspace ID to discover and fill it in automatically. Asset synchronization fails with a missing workspace error until this field is populated.
Permissions
Asset synchronization uses the same permission sets as the rest of the connector - Read, Edit and Admin - extended to also cover the asset schema, object type, attribute and field mapping tables, and the Service Asset table. No separate permission set is needed.