ActionLinearUpdated September 2026

How do I update a Linear issue?

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

Update Issue in Linear — 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.

FieldTypeRequiredDescription
Issue ID
issueId
stringRequiredThe Linear issue UUID
Title
title
stringOptionalTitle
Description
description
stringOptionalDescription
Priority
priority
optionsOptionalPriority. Options: No priority, Urgent, High, Medium, Low
State ID
stateId
stringOptionalWorkflow state UUID (e.g. 'In Progress' state ID)
Assignee ID
assigneeId
stringOptionalAssignee ID. Example: user-uuid
Sample request
{
"issueId": "e.g. issue-uuid",
"title": "{{trigger.title}}",
"description": "{{trigger.description}}",
"priority": "{{trigger.priority}}",
"stateId": "e.g. state-uuid"
}
Returns
{
"data": {
"issueUpdate": {
"issue": {
"id": "uuid",
"state": {
"name": "In Progress"
},
"title": "Updated title",
"identifier": "ENG-123"
},
"success": true
}
}
}

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

Triggered by

Apps that pair well as the trigger for Update Issue.

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

FAQ

Questions about Update Issue.

What does the Update Issue action do in Linear?
Updates fields on an existing Linear issue: title, description, state, priority, assignee, estimate, labels, project, or cycle. Only the fields you pass are changed.
What inputs does Update Issue require?
Required: Issue 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 Linear returns an error?
The run history shows the failed step with its input and the error message Linear 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 Issue support batch operations?
Run Update Issue 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 Linear's rate limits.
More actions

Other Linear actions.

Update Issue in Linear — start free