Native Issue Level Integrations

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

There is no excerpt because this is a protected post.

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

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

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

Azure DevOps Work Items integration is released publicly and can be enabled for any account upon request to a Customer Care and Account Manager as integration depends on connected users licensing and integration implementation paid services. Useful Links

How to write WIQL filters for Azure DevOps Integration For easier writing of Azure DevOps WIQL filters use extension: https://marketplace.visualstudio.com/items?itemName=ottostreifel.wiql-editor Batch update of multiple selected issues using Import Import creates new entities if they are not yet in sync

Area Path in Microsoft Azure DevOps supports teamwork and group work items based on a product or business unit. In Azure DevOps, you can even create a tree-hierarchy of area paths to organize teams into hierarchy. The current

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

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

Sometimes it is impossible to map several teams in one integration profile because of very different workflows. If Features of Engineering team have drastically different set of fields and validation rules and automations than Features of Accounting or Marketing

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