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
ticket.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.
- 01Ticket Created
triggerThe event that starts the run.
- 02List Closed Tickets ⚠️ SET YOUR INTEGRATION AND STATUS
ticket.listQueries the tracker for a set of tickets.
- 03Estimate from Historical Tickets
agent.runOne agent works the task with its toolkit.
- 04Post Estimate Comment ⚠️ SET YOUR INTEGRATION
ticket.commentPosts 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 · readread_ticketRead Ticket · readadd_comment_to_ticketAdd Comment to Ticket · write
Code search · 1
code_searchCode Search · read
Status · 1
update_statusUpdate Status · write
Related playbooks
Break Down Ticket
Decomposes a labeled ticket into a concrete set of proposed sub-tasks.
Generate Requirements
Turns a labeled ticket into a structured requirements document, posted as a comment.
Blocked Ticket Escalator
Tracks tickets that move to a blocked status and escalates with status updates at 3 days and to the board owner at 7 days.