Go to Atlassian ID Portal and login with an account you will use to synchronize data from Jira to SGNL
Enter a label for the API key, click Create, and copy the API token that is created
Save the API key in a temporary location. You will need this API key for completing configuration in SGNL
In the Atlassian Admin app, browse to Products and note the Base URL for the Jira Software
Login to the SGNL Console
From the left menu, select Systems of Record
Click “Add System of Record” or “Add”.
The SGNL SoR Catalog will show up on the screen:
Click on “Jira” which will open up the New System of Record screen with some configuration options pre-populated from the Jira SoR template:
Choose the correct adapter that matches the Jira System of Record Type.
Replace all fields that have the {{Input Required:}} placeholder with relevant information. For Jira, the following fields are required:
Click “Continue” to save your Jira System of Record. You will be taken to the Jira System of Record page.
All entities and relationships are created as defined in the Jira template. If applicable, you can edit an entity and modify any properties of the entity or the associated attributes. Hover over the entity on the screen above to see the Edit button as shown above.
You can check the relationships created through the Relationships tab. However, relationships cannot be modified. You will need to delete an existing one, and create a new relationship.
Note that synchronization is disabled by default when a new System of Record is created. You can choose to enable synchronization on Entities individually. Hover over the entity to see the Enable Sync button, and click on it.
Repeat for all Entities you want to synchronize to SGNL. Finally, Enable synchronization for the System of Record.
After some time, SGNL should complete ingesting the data from your Jira instance into the SGNL graph. The number of objects ingested per entity are displayed on the Jira screen. You should then be able to construct policies based on your Jira data and make access evaluation calls to SGNL.
Once ingestion is complete and Jira data is in the SGNL graph, you can use Data Lens to explore the SGNL graph.
In most cases, you will want to reduce the data coming from Jira to only the entities, attributes, and objects that you need to sucessfully evaluate your policies or take action within SGNL. Given that, it’s likely that you will want to make use of filters to reduce that data.
As with other SoRs, you can apply the native JQL filtering syntax for Issues from the SoR, in this case Jira, to the Adapter Config for the System. Filters are configured for Jira Issues and are passed directly to the System of Record at Synchronization time to be evaluated and have only the right data made available to SGNL.
SGNL uses Jira’s JQL filtering syntax for filtering Issues from the System of Record.
Sample Adapter Config
{
"requestTimeoutSeconds": 10,
"localTimeZoneOffset": 43200,
"issuesJqlFilter": "project=SGNL OR project=MVP",
"objectsQlQuery": "objectType = Customer",
"assetBaseUrl": "https://api.atlassian.com/jsm/assets"
}
10