Jira Integration Limitations

Edit online

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 remain in Jira and do not roll up to portfolio level. User can navigate easily from Targetprocess to Jira by ‘External ID’ link of the shared issue.
  • Time tracking: we support sync of recent total time spent/remaining as a single record in Targetprocess. Detailization is not available in Targetprocess
  • QA Area many-to-many hierarchy support is not completed. You can sync and export Test Area from Targetprocess to Jira, but many-to-many hierarchy will not be synced correctly both ways. Excess effort to fix VS low business value.
  • Team-managed Projects are not supported and there are no future plans to support them.
    • Multiple Team-managed Projects cannot be mapped in a single profile due to different/separate custom fields sets.
    • Team-managed Project webhooks do not support parent-child relations synchronization.
  • Cross-profile relations are not yet supported but Beta version is available upon request. Email to Product Manager nadia.bulynia@ibm.com to try new functionality first.
  • Batch actions “Pull from Jira”, “Push to Jira”, and “Unlink” are not available from Targetprocess UI. Batch pull and push for the whole profile is supported in profile settings available for Admins only. Also, batch pull and push is supported in “Data validation report”.
  • Create Date” of Jira issues cannot sync as “Creation date” field of Targetprocess entities.