How To Copy Tasks In Azure DevOps

Learning how to efficiently copy tasks—whether it’s a single bug fix or a massive hierarchical epic—is a fundamental skill for any DevOps professional or Project Manager looking to scale their operations. In this article, I’m going to walk you through every method for duplicating work items, keeping your backlogs clean and your productivity high.

How To Copy Tasks In Azure DevOps

Method 1: The “Copy Work Item” Feature (The Quick Fix)

The most straightforward way to duplicate a task is the native “Copy Work Item” function.

Step-by-Step Execution

1. Navigate to your Backlog or Board: Find the specific task (or “Work Item”) you want to duplicate.
2. Open the Task: Click on the Title to open the full view.
3. The Actions Menu: In the upper right-hand corner, look for the three dots (…).
4. Select “Copy work item”: A dialog box will appear.
5. Choose Your Destination: You can copy the task into the same project or a completely different project within your organization.
6. Toggle Links: You’ll see a checkbox labeled “Include existing links.” If you want the new task to be connected to the same Parent or Related items, keep this checked.

Check out the screenshot below for your reference.

Key Considerations for Copying

Method 2: Creating a Task from a Template

If you find yourself copying the same type of task every Monday morning, stop using the copy button. You need Work Item Templates. I use these for recurring maintenance tasks, like “Monthly Server Patching” or “Quarterly Compliance Review.”

How to Build a Blueprint

To create a template, fill out a task exactly how you want it to look. Before saving, click the three dots (…) and select Templates > Capture. Name it something recognizable, like “Backend Feature Template.”

Applying the Template

When you create a new, blank task, simply go to the actions menu, select Templates, and choose your saved version. Azure DevOps will instantly populate all the fields—priority, area path, and tags—saving you minutes of manual entry.

Method 3: Bulk Copying with “Copy as HTML” or Excel

Sometimes copying one task isn’t enough. Perhaps you’re migrating ten tasks from a “Discovery” phase to an “Execution” phase.

Using the Bulk Edit Feature

1. Go to your Queries or Backlog.
2. Hold down the Ctrl key (or Cmd on Mac) and select multiple tasks.
3. Right-click on the highlighted area.
4. You can select Change Type or Move to Project, but for a true “copy,” most pros prefer the Excel Integration.

The Excel Power Move

For my fellow data enthusiasts, the Azure DevOps Office Integration is a lifesaver. By opening a query in Excel, you can simply copy rows of data and “Publish” them back to DevOps. This creates entirely new work item IDs while maintaining all the metadata you just pasted.

Method 4: Copying Hierarchies (Epics and Features)

Copying a single task is easy, but what if you have an Epic with five Features, and each Feature has ten Tasks? Manually copying those 51 items would be a nightmare.

For this, I recommend the “Clone” functionality available through various Azure DevOps Marketplace extensions, or by using the “Create Copy” feature at the Epic level.

Pro Tip: When you copy a parent item, pay close attention to the “Link to original” setting. If you don’t uncheck this, your new “Copy” will still be linked to the old parent, which can cause massive confusion during sprint reporting.

Method 5: Using the Azure CLI for Automation

As a technical trainer, I always encourage people to look toward automation. If your workflow involves copying tasks as part of a CI/CD trigger, the UI is your enemy. Use the Azure CLI.

You can use the az boards work-item create command combined with az boards work-item show to pull data from an existing task and inject it into a new one. This is how high-performing teams “copy” tasks automatically when a build fails or a specific gate is passed.

Common Pitfalls to Avoid

1. The “Ghost Link” Problem

When you copy a task and include links, you might accidentally link your new “Sprint 2” task to a “Sprint 1” User Story. Always audit your Links tab immediately after copying to ensure the parent-child relationship is accurate for the current milestone.

2. Forgetting the “Area Path”

If you copy a task from Project A to Project B, Azure DevOps will try to match the Area Path. If Project B doesn’t have a matching folder structure, it defaults to the root. This results in “lost” tasks that don’t show up on your team’s specific board.

3. State Reset

Most copied tasks will default back to “New” or “To Do.” If you were copying a task that was “In Progress” because you wanted to split the work, remember that you’ll need to manually move the state forward.

Best Practices

When copying tasks:

• Rename Immediately: Never leave a task titled “Copy of [Original Task].” It looks unprofessional and confuses stakeholders. Add a prefix like “[Phase 2]” or “[Refactored].”
• Tagging: Use tags like Duplicated or Template-Derived if you need to track the origin of the work for auditing purposes.
• Clean the Description: Often, the original task has comments or specific “Notes to Dev” that no longer apply. Scrub these before assigning the new task to a team member.

Summary of Methods

Frequently Asked Questions

Can I copy a task to a different Organization?

Not directly through the UI. You would need to export the tasks to a CSV or use a third-party migration tool like the “Azure DevOps Migration Tools” available on GitHub.

Do comments get copied over?

No. Comments are considered historical data tied to the specific instance of a work item. A copied task is treated as a “New” entity.

Does copying a task notify the person it’s assigned to?

If the “Assigned To” field is populated during the copy process, the user will receive a notification based on their personal alert settings.

Final Thoughts

Mastering the art of copying tasks in Azure DevOps is about architecting a repeatable, scalable process. By utilizing templates for your common work and using the bulk edit tools for larger migrations, you free up your brainpower for what really matters: solving complex problems and delivering value to your users.

You may also like the following articles:

• How To Add Feature To Epic In Azure DevOps
• Azure DevOps CI CD Pipeline Step By Step
• Azure DevOps Tutorial For Beginners
• How To Use Azure Devops For Project Management

Rajkishore

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.