Filter on work item history

With this update, we included multiple updates to Azure Boards. On Delivery Plans, we added a Last accessed column to the directory page and we improved the experience by allowing you to see all the dependencies lines across all the work items on the screen. In addition, we've added a filter option to the work item history tab. This filter will let you quickly find revisions made to individual fields by specific people.

Check out the release notes for details.

Azure Boards

• Filter on work item history
• Last Accessed column on Delivery Plans page
• Visualize all dependencies on Delivery Plans
• New work item revision limits

Azure Pipelines

• Current project set as default scope for build access token in classic pipelines

Azure Boards

Filter on work item history

Work items are designed with collaboration in mind. They also keep track of every change for full traceability. This can create a long revision history making it difficult to understand when changes happen to specific fields. In this sprint, we have added a filter option to the work item history tab. This allows you to quickly find revisions made to individual fields by specific people.

We prioritized this feature based on one of the top suggestion from the Developer Community.

Note

This feature is available with the New Boards Hubs preview.

Last Accessed column on Delivery Plans page

The Delivery Plans directory page provides a list of the plans defined for your project. You could sort by: Name, Created By, Description, Last configured, or Favorites. With this update, we have added a Last accessed column to the directory page. This provides visibility on when a Delivery Plan was last opened and looked at. As a result, it is easy to identify the plans that are no longer used and can be deleted.

Visualize all dependencies on Delivery Plans

Delivery Plans has always provided the ability to see the dependencies across work items. You can visualize the dependency lines, one by one. In this sprint, we improved the experience by allowing you to see all the dependencies lines across all the work items on the screen. Simply click the dependencies toggle button on the top right of your delivery plan. Click it again to turn off the lines.

New work item revision limits

Over the past few years, we have seen organizations with automated tools generate tens of thousands of work item revisions. This creates issues with performance and usability on the work item form and the reporting REST APIs. To mitigate the issue, we have implemented a work item revision limit of 10,000 to the Azure DevOps Service. The limit only affects updates using the REST API, not the work item form.

Click here to learn more about the revision limit and how to handle it in your automated tooling.

Azure Pipelines

Current project set as default scope for build access token in classic pipelines

Azure Pipelines uses job access tokens to access other resources in Azure DevOps at run-time. A job access token is a security token that is dynamically generated by Azure Pipelines for each job at run time. Previously, when creating a new classic pipelines, the default value for the access token was set to Project Collection. With this update we are setting the job authorization scope to current project as the default when creating a new classic pipeline.

You can find more details about job access tokens in the Access repositories, artifacts, and other resources documentation.

Next steps

Note

These features will roll out over the next two to three weeks.

Head over to Azure DevOps and take a look.

Go to Azure DevOps

How to provide feedback

We would love to hear what you think about these features. Use the help menu to report a problem or provide a suggestion.

You can also get advice and your questions answered by the community on Stack Overflow.

Thanks,

Aaron Hallberg