The Azure DevOps team hit the ground running during Q1 2024. In this post, we will highlight some of the new and exciting features now available to help you enhance your development experience.

Show GitHub pull request details

In Azure Boards, there is a new view to provide more information regarding the status of a pull request. While still in preview, this experience provides information such as a pull request needing review, still being in draft mode, or having status checks running. This information is visible without even having to open the pull request. To participate in this preview, contact the team directly.

Add link to GitHub commit or pull request

After several weeks in preview, the enhanced experience for linking work items to GitHub is now generally available in the New Boards Hub. You’ll no longer need to have multiple windows open, switch between Azure DevOps and GitHub, and copy/paste the URL of the GitHub PR. Now, you’re able to search for and select the desired repository, then drill down to find and link to a specific pull request or commit.

Resource utilization alerts for Azure Pipeline agents

Last year, you saw the ability to monitor memory and disk utilization by the Pipelines agents. Now, you have enhanced visibility of resource constraint alerts. This update will help you understand why pipeline jobs are failing and to ensure you’re able to get sufficient resources for your agent.

Custom CodeQL queries

You can now create custom CodeQL queries in Code scanning alerts for GitHub Advanced Security for Azure DevOps. With this feature, you can craft queries tailored to identify issues specific to your codebase. You can create and publish packs containing custom queries, execute these queries in your pipelines, and customize vulnerability detection.

Team Automation Rules is generally available

Previously, the overall state of a User Story would remain unchanged even after child tasks have been updated. You could automate the closure of the parent item, but it required web hooks and custom code, and really wasn’t configurable. You can now configure each backlog level to automate the opening and closing of work items based on the state of its child items. Each backlog level can be configured differently depending on the preferences of your team.

For more information, contact our team of experts here at PRAKTIK.