- Native Issue Level Integrations
- Native Jira Integration: Technical Overview
- Native Jira Integration: Data Validation Report
- Native Jira Integration: Setup Guide
- Native Azure DevOps Issue Level Integration. Technical Overview
- Migration of synced data to a new profile and profile splits (BETA)
- Native Azure DevOps Integration: Setup Guide
- Native Integrations Tips & Tricks
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 projects or project portfolio. With native Jira Integration, engineering teams can use Jira and Program Managers, Release Train Engineers and Engineering Leads are able to visualize incoming data from execution level in Apptio Targetprocess. This traceability encourages accountability and transparency across teams and departments.
Let’s see several examples of different complexity.
Case 1. Basic use case
Portfolio of Epics and Features are tracked in Targetprocess portfolio project and planned into Program Increments. Teams plan each increment, split features to stories and plan them into team iterations. Some teams work in Jira, where teams have their own separate scrum projects.
When a new PI is created in Targetprocess and Team Sprints are generated, sprints can be pushed to Jira to correspondent teams’ projects.
When Features are assigned to Teams and PIs, they can also sync to Jira as Jira Epics for further planning into iterations. Integration could be configured to push Targetprocess Features into common portfolio project in Jira or if each team uses its own project – to a Jira team’s project Epic.
See an example of mapping here.
Case 2. Portfolio Epics shared with multiple teams across different Jira instances
A single strategic theme, portfolio epic or feature is implemented by different teams in collaboration across different business units. For such cases, Jira integration supports multiple sharing of one entity with several integration profiles (not within one profile!)
Case 3. Dynamic routings and automatic detection of Jira project and issue type based on a set of criteria
In some businesses, Portfolio Epic means a new project in Jira every time. In this case, Targetprocess Portfolio Epic is linked to a Jira Project and all mapped work hierarchy syncs from the Jira project to Targetprocess project and links to a specific Portfolio Epic.
Jira Integration Technical Overview
This article describes architecture, security and encryption, supported authentication methods and Jira API endpoints that must be accessible for Targetprocess.
Connected Users and Licensing
In case integration synchronizes Assignments and User fields, then integration service can create a new connected user from Jira Assignee. Integration users are not allowed to log into Targetprocess. More details about integration user type is in this guide.
Read this about connected users licensing
Full Setup Guide For Implementation Teams
This guide is for implementation specialists, describes specifics of integration and advises on how to set it up.
Data Quality And Validation report
This guide describes how to validate the integration quality, analyze the conflict, and fix data mismatches.
End User Guide
This guide describes integration for non-admin end users, simple maintenance and administering actions for admins from the customer side.
- 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.
- 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 nor planned.
- 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 be synced into “Creation date” field of Targetprocess entities.
Roadmap for 2023
- Migration support from Jira Server to Jira Cloud
- Notifications integration for integration admins
- Automatic time-based validation of synced data and automatic conflicts resolution