ActionJiraUpdated June 2026

How do I update a Jira issue?

Short answer: You can update issue in Jira by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Jira 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 Jira — start free All 17 Jira actions

Update Issue in Jira — 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
Issue Key or ID issue_key	string	Required	Issue Key or ID. Example: PROJ-123
Summary summary	string	Optional	Summary. Example: Updated summary
Description description	string	Optional	Description
Priority priority	options	Optional	Priority. Options: Highest, High, Medium, Low, Lowest
Assignee Account ID assignee_id	string	Optional	Assignee Account ID. Example: 5b10a2844c20165700ede21g
Labels labels	string	Optional	Comma-separated labels (replaces all existing labels)

Sample request

{
  "issue_key": "e.g. PROJ-123",
  "summary": "e.g. Updated summary",
  "description": "{{trigger.description}}",
  "priority": "{{trigger.priority}}",
  "assignee_id": "e.g. 5b10a2844c20165700ede21g"
}

Returns

{
  "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.

2 Google Sheets triggers

HubSpot → Jira

18 HubSpot triggers

FAQ

Questions about Update Issue.

What does the Update Issue action do in Jira?

Updates fields on an existing Jira issue: summary, description, priority, assignee, labels, components, custom fields. Only the fields you pass are changed.

What inputs does Update Issue require?

Required: Issue Key or 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 Jira 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 Issue support batch operations?

Yes. Run Update Issue inside a Loop node to process arrays. TinyCommand handles Jira's rate limits automatically so you don't have to throttle manually.

More actions