ActionAzure DevOpsUpdated September 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.

Update Work Item in Azure DevOps — start free All 5 Azure DevOps actions

Update Work Item in Azure DevOps — start free

Inputs

The fields this action accepts.

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

Field	Type	Required	Description
Work Item ID id	string	Required	–
New State state	string	Optional	Active, Resolved, Closed
New Title title	string	Optional	–
Assigned To (email) assigned_to	string	Optional	–

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.

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 run history shows the failed step with its input and the error message Azure DevOps returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Update Work Item support batch operations?

Run Update Work Item inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Azure DevOps's rate limits.

More actions