TFS4JIRA | Template to start synchronizing
Instructions
This is an example of a migration template with two mapping schemes:
Basic Settings
Mapping:1
Types
Status / State
Fields
Mapping:2
Types
Status / State
Fields
Filters
This template is a guide to document an example of migration process using TFS4JIRA app.
1. Basic Settings
Profile’s general configuration and synchronization mode.
Sync. profile | Profile Status | Jira Project | TFS/ADO Project | Current sync. | Direction | Mapping | Jira cf for TFS/ADO ID | TFS/ADO cf for Jira Key | Filters |
Profile I | Enabled | Project A | Project D | Continuous Sync | JiraToAzure | 1 | TFS ID (Custom field) | JIRA ID (Custom field) | Yes |
Profile II | Disabled | Project B | Project E | Initial Sync | AzureToJira | 2 | TFS ID (Custom field) | JIRA ID (Custom field) | No |
Profile III | Enabled | Project C | Project F | Continuous Sync | Both Directions | 1 | TFS ID (Custom field) | JIRA ID (Custom field) | Yes |
a. Mapping: 1
i. Types: Issue types, work item types, and how they should map.
Jira | TFS/ADO |
Bug | Bug |
Story | User Story |
Epic | Epic |
|
|
ii. Status / State: Jira Status, Azure State, and how they should map. Note that each workitem type/ Issue type can have its own workflow with different statuses; this is important to consider when configuring the state/status mapping section.
Jira | TFS/ADO |
Open | Open (Default) Active |
In Progress | In Progress (Default) Development |
Closed | Closed (Default) Removed |
|
|
iii. Fields: Jira Fields, Azure Fields, and how they should map.
Jira | TFS/ADO |
Assignee | Assigned To |
Reporter | Created By |
Priority* | Priority* |
Environment | System Info |
Sprint* | Iteration Path* |
Repro Steps (Custom Field)* | Repro Steps* |
Created Date (Custom field)* | Created Date* |
Description | Description |
Components* | Area Path* |
Labels | Tag |
|
|
b. Mapping: 2
i. Types: Issue types, work item types, and how they should map.
Jira | TFS/ADO |
Epic | Feature |
Issue (Custom IssueType) | Issue |
Task | Task |
|
|
ii. Status / State: Jira Status, Azure State, and how they should map.
Jira | TFS/ADO |
To Do | To Do |
In Progress | Doing |
Resolved | Resolved |
|
|
iii. Fields: Jira Fields, Azure Fields, and how they should map.
Jira | TFS/ADO |
Assignee | Assigned To |
Reporter | Created By |
Priority* | Priority* |
Environment | System Info |
Sprint* | Iteration Path* |
Repro Steps (Custom Field)* | Repro Steps* |
Created Date (Custom field)* | Created Date* |
Description | Description |
Components* | Area Path* |
Labels | Tag |
|
|
iv. Filters:
JQL filters/ WIQL filters.
Profile | JQL Filters | WIQL Filters |
I | Custom field = value AND created >= -30w | - |
III | issuekey in (ABC-1, ABC-2, ABC-3) AND Assignee = currentUser() | [System.Description] CONTAINS WORDS ‘test'-- |
Related articles