The relationship between an Epic and a Feature is the backbone of strategic alignment. Today, I’m going to walk you through the process of adding a Feature to an Epic in Azure DevOps, ensuring your project hierarchy is as clean as a fresh Slack workspace.
Table of Contents
- How To Add Feature To Epic In Azure DevOps
- Video Tutorial
How To Add Feature To Epic In Azure DevOps
By adding a Feature to an Epic, you are “parenting” the work. This allows the Epic to aggregate the progress of all its underlying Features, giving leadership a real-time view of completion percentages.
Method 1: Using the Mapping Pane
- Sign in to your Azure DevOps organization (e.g.,
dev.azure.com/YourOrg). - Select your Project from the dashboard.
- On the left-hand sidebar, navigate to Boards > Backlogs. Check out the screenshot below for your reference.
Ensuring the Correct View
By default, your backlog might be showing “Stories” or “Tasks.” To work with Epics and Features, you must adjust your view:
- In the upper right-hand corner of the Backlog screen, look for the Backlog level selector.
- Select Features. This will display all the high-level initiatives currently in your roadmap.
Step 2: Enabling the Mapping Pane (The “Pro” Way)
If you have an existing Epic and you want to add a Feature to it, the most efficient way—and the one I recommend —is using the Mapping Pane.
- While in the Backlogs view, click on the View Options (gear icon or toggle) in the top right.
- Turn the Mapping toggle to On.
- A pane will appear on the right side of your screen showing your Epics. Check out the screenshot below for your reference.
4. Now, using your left mouse click, drag the respective feature from the main backlog list and drop it onto the target epic in the mapping pane.
Why Mapping Matters
The Mapping Pane allows for a simple drag-and-drop interface. If you have a list of “Unparented Features,” you can simply grab them and slide them onto the appropriate Epic. Azure DevOps automatically creates the “Parent” link for you behind the scenes.
Method 2: Adding a Feature Directly from the Epic
Sometimes you are starting fresh. You have an Epic, and you want to brainstorm the Features that will make it a reality.
- In the Epics Backlog, you will see a plus (+) icon next to each Epic title.
- Click the + icon. A dropdown or a new work item row will appear.
- Select Feature as the work item type.
- Enter the title (e.g.,
Feature: Cloud Migration - Phase 1). - Press Enter. Check out the screenshot below for your reference.
This Feature is now officially a “child” of that Epic. You can click the small arrow next to the Epic to expand it and see your newly created Feature nested neatly underneath.
Method 3: Linking an Existing Feature to an Epic
In a fast-paced development environment—say, a startup in Seattle—teams often create Features in a vacuum. Later, the leadership team realizes these Features belong under a specific strategic Epic.
The “Parent Link” Method
If the Feature already exists:
- Open the Feature work item.
- Locate the Related Work section (usually on the right side or at the bottom depending on your layout).
- Click Add link > Existing item.
- Change the Link type to Parent.
- Search for the Epic ID or title in the search box.
- Click OK and then Save & Close.
Organizing Features for Multi-Team Projects
In large US corporations, you might have an Epic that spans multiple teams. For example, a “Global Expansion” Epic might involve the “US-East Team” and the “US-West Team.”
Using Area Paths and Iteration Paths
When adding a Feature to an Epic, don’t forget to set the Area Path.
- Epic Area Path: Usually set to a high-level Business Unit.
- Feature Area Path: Set to the specific team responsible for delivering that feature.
This allows the Epic to stay on the “Executive Board” while the Feature shows up on the “Team Board.”
Best Practices for Feature Management
Maintaining a clean hierarchy is a discipline, not a one-time task. Here are the standards I enforce during my DevOps audits:
1. The “Single Parent” Rule
A Feature can only have one Parent Epic. If you find a Feature that seems to belong to two Epics, your Epics are likely defined too narrowly.
2. Naming Conventions
I always advise teams to use prefixes. It makes searching much faster:
- Epic:
[EPIC] 2026 Mobile Refresh - Feature:
[FEAT] Apple Pay Integration
3. Keep the “Leaf Nodes” Balanced
Don’t have one Epic with 50 Features and another with only one. If an Epic is too large, it becomes a “Black Hole” where work goes to disappear. Aim for 5–10 Features per Epic for optimal visibility.
Comparison: Adding via Backlog vs. Board
| Feature | Backlog View | Board View |
| Speed | High (Bulk adding) | Medium |
| Visibility | Hierarchy List | Status Columns |
| Ease of Use | Best for Planning | Best for Daily Standups |
| Mapping Pane | Available | Not Available |
Video Tutorial
Conclusion:
Adding a Feature to an Epic in Azure DevOps is a simple mechanical act that carries profound organizational weight. It turns a list of tasks into a cohesive strategy. By following the steps outlined above, you can easily achieve this.
You may also like the following articles:
- Azure DevOps Tutorial For Beginners
- How To Use Azure Devops For Project Management
- Epic Vs Feature Azure DevOps
- Kanban Board Azure DevOps
I am Rajkishore, and I am a Microsoft Certified IT Consultant. I have over 14 years of experience in Microsoft Azure and AWS, with good experience in Azure Functions, Storage, Virtual Machines, Logic Apps, PowerShell Commands, CLI Commands, Machine Learning, AI, Azure Cognitive Services, DevOps, etc. Not only that, I do have good real-time experience in designing and developing cloud-native data integrations on Azure or AWS, etc. I hope you will learn from these practical Azure tutorials. Read more.
