corestack-workitems

To enforce mandatory fields on Azure DevOps work items, validate them against hierarchy rules requiring Title, Description, Assigned To, Area Path, Iteration Path, and Bundle for Features, User Stories, and Tasks.

To prevent orphaned Azure DevOps User Stories and Tasks, enforce a strict parent-child hierarchy linking Tasks to User Stories and User Stories to Features during creation and updates.

For Azure DevOps Tasks, Original Estimate and Remaining Work fields are enforced with default behaviors, alongside required fields like Title, Description, Assigned To, and Iteration Path.

Yes, Azure DevOps supports validating Custom Bundle fields for Features and User Stories by applying field mapping rules to ensure the Bundle field is populated during work item creation and updates.

To audit Azure DevOps work items for missing parent links, apply validation patterns checking that User Stories have a Parent Feature and Tasks have a Parent User Story to prevent misconfigurations.

Azure DevOps work item validation fails on Iteration Path because it is a mandatory field for Features, User Stories, and Tasks, requiring a valid value to maintain proper hierarchy and configuration standards.