Configuration

Owned by Nikola Zivkovic
Last updated: Sept 29, 2022
4 min read

3DX Connector for Jira configuration has 5 main configuration sections

 

TIF Configuration

In the TIF Configuration section we will establish connection between Jira Cloud and your on-prem 3DExperiance Installation with TIF module installed on top.
In the TIF Connection provide TIF module base URL and credentials. For now, we only support Basic Authentication, and OAuth is behind the corner.

We will provide 3DX Objects which are in the scope of the Integration in the TIF Objects section.
We will pair TIF Object types with their service endpoints on TIF module.

Finally, we will add attributes/fields which are in the scope for this integration.

Jira Configuration

In the Jira Configuration section we’ll configure our mapping attributes:

  1. Which attribute will hold information about target Jira project

  2. Which attribute will determine relation between Jira Issue Type and 3DX Object Type

  3. Which attribute will hold priorities.

Once we have completed mapping criteria configuration, we can configure Jira projects in the scope of integration. By clicking on the “Add Jira Project” button.
In the Project Configuration dialog we need to specify:

  1. Which project we would like to use for the integration

  2. What will be the value of the project mapping attribute (project mapping attribute we have configured in previous section) coming from the TIF.

  3. Sync Direction – one of the unidirectional options or bidirectional.

  4. Jira events – upon which ticket events we will run synchronization.

  5. Use Issue Sync control toggle – enabling option will check if custom field “Sync to 3DX” has option of “Yes” set prior to triggering synchronization, this is useful option if one do not want to create 3DX object immediately after starting Jira ticket, option applies only for bidirectional and Jira to 3DX synchronization.

  6. Project Enabled toggle – controls if synchronization is enabled for project or not, advised is to leave this option disabled until complete configuration is carried (Field mappings, Priority mappings, Issue Type Mappings ..etc)

During installation, app will create custom field named “Sync to 3DX“, if you configure your project to “Use Issue Sync Control“, you should add custom field to the edit screen of your project.
By setting this field value to Yes or No, synchronization will be enabled on the ticket granularity or stopped.

 

Field Mappings


Field Map will determine relation between Jira Issue Type fields and 3DX Object attributes, you must define mandatory field set (Required fields during issue Create Screen) for Jira Issue to be created, otherwise Issue Creation from 3DX Object will fail.
Out of the box App has Default Field Map defined, one is not able to delete this Map, in simple deployment scenarios Default Map is enough as it will be applied to all Configured Jira Projects which doesn’t have dedicated Field Map, if Project Specific Field Map is required it’s simple to create it by clicking on the “Add Field Map” button.
Later on, we will use defined Field Mappings in the Issue Type Mappings Configuration.

 

Priority Mappings


Since different set of priorities might be there between 3DX Platform and Jira, we need to define mapping for these values, you can edit Default Priority Map and add mapping values, or you can define project specific priorities if 3DX Platform has different set of priorities for different Object types, by clicking on the “Add priority Map” button. All priorities from Jira and 3DX must be mapped to avoid synchronization problems.

Issue Type Mappings


Issue Type Map is place where we map 3DX Object type to Jira Issue Type and tie it to specific Field Map. Issue Type Map can be Default, applied to all projects without specific Issue Type Map or project specific. To Create Project specific Issue Type Map click on the “Add Issue Type Map” button.

 

TECHNIA CONFIDENTIAL