Add vektor issue list with filtering #9

Open
opened 2026-03-16 21:22:02 +00:00 by austin · 0 comments
Owner

List issues with optional status and priority filters.

What needs to happen

CLI:
vektor issue list --project VEK --status todo,in_progress --priority high

Table output: number (as VEK-3), status, priority, title.

Backend change needed:
The current GET /api/projects/{key}/issues endpoint returns all issues unfiltered. Add ?status=todo&priority=high query parameter support with conditional WHERE clauses in the SQL query. This follows the same pattern as the existing handleUpdateIssue dynamic query building, but for SELECT instead of UPDATE.

Key files

  • internal/api/issues.gohandleListIssues needs query param filtering
  • cmd/vektor/ — new issue list command
List issues with optional status and priority filters. ## What needs to happen **CLI:** `vektor issue list --project VEK --status todo,in_progress --priority high` Table output: number (as VEK-3), status, priority, title. **Backend change needed:** The current `GET /api/projects/{key}/issues` endpoint returns all issues unfiltered. Add `?status=todo&priority=high` query parameter support with conditional WHERE clauses in the SQL query. This follows the same pattern as the existing `handleUpdateIssue` dynamic query building, but for SELECT instead of UPDATE. ## Key files - `internal/api/issues.go` — `handleListIssues` needs query param filtering - `cmd/vektor/` — new issue list command
austin added this to the CLI Core milestone 2026-03-16 21:22:02 +00:00
austin self-assigned this 2026-03-16 21:22:02 +00:00
austin added this to the Vektor - CLI project 2026-03-16 21:22:02 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
austin/vektor#9
No description provided.