Move an issue before or after another one in board/backlog order (manual rank)
rank_issueMove an issue before or after another one in board/backlog order (manual rank).
Give exactly one of before / after. Only the moved issue is written.
Give EXACTLY ONE of before or after (another issue key in the same project) plus version — never both, never neither. Only the moved issue gets a new version.
WRITE: version must be the version from your latest read of this file (get_issue for issues, list_comments for comments, list_sprints for sprints, get_doc for project docs, read_file for md files). If the file changed since, the call fails with 409 version_conflict and the error contains the current file (details.current, details.current_version): re-read it, re-apply your change on top of the current content and retry with the new version. Never overwrite someone else's change blindly — if your change and theirs disagree, ask the user which to keep.
You act with exactly the rights of the user who owns this token; a project you cannot see returns not_found.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| after | No | Issue key `{PROJECT}-{n}`, e.g. `KJ-101`. | |
| before | No | Issue key `{PROJECT}-{n}`, e.g. `KJ-101`. | |
| version | Yes | Optimistic-lock version of the file; +1 on every write. Every write must send the version it read. | |
| issue_key | Yes | Issue key `{PROJECT}-{n}`, e.g. `KJ-101`. | |
| project_key | Yes | Project key, e.g. `KJ`. 2–10 chars, uppercase letters and digits, starts with a letter. |