GT-ISSUE-MOVE(1) gitea-cli Manual GT-ISSUE-MOVE(1)

gt-issue-move - Move an issue to a column of its project board

gt issue move {<number> | <url>} [to] <column> [flags]

Move an issue to another column of the project board it is on. The column is matched by ID, then by name, then ignoring case, spaces and punctuation, so that in-progress finds "In progress". An issue on several projects needs --project to say which board to move it on. Moving issues on organization projects needs a token that can write to the organization.

An issue can be supplied as argument in any of the following formats:
- by number, e.g. "123" or "#123"
- by URL, e.g. "https://gitea.com/OWNER/REPO/issues/123"
- by repository and number, e.g. "OWNER/REPO#123"
Several issues must be in one repository. Next to "OWNER/REPO#123" or a URL, "124" means
OWNER/REPO#124, unless gt targets another repository otherwise, such as the clone's, --repo
or GITEA_CLI_REPO: then the command fails, and the number must be qualified.

-h, --help[=false] help for move

--project="" Move the issue on the project with this ID or title, a number being an ID first

--cwd="" Working directory for repository discovery

--debug[=false] Log the method, URL, status, and duration of each HTTP request to stderr

--host="" Gitea instance URL, including any base path

--interactive[=false] Allow prompts with machine output

--no-input[=false] Disable prompts and implicit editor/browser interactions

--remote="" Git remote used for repository discovery

-R, --repo="" Select a repository as OWNER/REPO or URL

--sudo="" Perform API requests as this user (requires an administrator account)

--user="" Account name on the selected instance

$ gt issue move 47 to Todo
$ gt issue move 47 to "In progress"
$ gt issue move 47 in-progress --project Roadmap

gt-issue(1)

Nov 2026 gitea-cli