/move

/jira:move

Transition a Jira ticket through its workflow.

Step 1: Parse arguments

• <TICKET-ID> — required, normalize informal forms.
• <target-status> — optional. Status name as shown in the workflow (e.g. "In Progress", "In Review", "Done"). Match case-insensitively.
• --agent — JSON output.

Step 2: Discover transitions if needed

If <target-status> is missing, OR is given but does not match an available transition, list current transitions:

jira issue list --transitions <TICKET-ID>
# fallback if unsupported:
jira issue view <TICKET-ID> --raw 2>/dev/null | jq -r '.transitions[]?.name'

In default mode: render a numbered list and ask the user to pick by number or name. In --agent mode without a target: emit the list as JSON and stop (the caller will choose).

Step 3: Move

jira issue move <TICKET-ID> "<target-status>"

Step 4a: Default output

✅ PU-1776 → In Review
URL: https://vialytics.atlassian.net/browse/PU-1776

Step 4b: --agent output

Successful move:

{
  "key": "PU-1776",
  "ok": true,
  "from": "In Progress",
  "to": "In Review",
  "url": "https://vialytics.atlassian.net/browse/PU-1776"
}

Discovery only (no target given):

{
  "key": "PU-1776",
  "current": "In Progress",
  "transitions": ["In Review", "Blocked", "Done"]
}

Failure: { "key": "PU-1776", "ok": false, "error": "<message>" }.