jira issue clone¶

• Usage: jira issue clone KEY... [flags]

Run the issue clone mutation for one or more issue keys. Use it when you need the shared clone, move, or delete safety path rather than a specialised Jira screen.

--dry-run previews the mutation locally and does not contact Jira. Live clone and move payloads run through the validate-and-encode pipeline before submission; delete carries no field payload.

Live destructive operations require --force in headless, agent, or --no-input mode. Without --force, an interactive terminal is prompted.

Input¶

--json-input <FILE>¶

Read mutation payload from JSON file (canonical for agents)

Accepts a file.

Safety¶

--dry-run¶

Preview mutation without submitting

--force¶

Confirm destructive mutation

Execution¶

-p --parallelism <N>¶

Maximum concurrent requests (1-16)

Default: 1

Examples¶

jira issue clone PROJ-123 --dry-run # (1)!
jira issue clone PROJ-123 --force # (2)!

1. Preview the change without applying it
2. Apply the change non-interactively