Workflow

How to Mark a Ticket as Spam

Verified with a disposable ticket. A new ticket was created with outbound email disabled, selected through the same payload shape used by the list action, marked as spam, checked on the detail page, and then trashed.

Evidence Summary

Workflow run
ticket-spam-20260519T135411Z
Support check
ticket-spam-support-check-20260519T135411Z
Ticket id
187
Ticket number
SUP-2605-82913
Final state
Spam action accepted; disposable ticket marked as trash after verification.

Ticket spam workflow diagram

Use the List Action

  1. Open Tickets then Tickets.
  2. Select one or more ticket rows.
  3. Click Spam.
  4. Confirm the prompt.

The verified endpoint was tickets / SPAM_tickets, posted as list[]=187. The response returned {"success":true}.

Observed Result

After the spam action, ticket 187 still opened normally on the detail page and was not automatically marked as trash. The visible detail state remained subject AI Demo Ticket Spam 20260519T135411Z, status Aberto, owner Demo, department Suporte Tickets, topic Baixa, and priority Normal.

The SPAM support-file page at /tickets/apoio/spam was checked after the action. It showed No data available in table, so this controlled ticket with source other did not add the fake recipient aiticket@example.invalid to the SPAM support file.

Artifacts