A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:06:01Z by majordomus 0.29.0. Nothing on this page is read again. See it live
I2475
The issues are browsed: every issue of the plan by status, milestone, priority or text, each a link onward
Where it stands
devtask.issue- Readiness
- complete completion is recorded and every required evidence token is present
- Status
- DONE
- Can start
- not now
- Milestone
- Milestone status
- ACTIVE
- Wave
4- Waiting on
- none
- Holds back
- none
- Behind it in all
0- Evidence
2of2
Moves
plan.transitionWhat it is
- Objective
- Give majordomus ui an Issues screen (/ui/issues) that lists every issue of the plan, narrowed by the plan's own statuses as tabs and by milestone, priority and text in a GET form, each issue leading to its inspector, its milestone to the milestone's and what blocks it to that issue's.
- Why
- The owner asked on 2026-10-11 to implement every view of the UI screenshots, maximally interactive (reference 05-issues-and-prs; pack v3 M05-01 issue list and detail). /ui/work shows only the ready and the active issues; the plan holds about 280, 152 of them blocked, and nothing let a reader find one or see a slice of them.
- Now
- The UI shows two short lists of issues and one issue at a time on the PR Drain.
- Wanted
- /ui/issues paints at once from plan.issues, plan.status and plan.roadmap. Tabs are the statuses the issues hold with their counts; a GET form narrows by text (id, title, objective, slug), milestone (from the roadmap) and priority (from the issues), carrying the status tab; the pick stays picked. Each row shows the issue, its status, its milestone (a link to its inspector), its priority, what blocks it (each a link to that issue) and its evidence as a meter. A value that is no word of the plan is dropped.
- Done when
- unknown: the record declares no `completion`
- Risk
- unknown: the record declares no `risk`
Acceptance
- /ui/issues lists every issue; a status tab narrows to it
- milestone, priority and text narrow together, and the pick stays picked
- an issue, its milestone and what blocks it are links to their inspectors
- a value that is no word of the plan is dropped
- Validation
cargo test --lib ui::issuestest/run.sh 1080_the_issues_are_browsed- Evidence required
ui_issues_unit_testsui_issues_case_1080- Evidence present
ui_issues_unit_testsui_issues_case_1080
Scope
- Touches
apps/majordomus-cli/src/ui/issues.rsapps/majordomus-cli/src/ui/mod.rs.ai/repo/project/issues/I2475.yamldocs/MAJORDOMUS_UI.mdtest/cases/1080_the_issues_are_browsed.sh- Not
- unknown: the record declares no `non_scope`
- Depends on
- Priority
- p1
- Profile
- implementation
- Parallel safe
- false
- Owner
- unknown: the record declares no `owner`
The work so far
- Branches
- none
- Merged
- none
- Commits
0- Trunk
- master
- Sessions
- none
- Created
- 2026-10-11
- Updated
- 2026-10-12T11:04:42Z
- Started
- 2026-10-12T11:04:21Z
- Verified
- 2026-10-12T11:04:28Z
- Completed
- 2026-10-12T11:04:42Z
Synchronisation
- Adapter
scripts/github-sync- Repository
- unknown: the derived plan's header carries no repository
- External issue
- unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
- State there
- unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
Findings
Nothing is wrong with these records.