ActionJiraUpdated September 2026

How do I link two Jira issues?

Short answer: You can link issues in Jira by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Jira Link Issues action to a workflow, map its 3 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Link Issues in Jira — start free All 17 Jira actions

Link Issues 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 (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.

Triggered by

Apps that pair well as the trigger for Link Issues.

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 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 run history shows the failed step with its input and the error message Jira 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 Link Issues support batch operations?

Run Link Issues 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 Jira's rate limits.

More actions