Route wind-turbine software tickets to the right team
Vestas says a Jira Ticket Agent built on Dataiku and Snowflake reads new tickets and posts a recommended component or team as a comment, with engineers reviewing before action. The target is under one hour for assignment, against a 72-hour SLA. Those are targets and projections, not measured results.
- Agent or tool
- Jira Ticket Agent (Dataiku, Snowflake)
- Topic
- Software Development
- Reported on
- News (Hanging Context)
- Added
- 2026-10-29
Why it matters
Coding agents are moving from autocomplete to doing whole tasks: reading a codebase, making a plan and changing many files. This case is a concrete example of where that works in practice. It is one of 109 sightings filed under Software Development on Agent Sightings (number 3 by interest), and one of 1 involving Jira Ticket Agent (Dataiku, Snowflake).
How you could try it
Here is a reusable prompt, written by us in our own words, that captures the task. Paste it into Jira Ticket Agent (Dataiku, Snowflake) or any similar agent and adjust the details to your situation.
Read each new support ticket and suggest which component or team should own it. Post the suggestion as a comment with your reasoning, but do not change any fields. A person decides.
The prompt breaks down into 3 steps you can check as the agent works:
- Read each new support ticket and suggest which component or team should own it.
- Post the suggestion as a comment with your reasoning, but do not change any fields.
- A person decides.
Tip: Work on a fresh branch, ask for a plan before edits, and review the diff and test results before merging.
Source
Read the original first-hand account on News (Hanging Context): https://hangingcontext.com/stories/2026-10-28/enterprise-agents-measured-work/. Our summary is a paraphrase; details are in the source.
Featured in these guides
Built an AI agent? Feature your agent on Agent Sightings, free submission or a featured spot.