mars
MARS-467
· child of EVO-52 SOP support-ticket API: full CRUD + private stakeholder comments + notify-list, per app Backlog
SOP support-api: stakeholder-pair-only private comments (CRUD + notify shipped)
Blocked high
cmcoder-mars-cc
⛔ Only remaining stakeholder-pair private-comment visibility is tracked by MARS-732, which is blocked on EVO-102 trusted per-agent identity, EVO-104 env provisioning, and stakeholder policy. Shared SUPPORT_API_KEY cannot enforce Elazar-plus-ticket-stakeholder reads. CRUD/notify/staff notes already shipped; do not build a second ambiguous bearer path.
Sub-item EVO-52. Delivered in 4a661f9/MARS-470: API status transitions (close/reopen), notify-list, and internal staff-only notes. Remaining requirement: implement a private comment visible only to Elazar and the ticket stakeholder agent, not the end user. Detailed access-scope tracking: MARS-732.
Activity
-
parent=#2024
-
coder-mars-cc
-
coder03-mars-ca
-
SOP support-api: stakeholder-pair-only private comments (CRUD + notify shipped)
-
was: Sub-item of EVO-52. Mars support-api needs: full ticket status transitions (incl. close/resolve) callable by PM/coder via API, a private comment type visible only to Elazar + the ticket's stakeholder agent (never the end user), and a notify-list (agent name + email) that fires notifications on ticket events. No direct DB writes or chrome-mcp driving tickets — API only.
-
BWI reconciled 2026-09-13: close/reopen, notify-list, and staff-only notes are shipped. Stakeholder-pair-only visibility remains; access-scope issue is separately tracked in MARS-732.
-
coder-mars-ca / coder
-
Only remaining stakeholder-pair private-comment visibility is tracked by MARS-732, which is blocked on EVO-102 trusted per-agent identity, EVO-104 env provisioning, and stakeholder policy. Shared SUPPORT_API_KEY cannot enforce Elazar-plus-ticket-stakeholder reads. CRUD/notify/staff notes already shipped; do not build a second ambiguous bearer path.
-
coder-mars-cc
task
2026-07-15 by wi-cli-venus
6d ago