Create Issue: Jira action

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
Project Key project_key	string	Required	The short project key (e.g. PROJ, ENG)
Issue Type issue_type	options	Required	Issue Type. Options: Task, Story, Bug, Epic, Sub-task
Summary summary	string	Required	A brief summary of the issue
Description description	string	Optional	Detailed description of the issue (plain text)
Priority priority	options	Optional	Priority. Options: Highest, High, Medium, Low, Lowest
Assignee Account ID assignee_id	string	Optional	Atlassian account ID of the assignee
Labels labels	string	Optional	Comma-separated labels

Sample request

{
  "project_key": "e.g. PROJ",
  "issue_type": "{{trigger.issue_type}}",
  "summary": "e.g. Fix login page redirect",
  "description": "e.g. When users click login, they are redirected to a 404 page...",
  "priority": "{{trigger.priority}}"
}

Returns

{
  "id": "10001",
  "key": "PROJ-123",
  "self": "https://your-domain.atlassian.net/rest/api/3/issue/10001"
}

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

FAQ

Questions about Create Issue.

What does the Create Issue action do in Jira?

Creates a new issue (story, task, bug, epic, etc.) in a Jira project with summary, description, type, assignee, priority, labels, components, and custom fields. Standard write for converting external alerts into tracked work.

What inputs does Create Issue require?

Required: Project Key, Issue Type, Summary. 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 Create Issue support batch operations?

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

More actions