Give Each Azure DevOps Work Item a Different Value in One Pass

What bulk edit actually does

Select several work items in a query or backlog and choose "Edit work items in bulk." Pick the fields you want to change, set a value for each, and Azure DevOps applies that exact value to every selected item. There is no per-row column: whatever you type into the iteration path or assigned-to field lands on all of them, identically.

When one value isn't enough

• Reassigning a mixed batch of work items to different owners.
• Moving items into different iterations based on triage notes that vary per item.
• Correcting story points or effort estimates that differ from item to item.
• Setting a status or priority that depends on each item's own context, not a shared decision.

None of these fit the bulk-edit panel. Each row needs its own value, and the panel has no concept of a row.

The spreadsheet workaround

1. Export the query result to a workbook, keeping work item ID and revision.
2. Edit the field values you actually want, one row per work item.
3. Upload the workbook and review a per-row plan before anything writes.
4. Commit only once the plan matches what you intended.

Keep the work item ID and revision columns in the sheet. Matching by title, or dropping the revision, is how a bulk update silently overwrites someone else's change.