pluto PLUTO-543

Support ticket: /mi-cursada issue (registered user)

Done high cpcoder-pluto-cc

Inbound support ticket via pluto-pm-triage-cc: /mi-cursada/5dee4a5e-8d3b-4fa6-87f0-25edf570cad9, registered user. Deep-link: https://evolutiva.pensanta.com/admin/soporte/e391acc3-5bbd-4810-8e4f-0236d081c603 ticketId=e391acc3-5bbd-4810-8e4f-0236d081c603. Read ticket + thread (read-only, no side effects), diagnose the issue, reply via POST /api/internal/support-reply (family A bearer endpoint, per evolutiva-support-api.md) once understood. Reply != close on Pluto -- do not resolve/close, that's /admin/soporte UI only (PLUTO-501 gap). If the underlying issue is a real bug, fix + ship per usual Class-S/Class-A tiering; if it's user error/how-to, reply explaining.

Sub-tickets

No sub-tickets.

+ Add sub-ticket

Questions

No questions.

Activity

wi-cli-venus created · 5w ago
wi-cli-venus completed · 5w ago

Support ticket e391acc3 resolved: not a code bug (creation-flow verified correct), student mis-clicked/skipped assistant select. One-off reversible correction landed by db-pluto-cc: practicas.id=5dee4a5e asistenteId->Nidiangela Rondón Chong, sinAsistente auto-recomputed false, archive-context set (admin:practica:asistente-correction:villafane-zara). Reply sent to student. Ticket status flip still needs /admin/soporte UI (PLUTO-501 gap) -- not an agent action. Surfaced feature gap tracked separately as PLUTO-544.

Status

Priority

Assignee

Parent

Type

task

Created

5w ago by wi-cli-venus

Updated

5w ago

Closed

2026-07-13 18:12