e-volv

Planning playbook

BlockedTicketEscalator

Tracks tickets that move to a blocked status and escalates with status updates at 3 days and to the board owner at 7 days.

Fires when a ticket moves to a blocked status. Records what it is blocked on from the ticket and its comments, then tracks it: at 3 days it comments asking for a status update, at 7 it escalates to the reporter and the board owner with a summary of how long it has been blocked and what has changed since, and it identifies whether the blocker is itself a ticket that is also stalled. Cancels cleanly when the ticket unblocks.

Identifier
blocked-ticket-escalator
Version
1.0.0
Steps
5
Triggers
1
  • tickets
  • blocked
  • escalation
  • tracking
  • automated
  • status

When it runs

Ticketticket.status_changed

Only when all hold

  • ticket.status equals Blocked

The pipeline

The graph below is the one the workflow opens with in the builder — same steps, same layout, drawn on the same canvas. The run playing through it is a simulation; the branches and conditions are real.

React Flow
  1. 01
    Ticket Blockedtrigger

    The event that starts the run.

  2. 02
    Read Blocked Ticketticket.read

    Loads one ticket into the run context.

  3. 03
    Assess Blocked Ticketagent.run

    One agent works the task with its toolkit.

  4. 04
    Post Escalation Commentticket.comment

    Posts a comment onto a ticket.

  5. 05
    Mark as Trackedticket.update

    Moves status or fields on an existing ticket.

The agent

Blocked Ticket Escalator

Base type
Product Manager
Temperature
0.2
Max iterations
25
Tools
6

Tickets · 5

  • read_ticketRead Ticket · read
  • read_ticket_commentsRead Ticket Comments · read
  • list_ticketsList Tickets · read
  • add_comment_to_ticketAdd Comment to Ticket · write
  • update_ticketUpdate Ticket · write

Status · 1

  • update_statusUpdate Status · write