Start free
ActionAzure DevOpsUpdated June 2026

How do I update an Azure DevOps work item?

Short answer: You can update work item in Azure DevOps by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Azure DevOps Update Work Item action to a workflow, map its 4 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Use this actionAll 5 Azure DevOps actions
Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

FieldTypeRequiredDescription
Work Item ID
id
stringRequired–
New State
state
stringOptionalActive, Resolved, Closed
New Title
title
stringOptional–
Assigned To (email)
assigned_to
stringOptional–
Sample request
{
  "id": "{{trigger.id}}",
  "state": "Active, Resolved, Closed",
  "title": "{{trigger.title}}",
  "assigned_to": "{{trigger.assigned_to}}"
}
Returns
{
  "id": 42,
  "rev": 2,
  "fields": {
    "System.State": "Resolved"
  }
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Update Work Item.

Any of these apps can fire this action as part of a workflow.

Gmail → Azure DevOps
1 Gmail triggers
Slack → Azure DevOps
13 Slack triggers
Google Sheets → Azure DevOps
2 Google Sheets triggers
HubSpot → Azure DevOps
18 HubSpot triggers
FAQ

Questions about Update Work Item.

What does the Update Work Item action do in Azure DevOps?
Partial update on a work item — change state, assignee, priority, or any field. For "auto-transition to Resolved when the related PR merges" or "reassign all open bugs from this engineer to their replacement" bulk-update workflows.
What inputs does Update Work Item require?
Required: Work Item ID. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Azure DevOps returns an error?
The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.
Does Update Work Item support batch operations?
Yes. Run Update Work Item inside a Loop node to process arrays. TinyCommand handles Azure DevOps's rate limits automatically so you don't have to throttle manually.
More actions

Other Azure DevOps actions.

Action
Add Comment to Work Item
Posts a comment to a work item's discussion thread. Useful for "AI-summarised context → log on the work item" or for cross-tool notifications ("CI build failed → comment on the related work item with the error log").
Action
Create Work Item
Creates a Bug, Task, User Story, Feature, or Epic with title, description, assignee, area path, plus custom fields configured per the project's process template. Required fields depend on the work-item type and project template.
Action
Get Work Item
Returns a work item by ID with all standard and custom fields, relations (parent/child links), and history if requested. The standard lookup for workflows that received a work-item ID upstream and need richer detail.
Action
Query Work Items (WIQL)
Runs a Work Item Query Language (WIQL) statement — Azure DevOps's SQL-like syntax for filtering across the work-item store. Returns matching work-item IDs; follow up with Get Work Item for full payload. Useful for dashboards and reporting workflows.