Jira Connection Configuration
Our application leverages Jira Rest API for programmatic access while updating Object Schema, Object Type, and Attribute configurations of JSM Assets.
| Info |
|---|
You need help from a Jira Administator for the steps on this page. |
1- Create a Jira Admin User that you will use in the application. I.e. jira_bot@example.com
2- Make sure that the user has a JSM Agent License, too.
3- Login with the bot user and create an API Token. (How to…)
| Info |
|---|
In case the user is an external user then you need to enable API access for the external user first. You may find the related Atlassian Documentation below: https://support.atlassian.com/security-and-access-policies/docs/set-api-token-access/ |
4- Fill in the User Email (jira_bot@example.com), and Jira Access Token for Jira Connection Settings.
5- Jira Service Management Site Name is the first part of your Jira Cloud application URL. For example, if your base URL is https://site-name.atlassian.net Please just enter your "site-name" below.
6- Click “Save & Check Connection”
 |
| Info |
|---|
If you don't get a success message. You need to review user permissions and site allow lists. User Permissions: The user needs to be a Jira Admin and have a JSM User license. Site Allow List: If you are using an IP allow list, then you need to add the Forge IP addresses to your list to be able to access your site via our application. https://piosoftware.atlassian.net/wiki/spaces/WS/pages/1277953/FAQ#Security |
Schema Selection Configuration
You have 2 options in this section. You may create a new Object Schema or use an existing one.
| Info |
|---|
Pro tip: We recommend creating a new Object Schema and storing Azure AD related data separately. This way you will be able to set roles only for the necessary users or groups. Remember that the imported data will include personal data. Follow the guidance from your organization on this matter. |
Option 1:
Fill in the fields. For example:
Object Schema Name: Azure AD
Object Scham Key: AD
Description: Auto-generated Azure AD data.
and click the button.
 |
Option 2:
Select an existing Object Schema and click the button.
| Note |
|---|
In case you already have the same Object Types in your existing schema, we will inform you and expect them to be updated before moving forward. |
| Info |
|---|
Pro tip: Either you chose Option 1 or 2, make sure that you remove the default values from the Object Schema Roles menu. It should look like the following.  Then, only add the relevant users, groups, or apps. |
Import Token Configuration
To be able to import a large amount of data into JSM Assets you must generate a key that allows the application to securely transfer the data (more info).
Please add the Import Token for your External Import configuration in Assets.
1- Click on the Import URL link and configure the import configuration. (You may find it in the Schema Selection Configuration section.)
2- Select the “Import” tab. Click on the “Create Import” button.
 |
3- Select “External Import” and click “Next”.
 |
4- Fill in the Name and Description fields.
 |
5- Click on 3 dots (…) and select “Generate new token”.
 |
6- Copy the token.
 |
7- Paste the token to the Import Token field in Import Token Configuration and click “Save Import Token”
 |
8- Now, it is time to import.