Azure DevOps Dashboard Migration

Azure DevOps Dashboard Migration

Project teams spend most of their time communicating. Good dashboards and queries are essential to easy, clear, concise, and accurate communication.

This extension helps you migrate dashboards and their underlying queries across Azure DevOps projects so you can resuse your own and others best practices across all your projects.

Prerequisites:

1. PAT of Source Project
2. PAT of Target Project

Source PAT with read access and scope to work items, Team Dashboard, Token, Project & Team would suffice.

Target PAT with read, write and manage access and scope to work items, Team Dashboard, Token , Project & Team of a Project Collection Admin would suffice and below screenshot shows how to create a PAT

For more details on PAT, please click on this link

Usage:

Go to Overview in the left pane of Azure DevOps project where the extension is shared and installed then click on Dashboard Migrator as shown in below.

Following fields would be listed in the Azure DevOps Dashboard Migration extension page.

Enter the source information to Fetch Dashboards from source project.

Enter the target information to Migrate Dashboards to target project.

Parameters:

1. Source PAT: Can make use of PAT created by following steps provided above.
2. Source Org: Source Organization name will be auto-populated in the Organization where the Extension is used.
3. Source Project: Project name will be auto-populated with the details where the extension is used.
4. Dashboard Type: Select the type of Dashboard, it can be Project Dashboards or Team Dashboards, or both Project & Team Dashboards. In case of Azure DevOps Server, Dashboard type will be pre-selected to Team Dashboards.
5. Fetch Dashboards: On clicking this button , the extension will populate all the Dashboards available in the box under Source Dashboards.
6. Source Dashboards: This section will display the Dashboards from Source Project as per user's selection of Dashboard Type. It will provide a checkbox against each Dashboard, so the user can check the necessary Dashboards to Migrate.
7. Target PAT: Can make use of PAT created by following steps provided above.
8. Target Org: Manually enter the Target Organization.
9. Target Project: Manually enter the Target Project.
10. Migrate Dashboards: On clicking this button , the extension will Migrate all the Dashboards selected by the user to the Target Project.
11. Target Dashboards: This section will display migration status of each Dashboard.
12. View Logs: View log will provide a detailed Log of the migration. This helps to identify the Status of migration of underlying entities like Area paths, Iteration paths, Queries.

Note:

The extension does not support migrations from Azure DevOps Server to Azure DevOps Service or vice versa.

As part of Dashboard Migration Extension, we collect the following usage telemetry to track and improve our services.

1. Azure DevOps Service/Server name and Team Project name that is using the extension.
2. Migrated Dashboard and Query name.
3. Exceptions logged while usage for troubleshooting purpose.

We do not collect any user and workitem related details.

FAQ

1. Why AreaPath and Iterations do not get mapped after migration?

   We have observed that , it might happen in few cases. Once such case is when we migrate a dashboard that has a background query having Areapath as @teamareas or IterationPath as @currentIteration. In such cases, we would recommend user to to manually update the Team settings for the newly created Team by mapping Areapath & Iterationpath.

Support:

Please raise a your concern in Q & A Section. We will try our best to respond at the earliest.