The current UI is a minimal status table. Arr-style tools expose a clear queue page with states, reasons, and safe actions.
Proposed change
Create a richer Jobs/Queue UI.
Scope
Group jobs by SAB processing, ready, importing, failed, ignored category, manual batch, and completed.
Show one row per video file with release/folder context.
Display readiness reason and SAB status/category.
Add safe actions: retry, ignore, remove from Importarr queue, and run now when allowed.
Confirm destructive actions.
Acceptance criteria
Users can understand why each file is or is not ready.
Failed jobs are actionable from the UI.
Manual batch files show full relative path context.
Write actions require auth when configured.
## Problem
The current UI is a minimal status table. Arr-style tools expose a clear queue page with states, reasons, and safe actions.
## Proposed change
Create a richer Jobs/Queue UI.
## Scope
- Group jobs by SAB processing, ready, importing, failed, ignored category, manual batch, and completed.
- Show one row per video file with release/folder context.
- Display readiness reason and SAB status/category.
- Add safe actions: retry, ignore, remove from Importarr queue, and run now when allowed.
- Confirm destructive actions.
## Acceptance criteria
- Users can understand why each file is or is not ready.
- Failed jobs are actionable from the UI.
- Manual batch files show full relative path context.
- Write actions require auth when configured.
Implemented the full Jobs and Queue UI for issue #8.
What changed
Added richer /api/jobs payloads with queue groups, one row per queue item/video file, SAB category/status, readiness reason, timestamps, batch/job IDs, and action capability flags.
Added write-auth protected queue item actions for retry, ignore, and remove from Importarr queue.
Reworked the web UI to group jobs by SAB processing, ready, importing, failed, ignored category, manual batch, and completed.
Expanded rows to show release/folder context, full manual batch relative paths, readiness reasons, SAB details, and safe action buttons.
Added confirmation prompts for destructive actions and current-job cancellation.
Added queue action and manual path context test coverage.
## Implementation summary
Implemented the full Jobs and Queue UI for issue #8.
## What changed
- Added richer `/api/jobs` payloads with queue groups, one row per queue item/video file, SAB category/status, readiness reason, timestamps, batch/job IDs, and action capability flags.
- Added write-auth protected queue item actions for retry, ignore, and remove from Importarr queue.
- Reworked the web UI to group jobs by SAB processing, ready, importing, failed, ignored category, manual batch, and completed.
- Expanded rows to show release/folder context, full manual batch relative paths, readiness reasons, SAB details, and safe action buttons.
- Added confirmation prompts for destructive actions and current-job cancellation.
- Added queue action and manual path context test coverage.
## Verification
- `.venv/bin/python -m pytest -q` — 22 passed
## Commit
- `1cafe2b` on `main`
## Result
Issue #8 is implemented and verified.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Problem
The current UI is a minimal status table. Arr-style tools expose a clear queue page with states, reasons, and safe actions.
Proposed change
Create a richer Jobs/Queue UI.
Scope
Acceptance criteria
Implementation summary
Implemented the full Jobs and Queue UI for issue #8.
What changed
/api/jobspayloads with queue groups, one row per queue item/video file, SAB category/status, readiness reason, timestamps, batch/job IDs, and action capability flags.Verification
.venv/bin/python -m pytest -q— 22 passedCommit
1cafe2bonmainResult
Issue #8 is implemented and verified.