Chore/wire ops queue view to domain queue builder#88
Merged
Conversation
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR wires the Ops queue page to the shared domain queue builder and updates docs/UI to reflect the current project state and roadmap.
What changed
policylens/apps/ops/views.pyto usebuild_queue_queryset(...)for queue ordering/filtering parity with the API.statuspriorityslaqueue_rankfor stable ranked display in the UI.claim_detail_view(...)scaffold with optimised related loading (select_related/prefetch_related) for upcoming detail page work.policylens/apps/ops/templates/ops/queue.html:ops:claim-detailREADME.mdto clearly separate Implemented vs Planned work with explicit milestone/date labels and corrected current-state setup details.Why
Notes / follow-ups
ops:claim-detailis referenced in the queue template andclaim_detail_viewexists, but URL wiring/template completion is follow-up work if not included in this PR.ruff, Docker daemon unavailable).