Outcome. Every ticket carries an accurate count of how many times it has been reopened, giving the service team a reporting property to spot recurring-issue tickets instead of reading the timeline by hand.
Workflow mapEnrollment, branches and actions at a glance
flowchart TD
A[Ticket stage changes Closed to Open] --> B[Custom code: read reopen_count, add 1, write back]
B --> C{reopen_count >= 3?}
C -->|yes| D[Create review task for ticket owner]
C -->|no| E[Exit]
When to use it / when not to
- Use it when reporting needs a genuine count, not just a yes/no, of reopen events per ticket, for example to segment "reopened 3+ times" tickets for root-cause review.
- Use it as an input to a broader recidivism report or dashboard grouped by product area or ticket category.
- Do not use it if a simple yes/no "has this ticket ever been reopened" flag is enough. That version is buildable natively with no custom code; see Variants.
- Do not confuse this with SLA or escalation handling of reopened tickets. What happens operationally when a ticket reopens belongs to the tickets-sla category. This fiche only produces the reporting number.



