You're offline — showing cached data

MC-4376

Pending tickets need explicit visible action/reason on ticket, not buried in chat
2026-06-13 08:48:47 SAST
Home Board MC-4376

Pending tickets need explicit visible action/reason on ticket, not buried in chat

User request from Telegram (/queue): When a ticket is Pending on the board (new board term = status in_review, needs_input, or waiting), the ticket itself must show a very clear...
State Done Next Action Closed Owner Luci Runtime Closed Age 16d ago
MC-4376
Ticket is done; runtime is closed. · profile claude_opus_1m_high · cwd /home/lucienne/workspace/mission-control · uptime 15d 22h · last activity 15d 17h ago

Description

MC-4376
User request from Telegram (/queue): When a ticket is Pending on the board (new board term = status in_review, needs_input, or waiting), the ticket itself must show a very clear task/call-to-action/reason. Do not require Elmar to ask Luci why it is pending or dig through chat comments. Problem examples: - If assigned to Elmar, the ticket should visibly say something like: "Approve XYZ" or "Review report: http://100.118.207.3:3001/md-view?file=reports/...". - If assigned to a controller/worker, it should visibly say the concrete blocker or active child, e.g. "Waiting for MC-4342 to finish" or "Luci review gate: verify live Home at <url>". - This CTA/reason must be first-class ticket/board UI, not buried in ticket comments/chat history. Deliverables: 1. Audit current pending-ticket rendering on Board and ticket detail: in_review, needs_input, waiting. 2. Add/derive a visible "Pending action" / "Why pending" field/strip for each pending ticket on board cards and ticket detail. 3. For Elmar-assigned pending tickets, show a human-readable imperative + artifact URL if available (review/approve/respond/etc.). Never show a generic "review required" without the artifact/action. 4. For non-human pending tickets, show concrete blocker/reviewer/dependency/active child from pending_state/failure_reason/relationships/comments fallback. 5. Add or update the transition paths so when a ticket is moved into pending states, the pending_action/pending_state is set clearly where possible. 6. Add regression tests covering: Elmar review with report link, waiting blocked_by dependency, controller umbrella active child, and needs_input question. 7. Browser smoke the live board/detail after implementation and include screenshot evidence in the ticket comment before review. Acceptance: - No pending ticket card/detail can render with only "waiting", "needs input", or "in review" and no clear visible reason/action. - Elmar-facing pending cards expose the next action + link without opening chat/comments. - Tests pass and live MC board/detail smoke passes. Expected check-in: within 60 minutes.

Activity

done
Luci is working...
Live
No activity yet
Help