About dashboards, charts, reports, & widgets

Azure DevOps Services | Azure DevOps Server 2022 - Azure DevOps Server 2019 | TFS 2018

Gain visibility into your team's progress by adding one or more widgets or charts to your dashboard. Customizable, highly configurable dashboards provide you and your teams with the flexibility to share information, monitor progress and trends, and improve your workflow processes. Each team can tailor their dashboards to share information and monitor their progress.

If you're just starting out, read Add, rename, and delete dashboards. Looking for instructions on a specific task, in context chart, widget, or report? See Dashboards and widgets quick reference. For more information, see the Reporting roadmap.

Important

Select a version from Azure DevOps Content Version selector.

Select the version of this article that corresponds to your platform and version. The version selector is above the table of contents. Look up your Azure DevOps platform and version.

Supported capabilities, permissions, and access

Access to Azure DevOps web portal features are managed through access levels assigned to users.

Web portal data views and reports

The following features provide support for viewing Azure DevOps data through the web portal:

  • Dashboards are customizable interactive signboards that provide real-time information. Dashboards are associated with a team or a project and display configurable charts and widgets.
  • Charts are query-based status or trend charts derived from a work item query or test results.
  • Widgets display configurable information and charts on dashboards. The widget catalog provides brief descriptions of those widgets available to you. Also, you can add widgets provided through the Azure DevOps Marketplace.
  • In-context reports are system-generated charts that support specific services. Examples are team velocity, sprint burndown, and the Cumulative Flow Diagram (CFD), and the Test Failures Report. These reports are displayed on the Analytics tab for a specific service and derive data from Analytics.

Power BI reports

The following features provide support for viewing Azure DevOps data using Power BI:

  • Analytics views provide a simplified way to specify the filter criteria for a Power BI report based on Analytics data for Azure Boards data. For more information, see What are Analytics views?.

  • Power BI reports allow users to create rich, customized Power BI reports or other reports using OData queries of Analytics data and the returned JSON data. For on-premises Azure DevOps environments, project collections must be configured to support the Inherited process.

    Note

    OData (Open Data Protocol) is an ISO/IEC approved, OASIS standard that defines a set of best practices for building and consuming REST APIs. For more information, see OData documentation.

SQL Server reports

SQL Server Reporting is the legacy reporting solution available with Azure DevOps Server 2020 and earlier versions. The following features provide support for viewing Azure DevOps data using SQL Server Reports and SQL Server Analysis Services.

  • Excel status and trend reports supports generating custom work tracking reports using Excel starting with a flat-list query. For more information, see Create status and trend reports from a work item query.
  • SQL Server reports: For project collections that support the On-premises XML process model, allow users access to out-of-the-box SQL Server reports and support to create customized SQL Reports or Excel reports. Doing so requires that the project is configured to support SQL Server reporting.

Supported features for access levels

Users with Stakeholder access get restricted privileges, granting them access to only those features outlined in the following table. For more information, see About access levels. In addition to access levels, certain features require permissions to execute.

Note

Data displayed within a chart or widget is subject to permissions granted to the signed in user. For more information, see FAQs on Azure DevOps dashboards, charts, and reports, Access and permissions.

Supported features and tasks

Stakeholder

Basic


Dashboards (View)

✔️

✔️

Dashboards (Create and edit)

✔️

Charts, Widgets (View)

✔️

✔️

Charts, Widgets (Add and configure)

✔️

In-context reports

✔️

✔️

Analytic views

✔️

Power BI reports

✔️

✔️

SQL Server reports

✔️

✔️

Default permissions

Dashboards

Set individual dashboard permissions to grant or restrict the ability to edit or delete dashboards.

Set dashboard permissions at the team level for team dashboards.


Task

Readers

Contributors

Team admins

Project admins


View team and project dashboards

✔️

✔️

✔️

✔️


View team dashboards

✔️

✔️

✔️


Add and configure project dashboards

✔️

✔️


Add and configure team dashboards

✔️

✔️

✔️

Power BI Integration and Analytics views

You set permissions for the service at the project level, and for shared Analytics views at the object level.

Task

Readers

Contributors

Project admins

View Analytics

✔️

✔️

✔️

View a shared Analytics view

✔️

✔️

Add a private or shared Analytics view

✔️

✔️

Edit and delete shared Analytics views

✔️

Configurable dashboards

With dashboards, you can configure an array of charts and widgets.

Each team can add and configure multiple dashboards to:

  • Share information.
  • View status, progress, and trends
  • Access quick links and other functions.

Easily add and rearrange widgets on the dashboard to show recent changes made to view build status, bug trends, and more.

Screenshot of Example dashboard.

Sequence for adding and customizing a dashboard

Select one of the following boxes to open the corresponding article.

Tile link to Add dashboard article.Tile link to Add widget article.

With flat-list queries, you can create various charts to monitor status, progress, and trends. Before you monitor work progress and trends, plan your project and make progress on work you're tracking.

You can open a shared query, create a chart, and add it to the dashboard. Once added to the dashboard, you can change the Chart for work items widget configuration to resize or change the chart parameters. Or, from the dashboard, you can add a Chart for work items widget and choose a shared query and set the chart parameters. Chart types include status—pie, bar, column, stacked bar, and pivot—and trend—stacked area, line, and area—charts.

For more information, see Define a query and Track progress with status and trend query-based charts.

Sample Agile tool light-weight charts

Screenshot of Active bug charts added to dashboards.

Screenshot of Active bugs chart.

Sequence for adding query-based charts to a dashboard

Select one of the following boxes to open the corresponding article.

Tile link to Edit query article.Tile link to Create chart article.Tile link to Add chart to dashboard article.

The steps to creating charts that track manual testing progress and results are similar to the ones for tracking work. The starting point, however, begins with the test plan rather than a query. For example, you can find out how many test cases are ready to run, or how many tests are passing and failing in each test suite. And, just like work item query-based charts, you can add these charts to a dashboard.

For details, see:

Sample light-weight test charts

Screenshot of Web Team test plan is a chart that shows counts of test in various stages. Tests by Suite breaks down the same tests by test suite.

Widgets

You add widgets to a dashboard to display a chart, information, or set of links. Most widgets are configurable. For a description of each supported widget for your platform and version, see the Widget catalog. Here are the widgets that support the indicated service.

Widgets are annotated as follows:

  • Analytics: Widget derives data from Analytics data
  • Build: Widget derives data for a selected build pipeline
  • Project: indicates you can select the project and team when configuring the widget
  • Release: Widget derives data for a selected release pipeline
  • Team: Widget is scoped to a single team
  • Teams: Widget is scoped to one or more teams
  • User: Widget is scoped to the signed in user account
  • Build: Widget derives data for a selected build pipeline
  • Release: Widget derives data for a selected release pipeline
  • Team: Widget is scoped to a single team
  • User: Widget is scoped to the signed in user account

Pipelines


Test Plans


Information and links

Build & Release


Test





Sprint chart widgets

Tile link to Sprint capacity widget. Tile link to Sprint burndown widget

Sprint scope change

There's no chart or widget that tracks changes to sprint scope. However, you can determine work items added to a sprint or moved out of a sprint using the Query Editor. For more information, see About Sprints, Scrum and project management, Sprint scope change.

Sample Cumulative Flow Diagram widget

Screenshot of Cumulative flow diagram widget.

Monitor code activity, build progress and deployment status

With the code tile widgets, you can monitor the activity occurring within a repository or branch folder. Build history displays a histogram of all builds run for a specific build pipeline. Bar color indicates: green-completed, red-failed, and yellow-completed without tests.

Code, build, and release chart widgets

Screenshot of Code tile widget.   Screenshot of Pull request widget.
Screenshot of Build history widget.    Screenshot of Deployment status widget.

Analytics widgets and reports

The Analytics service is the reporting platform for Azure DevOps. As described in What is the Analytics service?, it replaces the previous platform based on SQL Server Reporting Services. The Analytics service supports Analytics widgets, in-context Analytics reports, and Analytics views for Power BI reporting.

The Analytics service is the reporting platform for Azure DevOps. As described in What is the Analytics service?, it replaces the previous platform based on SQL Server Reporting Services. The Analytics service supports Analytics widgets and Analytics views for Power BI reporting.

Note

Analytics is in preview for Azure DevOps Server 2019 and generally available for Azure DevOps Server 2020 and later versions.

Sample Lead time widget

Screenshot of Lead time widget.

For more information, see the following articles:

In-context reports: Work tracking

Azure Boards provides several in-context reports that derive from Analytics data. From your backlog or board, you can view the Cumulative Flow Diagram and team Velocity reports by selecting the Analytics tab. Each report provides interactive controls to provide each user the view of interest to them. From a Sprint backlog, you can view the sprint burndown trend.

Cumulative Flow Diagram

Use the interactive controls to choose the time frame, swimlanes, and workflow states or Kanban board columns.

Screenshot of Open CFD Analytics.

Velocity

Use the interactive controls to choose the count or sum field and number of iterations.

Screenshot of Open Velocity Analytics.

Sprint Burndown Trend

Use the interactive controls to choose the start and end of the sprint and count or sum field to use in the burndown. If you don't track Remaining Work in tasks, you can view burndown based on a count of work items/tasks.

Screenshot of Burndown trend based on Remaining Work.

Azure Boards provides several in-context reports that derive from the work tracking data store. From your backlog or board, you can view the Cumulative Flow Diagram and team Velocity reports by choosing the miniature charts that appear on each page. From a Sprint backlog, you can view the sprint burndown.

Cumulative Flow Diagram

The CFD report shows the count of work items in the backlog based on their state over time.

Screenshot of Opened CFD chart.

Velocity

Velocity is based on the values entered for Effort, Story Points, or Size fields for work items that belong to the Requirement Category.

Screenshot of Web portal, Velocity chart showing seven sprints of in progress and completed work.

Sprint burndown

Each sprint provides access to two charts. The first tracks capacity for the team, team activities—such as Development, Test, Design—and individual team members. The second tracks the sprint burndown for remaining work.

Capacity bars Burndown
Screenshot of Capacity bars. Screenshot of Burndown chart.

You can add the in-context reports to a dashboard using the copy to dashboard option from the report's context menu.

Screenshot of Analytics in-context report, Copy to dashboard action.

Note

You can't add the in-context reports to a dashboard. However, you might find a comparable widget listed in the widget catalog that tracks the same or similar data which you can add to the dashboard.

For more information about these reports, see the following articles:

In-context reports: Pipelines and Test

Several in-context reports are provided for Azure Pipelines. These reports derive from Analytics data. Open a pipeline (or release summary for Test failure) to view the reports and select the Analytics tab. Select View full report on a summary card for a detailed report.

Screenshot of the Analytics tab.

For more information on each in-context Analytics report for pipeline runs, see the following articles:

You can also use Power BI and OData to create reports based on pipeline and test data. For more information, see the Overview of sample reports using OData queries.

Pipeline pass rate report

The Pipeline pass rate report provides a trend of pipeline failure and task failure of the pipeline. You can view the pass rate of the pipeline over a configurable period of time, for example, seven, 14, or 30 days. Find more details in Task failure details, which not only highlights the trend, but also lists the top failing tasks.

Screenshot showing pipeline pass rate report summary.

For more information, see Pipeline pass rate report.

Test failures report

The Test failures report provides a granular view of the top failing tests in the pipeline, along with the failure details. Summary charts are also provided for builds that indicate code coverage and test failures or success.

Screenshot of Test Analytics detail view.

For more information, see Test failures report.

Pipeline duration report

The Pipeline duration report provides the duration trend of a pipeline. It also highlights the average run time of the total successful runs over a period of time, for example, for seven, 14, or 30 days. The report also provides insights on the tasks that affected the duration of the pipeline.

Screenshot of pipeline duration summary.

Screenshot of pipeline duration trend.

For more information, see Pipeline duration report.

In-context reports: Pipeline Test Failures

Azure Pipelines provides an in-context Test failures report, derived from Analytics data. Open a release summary to view the report and select the Analytics tab. Select the summarized card for a detailed report. For more information, see Test failures report.

Screenshot of Analytics Tab, Azure DevOps Server 2019.

Add custom work tracking fields

Add a custom field to add data to support reporting requirements.

Add data to support reporting requirements by adding a custom field Inheritance process or On-premises XML process.

Add a custom field to add data to support reporting requirements.

Marketplace widgets and extensibility

In addition to the widgets available in the widget catalog, you might find interesting widgets in the Marketplace.

Or, you can create your own widget using the REST API.

Next steps