As part of connecting and syncing Craft.io Workspaces with Azure DevOps projects, users need to configure the mapping of work items between the tools. The configuration is dependent on the four Azure DevOps default processes, which include different item types. This article outlines the different options for item types mapping.
Table of contents:
Understanding Craft.io item types
Each Craft.io Workspace contains Products, which are containers or groups of work items. In most cases, it represents a certain component, a Product team, or a large aspect of your customer-facing proposition. In each of the Products you will find the following default structure:
Term | Definition |
Epic | Work items that allow you to cluster and organize groups of Features, and have a set of properties that are assigned to them (such as Status, Start date / End date, etc.). |
Feature | Work items that represent a specific user need or a product capability you plan to build. Also have a set of properties that are assigned to them (such as Status, Start date / End date, etc.). |
Story | Work items that can be used to further break down Features into smaller tasks and to-dos. |
Craft allows you to create additional work items, at the Feature level, such as Bugs, Tasks, and Requirements.
Working with Azure DevOps Default Processes
First, you will need to identify which process you are using in your Azure DevOps instance. There are four default processes: Basic, CMMI, Agile, and Scrum. You can read more about it here.
Based on your process method, here are the available mapping options in Craft.io:
Basic
With the Azure DevOps Basic process, the mapping is not customizable. The three main levels in Craft.io map to the three main levels in Azure DevOps.
Craft.io | Azure DevOps |
Epic | Epic |
Feature | Issue |
Story | Task |
Agile
When working with the Azure DevOps Agile process, you have more flexibility with the items mapping:
Decide if you wish to map the Craft.io Product entity to Azure DevOps
Depending on your choice above, decide if you wish to map additional item types
Option 1 - Map Craft.io's Product to Azure DevOps
Craft.io | Azure DevOps |
Product | Epic |
Epic | Feature |
Feature | User Story |
Story | Task |
Bug | Bug |
Task | Issue |
Requirement | Issue |
Option 2 - Do not map Craft.io's Product to Azure DevOps
Craft.io | Azure DevOps |
Product | IGNORE |
Epic | Epic |
Feature | Feature |
Story | User Story |
Bug | - |
Task | - |
Requirement | - |
Scrum
With the Azure DevOps Scrum process, the mapping options are similar to Agile, with the difference in the work item types on the ADO side.
Option 1 - Map Craft.io's Product to Azure DevOps
Craft.io | Azure DevOps |
Product | Epic |
Epic | Feature |
Feature | Product Backlog Item |
Story | Task |
Bug | Bug |
Task | Impediment |
Requirement | Impediment |
Option 2 - Do not map Craft.io's Product to Azure DevOps
Craft.io | Azure DevOps |
Product | IGNORE |
Epic | Epic |
Feature | Feature |
Story | Product Backlog Item |
Bug | - |
Task | - |
Requirement | - |
CMMI
Lastly, the mapping between Craft.io and Azure DevOps CMMI acts similarly to Agile and Scrum.
Option 1 - Map Craft.io's Product to Azure DevOps
Craft.io | Azure DevOps |
Product | Epic |
Epic | Feature |
Feature | Requirement |
Story | Task |
Bug | Bug |
Task | Issue |
Requirement | Issue |
Option 2 - Do not map Craft.io's Product to Azure DevOps
Craft.io | Azure DevOps |
Product | IGNORE |
Epic | Epic |
Feature | Feature |
Story | Requirement |
Bug | - |
Task | - |
Requirement | - |
How do I decide which mapping option to choose?
If you're working with Azure DevOps Agile/Scrum/CMMI, ask yourself which of these sentences fits best to your use case:
I need to map Bugs, Issues, and Impediments from ADO to Craft.io, and I can "lose' the Epic item in ADO, using the Feature as the highest item in the hierarchy.
My ADO Epic is a work item and I wish to map it to the Craft.io Work item, and not use it as a Product title for the other items. In addition, I don't need to map other items from ADO, like Bugs, Issues, or Impediments.
If you answered 1 -> Choose mapping option 1.
If you answered 2 -> Choose mapping option 2.
For additional assistance, please contact your dedicated Customer Success Manager (for Enterprise customers) or send a query to support@craft.io.