Events
Mar 17, 9 PM - Mar 21, 10 AM
Join the meetup series to build scalable AI solutions based on real-world use cases with fellow developers and experts.
Register nowAbout migrating and integrating work tracking data
Azure DevOps Services | Azure DevOps Server 2022 - Azure DevOps Server 2019
There are various tools available to help you migrate your work tracking data to the Azure DevOps platform. This article provides an overview of these tools and links to resources that support the migration of work tracking data and processes. You can also integrate Azure Boards with numerous non-Microsoft tools and extensions.
Note
With Azure DevOps Marketplace extensions for Azure Boards, you can customize and enhance the default experience. For more information, see the list of recommended extensions for Azure Boards, further in this article.
The Data Migration Tool for Azure DevOps provides a high fidelity way to migrate collection databases from Azure DevOps Server to Azure DevOps Services. For more information, see Migrate data from Azure DevOps Server to Azure DevOps Services.
You can search for extensions in the Visual Studio Marketplace that allow you to bulk edit and migrate data between project on both on-premises and the cloud. Such tools generally support the following tasks:
- Migrate work items from one project to another project and synchronize changes after a migration
- Merge many projects into a single project
- Split one project into many projects
- Assist changing process templates
- Edit work items in bulk
- Migrate test suites and test plans
For constraints on process template definitions that you can import, see Resolve validation errors for process import.
The main tool you can use to import work tracking data you exported from elsewhere is Microsoft Excel. Excel supports publishing a flat list of work items or a hierarchical tree of parent-child linked work items. For more information, see Bulk add or modify work items with Excel.
Azure Boards (cloud) and Azure DevOps Server integrate with GitHub. Connect Azure Boards with GitHub repositories to link between GitHub commits, pull requests, and issues to work items. You can use GitHub for software development while using Azure Boards to plan and track your work.
For more information, see Connect Azure Boards to GitHub.
You can integrate Azure Boards with other non-Microsoft tools such as Jenkins and Trello. Using service hooks you can generate actions based on Azure DevOps events. For more information, see the following articles:
- Create a service hook for Azure DevOps with Jenkins
- Create a service hook for Azure DevOps with Trello
- Integrate with service hooks
The following table contains some Microsoft extensions. You can search for other non-Microsoft extensions in the Visual Studio Marketplace.
| Category | Extensions |
|---|---|
| Automation | Power Automate, Azure DevOps |
| Command-line interface | Azure DevOps CLI |
| Customizing work item types | - Cascading Lists - Color picklist control - Multi-value control - Work Item Visualization - WSJF (Weighted Shortest Job First) |
| Dashboard widgets | - Azure Application Insights widget - Work Item Details widget - Roll-up Board widget |
| Product planning | - Azure DevOps Open in Excel - Epic Roadmap extension, Feature Timeline (Deprecated) - Feature Timeline extension, Feature Timeline (Deprecated) - Retrospectives - Split! - Team Calendar - Reactivations Report |
| Querying and reporting | WIQL to OData |
Additional resources
Training
Learning path
Continuous integration with Azure DevOps for Microsoft Dynamics 365 Business Central - Training
What tools are used by many Business Central developers to manage the creation of apps? This path discusses Azure DevOps, Git, Visual Studio Code, and other tools you can use to manage the development process.
Certification
Microsoft Certified: DevOps Engineer Expert - Certifications
This certification measures your ability to accomplish the following technical tasks: Design and implement processes and communications, design and implement a source control strategy, design and implement build and release pipelines, develop a security and compliance plan, and implement an instrumentation strategy.