Native Jira integration could be enabled upon request to product specialist and then set up by implementation team How to view Jira Issue information in Targetprocess 'Synced Work' block Jira links will be shown in the entity detail view
Integration Users are not expected to log into Targetprocess and use it on a regular basis, but they can be displayed as Assigned Users, be part of the Capacity Planning, etc. "Integration User" is part of native issue level integrations
Integration service access security We use OAuth2 for securing our internal APIs, each service call must contain an OAuth token with a special set of scopes requested by the service. Data isolation Native integration use Postgres as underlying
Two-way data synchronization implies that both systems can be inaccessible for different periods of time and data can get out of sync. With the data validation report, you are able to find the items that are not synced
Useful Links for Jira Integration Setup Automation Rules Library JS mappings Library Additional Feature Toggles List Dev Portal: Work Sharing API documentation, how to write JS mappings, comparators and dynamic routings How to validate the data quality How snapshot service work
Native Jira Integration Released Visibility is key in Targetprocess. Portfolio and Product Managers conducting planning on a high level can drill down to get details from an operational level. Targetprocess acts as a central point of truth for
Should you migrate your Jira Server to Cloud or decide to split a profile into two independent profiles for easier management, our migration tool will help with transferring synced data to a new profile. Beta migration support