删除部分VSTS工作项后，部分工作项无法修改/删除的问题求助

This is a common hiccup when a parent work item still holds a reference to a child that’s already been deleted—Azure DevOps (formerly VSTS) tries to validate that referenced work item during delete/edit operations, and throws the TF401232 error because it can’t locate the removed child. Here’s how to resolve it:

Step 1: Clean Up the Invalid Association via UI #

Start with the simplest approach through the web interface:

• Open work item 47420
• Navigate to the Related module/tab
• Locate the association entry pointing to work item 53559 (it should still appear even though the child is deleted)
• Remove that specific stale association
• Save the work item, then try deleting it again

Step 2: Use Azure DevOps CLI if UI Fails #

If the UI won’t let you remove the dead association (e.g., the entry is greyed out or unresponsive), turn to the Azure DevOps CLI:

1. Install the CLI if you haven’t already, then authenticate and set your default organization/project:

   az login
   az devops configure --defaults organization=https://dev.azure.com/your-org-name project=your-project-name
   

2. Fetch all relations for work item 47420 to get the ID of the invalid association:

   az boards work-item show --id 47420 --include-relations
   

   Scan the output for the relation referencing 53559 and note its unique relation-id.
3. Remove the stale relation:

   az boards work-item relation remove --id 47420 --relation-id <your-relation-id>
   

4. Now you can delete the work item via CLI or UI:

   az boards work-item delete --id 47420 --yes
   

Step 3: Contact Azure DevOps Support as a Last Resort #

If neither method works, the stale association might be stuck in the backend. Reach out to Azure DevOps support with the work item IDs (47420 and 53559) and the full error message—they can help clean up the invalid reference directly.

The root cause here is that deleting a child work item doesn’t always automatically clean up all cross-references in parent items. Azure DevOps enforces validation on all associated items during modify/delete operations, so the missing child triggers the "doesn’t exist" error even though you’re targeting the parent.

内容的提问来源于stack exchange，提问作者Ignacio Soler Garcia