Problem
The Buildkite CLI can reprioritize jobs (bk job reprioritize), but builddeck offers no way to change job priority from the TUI. When a critical build's job is stuck behind lower-priority work, users must drop to the CLI or browser to fix the ordering.
Proposed Feature
Add a job reprioritization action in the build detail pane (steps list). When a step is highlighted, pressing a key (e.g. p or ctrl+p) opens a small inline prompt to set a new priority value.
UX
Steps:
PASS :lint agent-1
FAIL :test agent-2 exit 1
> BLCK :deploy [blocked]
NRUN :integration-tests
→ Press `p` → inline prompt: "Priority (0-1000): [500]"
→ Enter value → PUT to API → step refreshes with new priority
The prompt should appear in the status bar area (non-modal, keeping context visible):
Status: Enter new priority for :deploy (0-1000): [500]
Why this fits a TUI
- Job priority is a quick operational tweak — perfect for a keyboard shortcut
- The TUI already shows the full job list with state badges; priority is a natural next dimension
- No context-switch to browser or CLI for a simple numeric change
References
bk job reprioritize in buildkite/cli
- Buildkite REST API:
PUT /v2/organizations/{org}/pipelines/{pipe}/builds/{build}/jobs/{job}
Acceptance
Problem
The Buildkite CLI can reprioritize jobs (
bk job reprioritize), but builddeck offers no way to change job priority from the TUI. When a critical build's job is stuck behind lower-priority work, users must drop to the CLI or browser to fix the ordering.Proposed Feature
Add a job reprioritization action in the build detail pane (steps list). When a step is highlighted, pressing a key (e.g.
porctrl+p) opens a small inline prompt to set a new priority value.UX
The prompt should appear in the status bar area (non-modal, keeping context visible):
Why this fits a TUI
References
bk job reprioritizein buildkite/cliPUT /v2/organizations/{org}/pipelines/{pipe}/builds/{build}/jobs/{job}Acceptance
pkey on a highlighted step triggers reprioritization prompt