These functional changes could be enabled or disabled via feature toggles in the account configuration by Targetprocess Support, Product Specialist or Product Managers
- Required always. Enables native integrations services (work sharing) AND Jira integration
- In addition to (1) enables Azure DevOps integration. Q2-2022 udpate: ADO integration is luanched silently and works in production for 2 clients only. It's not ready for scaling in prod due to limited dev/support capacity comparing to effort/capacity required for making integration ready for public access and prod implementations scale. Some functionality important for GA is missing and it's implementation is roughly planned for Q3-2022 and late autumn release.
- In complex with (1) enables TP integration
- Disable initial comment in Jira/ADO item with the link to TP entity (must be disabled, when notifications to a new comment is widely used in ADO/Jira/TP and a massive import to a tool is planned). Suggest to replace the comment with the fields mapping ID > TP Link if a redirection from Jira is required:
- Enable option of full profile resync to/from Jira/ADO/TP. Must be used carefully as it resyncs all the fields for all entities, it could bring a data loss or become a time-lagged heavy-performance operation. Advise to use it in the beginning of account implementation only
- Disables default sync of delete operation in case you want to keep items that were deleted in the other system.
- Hide comments utility header ‘Created by Targetprocess user %date% %time%”
- Enables experimental multiple sharing for TP and Jira Integrations.
- Batch Push from list or board to multiple profiles is not supported;
- Not supported for Azure DevOps beta
- Disables default convert support. Current implementation supposes Create+Delete operations, not exactly convert.
Example: if Jira issue was converted, its old copy in Targetprocess will be deleted and new one will be created matching the new Jira issue type.
Vice versa, when Targetprocess entity is converted, then the old issue will be removed in Jira and the new one will be pushed to Jira and linked to the result of convert
- Enables beta version of Data Validation Report:
As of Jan, 15 report can compare field values excluding collections and JS mappings without comparators. Comaprators must be added to every JS field mapping by implementation team engineer.
- Enables sync report popup functionality on UI
- Temporary feature toggle before public release
- Enable oAuth2.0 Client Credentials for Jira Server. It enables oAuth2.0 authentication at a customer's gateway, then gateway authorizes integration to Jira using Basic Auth. This is not oAuth2.0 to Jira, as some Jira Rest APIs still do not support parent linking and Boards/Sprints management.