Add `vektor issue update` command #11

New issue

Open

opened 2026-03-16 21:26:05 +00:00 by austin · 0 comments

austin commented

2026-03-16 21:26:05 +00:00

Owner

Update issue fields from the CLI using human-readable references.

What needs to happen

CLI:
vektor issue update VEK-3 --status in_progress --priority high --title "New title"

All flags are optional (at least one required). Uses the same VEK-3 ref parsing as issue view.

Backend change needed:
Add PATCH /api/projects/{projectKey}/issues/{number} endpoint. The existing PATCH /api/issues/{id} uses UUIDs, which the CLI shouldn't need to know about. The new endpoint resolves project key + number to the issue internally.

Key files

internal/api/issues.go — new handler for update-by-number
internal/api/server.go — new route registration

Update issue fields from the CLI using human-readable references. ## What needs to happen **CLI:** `vektor issue update VEK-3 --status in_progress --priority high --title "New title"` All flags are optional (at least one required). Uses the same `VEK-3` ref parsing as `issue view`. **Backend change needed:** Add `PATCH /api/projects/{projectKey}/issues/{number}` endpoint. The existing `PATCH /api/issues/{id}` uses UUIDs, which the CLI shouldn't need to know about. The new endpoint resolves project key + number to the issue internally. ## Key files - `internal/api/issues.go` — new handler for update-by-number - `internal/api/server.go` — new route registration