TechPrufer
Get started
Microsoft
Microsoft logoMicrosoft · Feature trail

Azure DevOps Object Limit Tracking

4 posts · Jan 2016 – Aug 2024

What this trail covers

Azure DevOps has introduced a work item revision limit of 10,000 to prevent performance and usability issues caused by automated tools generating excessive revisions. This limit affects updates via the REST API, returning a 500 status code with a specific exception message. Manual updates through the web interface are still permitted. Users with tooling that uses the Work Item Update REST API are advised to check responses, catch exceptions, mark work items for ignoring further updates, and cons. This thread tracks the evolution of Azure DevOps object limits, introducing real-time visibility into resource usage for each organization and project directly within Azure DevOps. This enhancement provides visibility into commonly asked object limits, making it easier for users to manage resources proactively and avoid potential issues.

All Microsoft trails
  1. Introducing Object Limit Tracker in Azure DevOpsIntroduces the Object Limit Tracker in Azure DevOps, providing real-time visibility into resource usage for organizations and projects. This feature visualizes limits for Projects, Work Item Tags, Area Paths, Iteration Paths, Teams, Project Dashboards, and Delivery Plans, enabling proactive resource management.
  2. Team Work Item Automation Rules (Private Preview)Introduced a new feature for automating work item state transitions. Teams can configure rules on the team backlog settings panel to automatically update parent item states based on child item state changes. Rules can be set independently for Stories, Features, and Epics. The automation works across different views like sprint boards and is triggered by updates to child items. The feature is in private preview and will be generally available in early 2024. Limitations include configuration being exclusive to Team Admins, rules only applying to items within the same team, and the use of State Categories instead of direct states.
  3. Revolutionizing Requirement Gathering: Azure DevOps Meets Azure OpenAI using Semantic kernelThis post introduces a new capability for automating requirement gathering and feature creation in Azure DevOps by integrating with Azure OpenAI via Semantic Kernel. It provides detailed steps for setting up semantic functions to generate feature titles and descriptions, and native functions to create work items in Azure DevOps. The post also showcases the use of Sequential Planner for dynamic feature generation.
  4. Work Item Revision LimitsImplemented a work item revision limit of 10,000 for Azure DevOps Service to address performance and usability issues caused by automated tools. This limit specifically impacts updates via the REST API, returning a 500 error with a detailed exception message. Manual updates via the web interface remain unaffected. Guidance is provided for developers to adjust their tooling to handle this new limit by catching exceptions, marking work items for exclusion, logging events, and manually intervening when necessary.
  5. Limit user visibility and collaboration to specific projectsIntroduced a preview feature to restrict user visibility and collaboration to specific projects. This limits users in the 'Project-Scoped Users' group from accessing Organization Settings pages (except Overview and Projects) and restricts their people-picker search and tagging capabilities to members within their current project. This provides an additional layer of isolation and access control for projects.
  7. What’s new in VSTS Sprint 131 UpdateThis post announces the rollout of the Sprint 131 Update for Visual Studio Team Services (VSTS). Key features include the general availability of the Work Items hub, which consolidates important work into new views (following, activity, assigned to you), aiming to reduce the need for custom queries. Additionally, virtual machine support is added to Azure DevOps Projects, allowing for lower-level control over deployed applications. The update also enables the use of AAD-based alternate email accounts for Visual Studio subscriptions.
  8. Receive an error when resolving a bug created by your build?This post addresses a specific issue where the 'Assigned To' field in a bug created by a failed build could not be resolved due to a change in how work items are assigned to groups. It provides a workaround by specifying an explicit value for the System.CreatedBy field in the build definition, allowing users to unblock themselves while a permanent fix is being worked on.