Forum Discussion
Azure devops - How to map existing jira to azure devops boards
Hi,
We are going to use both Jira and Azure devops to manage multiple projects. however, we are unable to match the jira hierarchy to Azure devops. in jira we use Project -> Release -> Issue Types (Epic -> story,task,supbtask etc)
We would like to know how we can map this hierarchy in Azure devops boards? what are equal entities for Project, Release, and Issue types in Azure devops
To map Jira to Azure DevOps:
Project → Project in Azure DevOps.
Release → Use Iterations/Sprints for Release timelines or Pipelines for deployment milestones.
Hierarchy Mapping:
- Epic in Jira → Epic in Azure DevOps.
- Story → Feature (for larger stories) or User Story.
- Task → Task.
- Subtask → Task (nested under a story).
Summary Hierarchy:
- Project
- Iteration/Release
- Epic
- Feature
- User Story
- Task
- User Story
- Feature
- Epic
- Iteration/Release
Use Area Paths for team organization.
Thank you for your quick reply,
Just wanted to clarify the following.In Jira, once we create a release, we can attach that release to a given work item as a fix version. And thereby, we can go to the release and see all the issues assigned to that particular release.
However, in Azure boards, I do not see any direct way of doing this.
We could create a delivery plan, but that delivery plan cannot be directly assigned to a given work item. But, we can assign sprint (which are under delivery plan) to a work item.In this case, if we want to see all the issues under release (assuming that release = delivery plan), then we have first find out what are the sprints in each delivery plan and view issues under each of these sprints. Is this correct ?
Appreciate your feedback in this.
You are correct in identifying that Azure DevOps doesn’t have a direct equivalent of Jira’s “Fix Version” for associating work items with a specific release that can then be easily filtered. Instead, the concept of a Release in Azure DevOps relies on Iterations/Sprints and Tags or custom fields to group work items.
You can try the below steps to replicate Jira's "Fix Version" in Azure DevOps
Use Iterations: Treat each release as a unique Iteration Path (e.g., "Release 1.0") and assign it to work items. Then filter by this path to view items by release.
Add a Custom Field: Create a "Release" field in work items to select a version, similar to "Fix Version" in Jira.
Create Queries: Use queries to filter work items by the custom "Release" field or specific Iteration Paths for easy viewing.
This setup provides a straightforward way to track items by release in Azure DevOps.
- You can customize an existing process model and bringing in custom item type and to an extend also a custom hierachy level.
