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 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
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
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
Limitations Integrations with self-signed certificates authorization to Jira Server or Data Center could be supported for private cloud account only. Sub-tasks are not supported. We do not plan to add the ability to sync low level details. Sub-tasks
Jira can migrate from Server to Cloud in several different ways: XML backup of Jira and restoring it in Cloud - Preferred option as integration migration will be the easiest in this case. JCMA - Jira Cloud Migration
Currently Targetprocess integration with Jira is based on webhooks, change notification mechanism. As the data flows across the systems, usually over the public network, security is a crucial aspect. The webhooks sent from Jira are plain http calls