jira issue rank¶
- Usage:
jira issue rank KEY... (--before ANCHOR | --after ANCHOR) [flags]
Move one or more issues so they sit immediately before or after an anchor issue in backlog order (Jira's LexoRank: a sortable rank string per issue, so reordering never renumbers the rest) — the headless equivalent of dragging rows in the web UI's backlog. The issues keep the order you pass them in.
Exactly one anchor is required: --before places the issues above it, --after below it. Key lists and ranges expand like every multi-key command, and more than 50 keys are chunked transparently with the order preserved end-to-end. Verify the result with jira issue list --jql "project = X ORDER BY Rank ASC".
Ranking is Jira Software board functionality: a project with no board (no rank field) rejects it, as does an anchor you cannot rank against. --dry-run previews the submission order locally and never contacts Jira.
Rank¶
--after <ANCHOR>¶
Anchor issue the ranked issues are placed immediately below
--before <ANCHOR>¶
Anchor issue the ranked issues are placed immediately above
Safety¶
--dry-run¶
Preview the submission order without contacting Jira
Output fields¶
With --output json, the response envelope's data object carries these fields. Run jira schema for the full machine-readable schema.
| Field | Type | Description |
|---|---|---|
anchor |
string | The issue the ranked set was placed relative to. |
chunks |
integer | How many 50-issue requests the set was split into. |
dry_run |
boolean | |
order[] |
string | |
position |
string | |
ranked |
boolean | false only on the no-profile degraded path. |
Examples¶
jira issue rank PROJ-7 PROJ-9 --before PROJ-3
jira issue rank PROJ-20:24 --after PROJ-50 # (1)!
jira issue rank PROJ-7 PROJ-9 --before PROJ-3 --dry-run --output=json # (2)!
- Move a range to the bottom of another issue
- Preview the order without contacting Jira