Jira Integration Limitations

Edit online

Limitations

  • Integration with Jira Server or Data Center using self-signed certificates is supported only for private cloud accounts.
  • Sub-tasks are not supported for synchronization. Syncing of low-level details is not enabled. Sub-tasks remain in Jira and do not roll up to the portfolio level in Targetprocess.

    However, users can easily navigate from Targetprocess to the corresponding Jira issue using the External ID link of the shared item.

  • Time tracking:Syncing the recent total time spent or remaining time as a single record in Targetprocess is supported, but further details are not available.
  • QA Area: Support for many-to-many hierarchies in the QA Area is not fully implemented. While it is possible to sync and export the Test Area from Targetprocess to Jira, the many-to-many relationships will not sync correctly in either direction. Due to the high implementation effort and low business value, there are no current plans to address this limitation.
  • Team-managed projects are not supported, and there are no plans to support them in the future. Multiple team-managed projects cannot be mapped within a single profile due to differing custom field sets. Additionally, team-managed project webhooks do not support parent-child relationship synchronization.
  • Batch actions such as Pull from Jira, Push to Jira, and Unlink are not available from the Targetprocess UI. However, only admins can perform batch pull and push for the entire profile. Batch pull and push are also available in the Data Validation report.
  • The Creation Date of Jira issues cannot sync with the Creation Date field of Targetprocess entities.
  • Aggregation fields such as Σ Original Estimate, Σ Progress, Σ Remaining Estimate, and Σ Time Spent are not supported.