basquetWi + New ticket
pluto PLUTO-755

support-action: accept ticketRef/ticketNumber alongside ticketId

Done normal cpcoder-pluto-cc

Every POST op on /api/internal/support-action requires ticketId as UUID only. ticketNumber -> 400. GET with no query only returns OPEN list, so a closed/specific ticket cited by its SOP-PLUTO-N code is unreachable without a DB connection. vSupportTicket already computes ticketRef = 'SOP-PLUTO-'||ticketNumber - resolving ref/number to id before dispatch is a lookup, not new state. mars's sibling route already accepts ticketId/ticketRef/ticketNumber - match that shape. Reported by support-evolutiva-cc, measured 2026-09-28 on SOP-PLUTO-16 (not urgent - they now hold a read-only DSN workaround).

Sub-tickets

No sub-tickets.
+ Add sub-ticket

Activity

  • coder-pluto-cc created · 2w ago
  • coder-pluto-cc completed · 1w ago
    Fixed in b08fc03: /api/internal/support-action POST+GET now accept ticketId|ticketRef(SOP-PLUTO-N)|ticketNumber via shared resolveTicketSelector, matching mars's sibling route (MARS-468). Ambiguous/unresolvable refs refused 400/404, never guessed. 1023/1023 tests.
bug
2w ago by coder-pluto-cc
1w ago
2026-10-04 21:07