Outcome. Every time a ticket's priority changes, a note logs automatically to the ticket's timeline with the new priority and a timestamp, giving support leads a visible trail without opening property history.
flowchart TD
A[Ticket Priority changes] --> B[Create note on ticket timeline with new priority]
B --> C[Set last_priority_change_logged_at = now]

When to use it, when not to
- UseUse it for lightweight, visible tracking of priority escalations and de-escalations on tickets that matter for SLA or leadership visibility.
- UseUse it when support leads read ticket timelines directly and want inline change visibility rather than checking property history per ticket.
- SkipDo not expect a true before/after log from this pattern alone. Native workflow tokens expose only the CURRENT, post-change value; for a "changed from X to Y" note, add the snapshot-property technique described in reporting-alerts-035.
- SkipDo not apply this to every ticket property. Priority is a high-signal field; logging every property change creates timeline noise nobody reads.
or the reporting and alerts pack, 39 EUR
One-time, excl. VAT. 30-day refund, no questions asked. Founding prices until 31 October, then 199 and 59 EUR. Includes every spec added later, up to the full 500, and the one-click installer on the full library. Building on client portals? The agency licence at 449 EUR covers unlimited client portals.





