Add `vektor issue view` command #10

New issue

Open

opened 2026-03-16 21:24:54 +00:00 by austin · 0 comments

austin commented

2026-03-16 21:24:54 +00:00

Owner

View a single issue's full details from the CLI using human-readable references.

What needs to happen

CLI:
vektor issue view VEK-3

Parse the argument by splitting on - to extract project key and issue number. Display: title, status, priority, description (if any), created by, created at, updated at.

Backend change needed:
Add a new endpoint: GET /api/projects/{projectKey}/issues/{number}. The current API only has list and update-by-UUID — there's no way to fetch a single issue by its human-readable identifier.

Key files

internal/api/issues.go — new handler for single issue by number
internal/api/server.go — new route registration

View a single issue's full details from the CLI using human-readable references. ## What needs to happen **CLI:** `vektor issue view VEK-3` Parse the argument by splitting on `-` to extract project key and issue number. Display: title, status, priority, description (if any), created by, created at, updated at. **Backend change needed:** Add a new endpoint: `GET /api/projects/{projectKey}/issues/{number}`. The current API only has list and update-by-UUID — there's no way to fetch a single issue by its human-readable identifier. ## Key files - `internal/api/issues.go` — new handler for single issue by number - `internal/api/server.go` — new route registration