- Native Issue Level Integrations
- Native Jira integration: End User Guide
- Integration user type
- Native Jira Integration: Technical Overview
- Native Jira Integration: Data Validation Report
- Native Jira Integration: Setup Guide
- Azure DevOps Integration: Technical Overview
- Native Jira Integration Released
Pros
Routings
- Targetprocess integrations support flexible dynamic projects routings. It is possible to define the target project dynamically, depending on a field value, or import issues from dependent project if only there is a relation to that project's work item.
Functional power
- Extendable Domain entity types support (Objectives, Risks, etc.)
- Native assignments, efforts mapping support and combination with automation rules
Sync Stability
- Native integration proceeds to sync the entity even if Targetprocess entity/Jira issue was moved to another project, which is not in the integration scope. Tasktop stops syncing issues which are out of predefined sync scope.
- Failed fields do not stop sync of others. Native integration will sync all the fields it can, even when some other fields show an error. Tasktop requires all fields to be fixed before restoring the synchronization.
Administration
- Any Targetprocess Administrator can access Jira integration profiles, check sync logs and modify mappings
Cons
Cases when Tasktop syncs with limitations while Targetprocess refuses to invest into partial support:
Sub-tasks sync is not supported
We suppose that it is unnecessarily detailed level and should remain in Jira.
Team-managed projects are not supported
- Team-managed projects have a separate independent set of custom fields – it would not be possible to map several Team-managed projects in one integration profile
- No webhooks to support epic-link relation type; thus, stories added on epic in JIRA would not sync to Targetprocess parent entity
- Tasktop supports with defined limitations. We decided to not invest greatly into non-target use cases support
Time-based Full Scan
Time-based scan and automatical consolidatiion of conflict and missed issues import is still on the roadmap with no exact planned date.
Fields synchronization frequency
Set field value once on creation, or on every update, or every specific field change – is not supported in Targetprocess.
Native integration syncs all mapped fields every time they change
More granular relations mapping
For example, Jira ‘is blocked by’ could be mapped to ‘Relation’ link type and ‘blocks’ to ‘Dependency’. Native integration will sync both end of one relation type to the same - both to ‘Relation’ or both to ‘Dependency’. (This is on the 2023 roadmap of ATP Native Integrations)
Still have a question?
We're here to help! Just contact our friendly support team