Skip to content

jira issue move

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

Run the issue move 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

Output fields

With --output json, the response envelope's data object carries these fields. Run jira agent schema for the full machine-readable schema.

Field Type Description
dry_run boolean
issue.id string
issue.key string
issue.self string
payload.fields object | null
result.comments[] object Fields: author, body, created, id, self, updateAuthor, …
result.editmeta object Fields: fields
result.fields object Fields: assignee, comment, components, created, description, fixVersions, …
result.id string
result.key string
result.linked_issues[] object
result.self string
result.subtasks[] object
result.transitions[] object Fields: hasScreen, id, name
result.worklogs[] object Fields: comment, id, started, timeSpentSeconds
warnings[].field string
warnings[].lossy boolean
warnings[].mark_type string
warnings[].message string
warnings[].node_type string
warnings[].path string
warnings[].type string

Examples

jira issue move PROJ-123 --dry-run # (1)!
jira issue move PROJ-123 --force # (2)!
  1. Preview the change without applying it
  2. Apply the change non-interactively