- 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
- Native Azure DevOps Issue Level Integration. Technical Overview
- Native Jira Integration Released
Basic Case 1.0
Portfolio level is tracked in Targetprocess and Teams work in Jira. Every team has its own Jira project for tracking Stories. Features are in a separate Jira project in order to be shared across all teams.
Portfolio Epics > Capabilities > Features > User Stories > Bugs
Features in Targetprocess are assigned to different Teams and Quarter Releases and sync as Jira Epics. Teams split their Epics in Jira to Stories, plan Stories to Sprints.
1. Create integration profile
As an ATP Administrator navigate to Settings > Integrations
- Add new Jira Cloud (or Server, if it is Data Center) integration profile;
- Set up account connection following all instructions in profile including webhooks setup in Jira.
2. Map projects and teams work scopes
Set up routings for required direction sync – from Jira to Targetprocess or from Targetprocess to Jira, or both if you want to all new issues that pass the integration filters to be created in the other tool and start syncing.
3. Types and Fields Mapping
Note: Jira Assignee could be mapped to a particular Assignee Role or drop-down/text Custom Field. When Jira user is synced to ATP custom field it works with email by default.
- Feature <> Jira Epic
- User Story <> Story
- JS mapping ‘Team to Jira Project’
With this mapping Jira project will be mapped to a specified Team in Targetprocess. Add it to second tab of the field mapping - From Jira to Targetprocess. Then map you Jira projects to Targetprocess Teams setting the correct Jira project keys against teams names. More JS mappings could be created by Implementation Team / Technical Support for Integrations.
4. Map Targetprocess Team Iterations to Jira Sprints
Map Team Iterations to Jira Bords – Scrum board from team’s project in Jira, then collections of work items, assigned to shared Team Iteration, will be imported to/from Jira automatically if Targetprocess Team Iterations is synced with the Jira Sprint.
*Team Itearations must be created in ATP and pushed to Jira. It is not possibe to import sprrints from Jira to ATP, you can only get existing Jira Sprint linked to an existing ATP team iteation. ATP team iterations have more strict default logic for setting Start/End Dates, so sprints dates not always could be synced between Jira and ATP.
Still have a question?
We're here to help! Just contact our friendly support team