Events

Every event is a final readonly class in RoundlyConsulting\Tickets\Events implementing ShouldDispatchAfterCommit: it fires only once the change committed, never for a rollback. $actor is who acted (null for the system). Every event about one ticket — 33 of the 34, all but GuestConverted — implements Contracts\TicketEvent:

interface TicketEvent
{
    public function ticket(): Ticket;   // TicketMerged: the source, the ticket merged away
    public function actor(): ?Model;    // null for the system, and always for TicketOverdue,
                                        // TicketDueSoon (the sweep) and TicketMentioned
}

Laravel’s dispatcher delivers an event to the listeners of the interfaces it implements, so one typed listener hears them all — an audit log, a webhook relay or a dashboard feed:

use Illuminate\Support\Facades\Event;
use RoundlyConsulting\Tickets\Contracts\TicketEvent;

Event::listen(TicketEvent::class, function (TicketEvent $event): void {
    AuditLog::create([
        'ticket' => $event->ticket()->reference,
        'event' => class_basename($event),          // TicketReplied, TicketAssigned, …
        'actor_type' => $event->actor()?->getMorphClass(),
        'actor_id' => $event->actor()?->getKey(),
    ]);
});

Before sending anything outward, mind the agent-only events: TicketNoteAdded, and a TicketMentioned or TicketCommentUpdated / TicketCommentDeleted about a note or a held reply, carry content no requester may see.

The events

• An internal note also reaches comments-for-laravel’s own events (CommentCreated, CommentMentioned), which fire for every comment — check meta.tickets.internal before telling anyone.
• Lifecycle’s LifecycleTransitioning / LifecycleTransitioned fire for tickets too; prefer the ticket events above.
• Tickets::fake() does not fake events — every call still runs — so Event::fake() works next to it.