Link Issues: 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
Issue Key (from) inwardIssueKey	string	Required	Issue Key (from). Example: PROJ-1
Linked Issue Key (to) outwardIssueKey	string	Required	Linked Issue Key (to). Example: PROJ-2
Link Type linkType	options	Optional	Link Type. Options: Blocks, Clones, Duplicates, Relates To, Is Blocked By

Sample request

{
  "inwardIssueKey": "e.g. PROJ-1",
  "outwardIssueKey": "e.g. PROJ-2",
  "linkType": "{{trigger.linkType}}"
}

Returns

{
  "success": true
}

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

FAQ

Questions about Link Issues.

What does the Link Issues action do in Jira?

Creates a link between two Jira issues (blocks/is blocked by, relates to, duplicates, etc.). Used to maintain cross-issue relationships from automated triage.

What inputs does Link Issues require?

Required: Issue Key (from), Linked Issue Key (to). 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 Link Issues support batch operations?

Yes. Run Link Issues 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