{"id":69514,"date":"2024-09-27T05:47:52","date_gmt":"2024-09-27T13:47:52","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/devops\/?p=69514"},"modified":"2024-09-27T05:47:52","modified_gmt":"2024-09-27T13:47:52","slug":"azure-boards-september-update","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/devops\/azure-boards-september-update\/","title":{"rendered":"Azure Boards, September Update"},"content":{"rendered":"

September was a productive month for Azure Boards, and we\u2019re excited to share some of the new features coming your way.<\/p>\n

Area and Iteration Level Fields<\/h2>\n

Area and iteration level fields have been crucial for querying or displaying results based on their specific levels:<\/p>\n

(Root) Level 1 \/ Level 2 \/ Level 3 \/ etc.<\/p>\n

Previously limited to a few organizations, these fields are now available to all Azure DevOps organizations using New Boards Hub<\/a>. You can use them in queries and display them as backlog columns, but they are not supported in style rules, swim lane rules, card fields, and delivery plan fields.<\/p>\n

Permanently delete attachments<\/h2>\n

In some cases, simply removing an attachment from a work item may not fully resolve security risks, especially if the file is flagged as malicious. Shared links to the attachment could still be accessible across other work items, comments, or external channels. To address this, we added a feature that allows users with “Permanently delete work items” permission to permanently remove attachments.<\/p>\n

\"Image<\/a><\/p>\n

This action can be performed from the Attachments<\/strong> tab on the work item form, under a new section labeled Deleted Attachments<\/strong>. This section is visible only to users with the necessary permissions to permanently delete work items. Once an attachment is permanently deleted, all associated links return a “File attachment does not exist” error.<\/p>\n

REST API support for connecting GitHub repositories<\/h2>\n

We’re introducing three new REST API endpoints that enable you to automate the addition and removal of GitHub repositories in your Azure DevOps Projects. Additionally, we increased the repository limit per connection from 500 to 2,000 when using these endpoints. They are designed to help teams automate the process of connecting their GitHub repositories to an Azure DevOps project.<\/p>\n

These endpoints include:<\/p>\n