Looking for the previous version? View v2024.06 documentation →
Third Party Integrations
Connect Data Trust with Jira and Azure DevOps for seamless issue and work item management.
Overview
The Third Party Integrations section in System Preferences allows administrators to connect Data Trust with external project management and DevOps platforms. Currently supported integrations include Jira (for issue tracking) and Azure DevOps (for work items, repositories, and pipelines). Once an integration is configured, users can create and link issues or work items directly from Data Trust screens without switching applications.
Prerequisites
- You are logged in to Data Trust with an Admin Pro-User role.
- Admin Console access has been granted by your system administrator.
- Valid Jira or Azure DevOps credentials and instance URLs are available.
Navigating to Third Party Integrations
Path: Data Trust › Admin Console › System Preferences › Third Party Integrations
Navigate to Admin Console and select System Preferences to find the Third Party Integrations tile for configuring external platform connections. Admin Pro-User access is required to add or modify third-party integrations, as these settings affect all users who can create or link issues from Data Trust. Have your Jira or Azure DevOps credentials and instance URL ready before opening this configuration area.
The System Preferences page shows all available platform configuration tiles; locate Third Party Integrations in the grid to manage connections to Jira and Azure DevOps. The tile grid is organised by configuration category — scroll down if Third Party Integrations is not in the first visible row. Clicking the tile opens the integration management page where separate sections for Jira and Azure DevOps are displayed.
The Third Party Integrations page lists all currently configured integration instances, separated into distinct sections for Jira and Azure DevOps. Each integration instance row shows the connection name, instance URL, and status, with Edit and Delete action buttons on the right. Multiple instances of each integration type can be configured — for example, if your organisation uses both a cloud and a server Jira deployment.
Jira Integration
Adding a Jira Instance
- In the Jira section, click Add Jira Instance.
- Provide all required details including the Jira base URL, API token, and email address.
- Click Save to create the Jira instance.
The Add Jira Instance pop-up collects all required connection details including the Jira base URL, email address, and API token for the integration account. Use a dedicated service account API token rather than a personal token to ensure the integration remains functional if individual team members leave the organisation. The Jira base URL should be the root URL of your Jira instance — for example, https://yourcompany.atlassian.net for Jira Cloud.
Enter the Jira Cloud or Server URL, the authentication email address associated with the API token, and the API token value to establish the integration. Jira API tokens are generated from the Jira user account settings under Security > API Tokens — ensure the token is not expired before entering it. After filling in all fields, use the Save button to submit the configuration; Data Trust will validate the credentials and confirm the connection status.
Clicking Save in the Add Jira Instance pop-up sends the provided credentials to Jira for validation and then stores the connection configuration if the test passes. If the credentials are invalid or the Jira URL is unreachable, an error message is displayed with guidance on what to correct. A successful save makes this Jira instance immediately available to all Data Trust users who have permission to create or link issues.
A success message confirms the Jira instance has been added and is now available for use throughout Data Trust wherever Jira issue creation or linking is supported. The new instance appears in the Third Party Integrations Jira section with its connection status shown as Active. Test the integration by navigating to a validation or reconciliation result and attempting to create a linked Jira issue from there.
Editing a Jira Instance
- Click the Edit button on the Jira instance row.
Click the Edit button on the Jira instance row to open the configuration pop-up where you can update any changed credentials or connection settings. Use this action when a Jira API token has expired, the Jira base URL has changed, or the authentication email needs to be updated. The Edit pop-up pre-fills all existing values so you only need to update the fields that have changed.
The Edit Jira Instance pop-up is pre-filled with the current URL, email, and API token (masked) — modify only the fields that have changed since the last save. If updating the API token, ensure the new token is copied from Jira before opening this pop-up to avoid errors during the save process. Click Save after making changes; Data Trust will re-validate the credentials and display a success or error message accordingly.
A success toast message confirms that the Jira instance configuration has been updated and the new credentials have been validated. The updated connection is immediately active — Data Trust will use the new credentials for all subsequent Jira operations from this instance. Test the integration after updating to confirm issue creation and linking still work as expected.
Deleting a Jira Instance
- Click the Delete button on the Jira instance row.
Click the Delete button on a Jira instance row to initiate the removal of that integration from Data Trust. A confirmation pop-up will appear before the deletion is finalised — ensure you have identified and communicated the impact to any users who rely on this Jira connection. After deletion, users will no longer be able to create or link Jira issues via this specific integration instance.
The deletion confirmation pop-up shows the Jira instance name and asks you to confirm the action, preventing accidental removal of an active integration. Click Confirm to proceed with the deletion or Cancel to return to the integrations page without making changes. Removing an integration does not delete any issues already created in Jira — it only removes the connection from Data Trust.
A success message confirms the Jira instance has been removed from Data Trust and is no longer available as an integration option. The Jira section on the Third Party Integrations page refreshes to reflect the removal. If the integration needs to be restored, add a new Jira instance using the Add Jira Instance button with the correct credentials.
Azure DevOps Integration
Creating a Personal Access Token in Azure DevOps
- Log in to Azure DevOps and navigate to your user settings to create a Personal Access Token (PAT).
Access the Personal Access Tokens section in your Azure DevOps account settings (User Settings > Personal Access Tokens) to generate a token for use with the Data Trust integration. This step is performed in the Azure DevOps portal, not in Data Trust — have the portal open in a separate browser window while configuring the integration in Data Trust. Create a dedicated PAT for the Data Trust integration rather than reusing one already associated with another tool, to allow independent revocation if needed.
When creating the PAT, provide a descriptive name (such as 'DataTrust-Integration'), set an appropriate expiry date, and define the minimum required scope — typically Work Items (Read & Write) and Code (Read). Restricting the PAT to only the necessary permissions follows the principle of least privilege and reduces the potential impact if the token is ever compromised. Click Create after configuring the PAT settings and copy the generated token value from the next screen immediately.
Copy the generated Personal Access Token value immediately after creation — Azure DevOps will not display the token value again once you navigate away from this screen. Paste the token into a temporary secure location before returning to Data Trust to complete the integration configuration. Store the token in your organisation's secrets management system and share it only with the administrators responsible for the Data Trust integration.
Adding an Azure DevOps Instance to Data Trust
- In the Azure DevOps section of Third Party Integrations, click Add Azure DevOps.
- Provide all required details and click Test Connection.
- After a successful connection test, click Save.
Back in Data Trust, click the Add Azure DevOps button in the Third Party Integrations section to open the configuration pop-up for entering your Azure DevOps organisation URL and the PAT. This button is found in the Azure DevOps section of the Third Party Integrations page, clearly separated from the Jira section above it. Have your Azure DevOps organisation URL and the newly created PAT ready to paste into the configuration form.
The Add Azure DevOps instance pop-up requires three inputs: your Azure DevOps organisation URL (for example, https://dev.azure.com/yourorg), the project name, and the PAT created in the previous step. Enter all three fields accurately — an incorrect organisation URL or project name will cause the Test Connection to fail. Once the form is complete, click Test Connection before saving to verify Data Trust can reach your Azure DevOps instance with the provided credentials.
After entering the Azure DevOps organisation URL, project name, and PAT in the pop-up form, click Test Connection to verify the integration can successfully reach and authenticate with Azure DevOps. A passing test result means Data Trust has confirmed network connectivity and valid credentials for the configured project. If the test fails, check that the organisation URL is correct, the project name matches exactly (including capitalisation), and the PAT has not already expired.
After the Test Connection returns a success result confirming the credentials are valid, click Save to persist the Azure DevOps integration configuration in Data Trust. Saving without a successful test is not recommended — always confirm connectivity first to avoid saving a broken integration. The integration takes effect immediately after saving and is available to all users with permissions to create or link Azure DevOps work items from Data Trust.
A success message confirms the Azure DevOps integration has been saved and is now ready for use across Data Trust wherever Azure DevOps work item creation or linking is supported. The new instance appears in the Azure DevOps section of the Third Party Integrations page with an Active status. Perform a quick end-to-end test by creating a linked work item from a Data Trust result page to confirm the full workflow is operational.
Editing and Deleting an Azure DevOps Instance
Click the Edit button on an Azure DevOps instance row to open the configuration pop-up and update the organisation URL, project name, or PAT when the integration credentials or project have changed. The pop-up pre-fills all current values so you can identify which fields need updating without re-entering unchanged information. After modifying the necessary fields, click Test Connection before saving to ensure the updated configuration is valid.
A success message confirms the updated Azure DevOps configuration has been saved and the new credentials or project settings are now active for the integration. All subsequent Azure DevOps operations initiated from Data Trust will use the updated configuration immediately. If users report issues with Azure DevOps integration after the update, re-verify the PAT scope and project name in the Edit pop-up.
The delete confirmation pop-up appears before the Azure DevOps integration is removed, displaying the instance name for you to confirm the correct entry is being deleted. Proceed with deletion only after confirming that no active Data Trust workflows rely on this Azure DevOps connection for work item operations. Click Confirm to complete the deletion or Cancel to return to the integrations page without making changes.
A success toast confirms the Azure DevOps integration has been permanently removed from Data Trust and is no longer available as a work item connection option. The Azure DevOps section on the Third Party Integrations page refreshes to reflect the removal. If the integration needs to be re-established, use the Add Azure DevOps button with the correct organisation URL, project, and a new PAT.
The Azure DevOps section on the Third Party Integrations page provides a consolidated overview of all currently configured Azure DevOps instances, reflecting their real-time Active or Inactive status. Review this page periodically to identify instances whose PATs may be approaching expiry, and update them proactively to avoid unexpected integration failures. Each instance row provides Edit and Delete actions so you can manage the full lifecycle of your Azure DevOps connections from a single location.