Get Analytics insights comparable to those provided by SQL Reporting Services reports
Azure DevOps Server 2022 | Azure DevOps Server 2020 | Azure DevOps Server 2019
You can get similar insights into your Azure DevOps processes made available through the legacy SQL Server Reporting Services reports using the Analytics service. This article provides guidance for migrating from each SQL Server Reporting Services reports to using the Analytics service.
Prerequisites
To access data available from the Analytics service, you must meet the following criteria:
- You must be a member of the projects from which you want to view data. If you haven't been added as a project member, get added now.
- Have the View Analytics permission set to Allow. See Grant permissions to access Analytics. Anyone with this permission, except those granted Stakeholder access, can view Analytics data.
- Have enabled or installed Analytics. You must be an account owner or a member of the Project Collection Administrators group to enable the service.
- The service for which data is collected must be enabled. For example, Boards must be enabled to view work tracking data. To re-enable it, see Turn an Azure DevOps service on or off.
- To use Power BI, have installed a recent version of Power BI Desktop. You can download this client application from the official Power BI Desktop download page.
Work tracking and project management reports
The following table summarizes Analytics reports, widgets, and other tools that you can use to gain comparable insights to the work tracking reports defined using the SQL Server Reporting services.
SQL Reporting Services reports
Migration guidance
Backlog Overview (Scrum)1
Requirements Overview (CMMI)1
Stories Overview (Agile)1
Display an overall progress (work breakdown) and test results for selected backlog items.
- To view rollup progress, add rollup columns to a backlog to view progress bars and remaining work counts.
- Use Power BI to generate a Requirements tracking report.
Release Burndown (Scrum)
Displays a column chart showing how much work remained at the start of each sprint in a release.
- Configure a Burndown widget.
- Create a Power BI Release burndown report.
Burndown and Burn Rate (Agile and CMMI)
Sprint Burndown (Scrum)
Displays an area trend chart for a team sprint showing the completed and remaining hours.
Remaining Work (Agile and CMMI)
Displays an area chart showing remaining and completed hours of work for a team sprint.
- Configure the Sprint burndown widget on a team dashboard, choosing the Task backlog and Remaining Work.
Status on All Iterations (Agile and CMMI)
Displays a rollup by sprint of stories that were closed, completed hours, and bugs active, closed, or resolved.
- Configure a query that spans several sprints and define a chart for the information of interest.
Requirements Progress (CMMI)1
Stories Progress (Agile)1
Displays overall progress bars for requirements or user stories, along with remaining hours.
- To view rollup progress, add rollup columns to a backlog to view progress bars and remaining work counts.
- Use Power BI to generate a Requirements tracking report.
Unplanned Work (Agile and CMMI)
Displays an area trend chart for planned work and work added after the start of the sprint.
- Configure the Sprint burndown widget on a team dashboard, the widget will show total scope increase.
- Configure a query at the start of a sprint to track work moved in or moved out of a sprint. To learn how, see Scrum overview, List work items added after the start of the sprint and List work items moved out of the sprint.
Velocity (scrum)
Displays a column chart showing the level of Effort completed by the team for each sprint within the selected time period.
- Configure the Velocity widget on a team dashboard.
- View the Built-in velocity report.
Notes:
- The overview and progress reports depend on linking tasks, test cases, and bugs to backlog items. Link these items using the parent-child link for tasks and bugs and the Tested By link for test cases.
Bug status and trends
The following table summarizes Analytics reports, widgets, and query charts that you can use to gain comparable insights to the bug reports defined using the SQL Server Reporting services.
SQL Reporting Services report
Migration guidance
Bug Status
Presents a stacked area chart of bug status, pie chart for bug priority, and assignment of bugs.
- Define a team dashboard and use three Chart work items widgets to recreate similar information.
- Use Power BI to generate a Bug trends report and define three different charts based on the data.
Bug Trends
Displays a calculated rolling average of the number of bugs that a team has opened, resolved, and closed.
(INVESTIGATING) The Analytics service doesn't store a calculated rolling average but it's possible to calculate one using Power BI.
Reactivations
Displays a stacked area chart of resolved and reactivated bugs over time to gain insight into effectiveness of team on closing bugs.
Create a work item query and area chart adapting the following WIQL syntax as needed.
SELECT
[System.Id],
[System.CreatedDate],
[System.State],
[System.AssignedTo],
[System.Title],
[System.IterationPath]
FROM workitems
WHERE
[System.TeamProject] = @project
AND [System.WorkItemType] = 'Bug'
AND EVER [System.State] = 'Closed'
AND NOT [System.State] IN ('Closed', 'Cut')
AND [System.ChangedDate] >= @today - 60
Pipelines, build, and release reports
The following table summarizes Analytics reports and widgets that you can use to gain comparable insights to the build reports defined using the SQL Server Reporting services.
Note
Build operations have significantly changed with the release of TFS 2018 and later versions. For example, manually assigning the build quality is no longer supported. YAML defined build pipelines support additional of tasks to automate testing, code coverage, and other operations. TO learn more, see Pipelines documentation.
SQL Reporting Services report
Migration guidance
Build Quality Indicators (Agile and CMMI) Presents code coverage, code churn and active bugs associated with select build definitions.
- See Build history widget to view the success/failure trend of a selected build pipeline.
- See Review code coverage results to determine the proportion of your project's code that is actually being tested by tests such as unit tests.
- See the built-in Pipeline pass rate report for key metrics of pass rate of the pipeline over a specified period, failure trends, and top failing tasks and their failed runs.
- Use Power BI to generate a Pipeline stage wise failures sample reportto view a pipeline's daily stage failures.
Build Success Over Time
Presents code coverage, code churn and active bugs associated with select build definitions.
- See Build history widget to view the success/failure trend of a selected build pipeline.
- See the built-in Pipeline pass rate report for key metrics of pass rate of the pipeline over a specified period, failure trends, and top failing tasks and their failed runs.
- Use Power BI to generate a Pipeline stage wise failures sample reportto view a pipeline's daily stage failures.
Build Summary
Presents code coverage, code churn and active bugs associated with select build definitions.
- See Build history widget to view the success/failure trend of a selected build pipeline.
- See the built-in Pipeline pass rate report for key metrics of pass rate of the pipeline over a specified period, failure trends, and top failing tasks and their failed runs.
- Use Power BI to generate a Pipeline stage wise failures sample reportto view a pipeline's daily stage failures.
Test Plans and pipeline and test reports
The following table summarizes Analytics reports, widgets, and other tools that you can use to gain comparable insights to the test plan and progress reports defined using the SQL Server Reporting services.
SQL Reporting Services report
Migration guidance
Test Case Readiness
Displays an area trend chart that shows the number of test cases Design and Ready state
- See Chart for test plans widget to create a similar chart using the Test Plans chart tool. Optionally add to a dashboard.
Test Plan Progress
Displays an area trend chart that shows the number of test points run and their status.
- To track a team's progress with respect to planned testing of a product or service, see the built-in Progress report.
- Use Power BI to generate Test Plans reports:
- Requirements tracking sample report
- Requirements tracking rollup sample report
- Manual test suites aggregated view sample report
- Tester by outcome matrix sample report
- Configuration by outcome matrix sample report
Next steps
Related articles
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for