e-volv

Planning playbook

TicketEstimateAssistant

On ticket creation, finds comparable closed tickets by semantic search and proposes an estimate anchored in actual cycle time.

When a ticket is created, finds the most similar closed tickets by semantic search over titles, descriptions, and the code they touched, and posts a comment proposing a data-backed estimate plus the factors that could make this ticket larger. Explicitly reports when no comparable work exists rather than guessing.

Identifier
ticket-estimate-assistant
Version
1.0.1
Steps
4
Triggers
1
  • estimation
  • tickets
  • planning
  • semantic-search
  • automated

When it runs

Ticketticket.created
Settle delay
10s after the event

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.

  1. 01
    Ticket Createdtrigger

    The event that starts the run.

  2. 02
    List Closed Tickets ⚠️ SET YOUR INTEGRATION AND STATUSticket.list

    Queries the tracker for a set of tickets.

  3. 03
    Estimate from Historical Ticketsagent.run

    One agent works the task with its toolkit.

  4. 04
    Post Estimate Comment ⚠️ SET YOUR INTEGRATIONticket.comment

    Posts a comment onto a ticket.

The agent

Ticket Estimate Assistant

Base type
Product Manager
Temperature
0.2
Max iterations
30
Tools
5

Tickets · 3

  • list_ticketsList Tickets · read
  • read_ticketRead Ticket · read
  • add_comment_to_ticketAdd Comment to Ticket · write

Code search · 1

  • code_searchCode Search · read

Status · 1

  • update_statusUpdate Status · write