Assign to an agent in Jira. Get it back priced and signed.
Jira's Agents button can hand a work item to Claude, Cursor, Copilot or its own coding agent. The button cannot say what the item will cost on each, whether the seat can take it today, or prove what came back. sleds treats the assignment as an input: the row arrives priced, gated by the policy, and returns with the band, the worth and the receipt Jira cannot produce.
Jira Coding Agent $6–16 · 55% · 2 of 5 in band — Claude Agent for Jira · Jake $4–11 · 20–55 min · 81% · 62% left Dispatch Cursor $5–14 · 68% · seat at 91% — GitHub Copilot $6–16 · 55% — Dana · a person $3–9 · owns billing · headroom Hand off
Reads
Summary, description, priority, story points if any, the assignee, the agent picked.
Planner's suggested work items, sized before anyone adds them to the space.
Assign to Claude, Cursor or Copilot and the dispatcher prices and gates it first.
Writes
Estimate and worth in fields Jira already shows.
Minutes, model and cost on merge; transitions with the numbers on them.
Which agent built it, signed, across agents Jira did not dispatch.
In Jira, in its own words.
Everything sleds writes into Jira is something Jira already knows how to show. If you leave, it keeps the rows.
Next. Jira Cloud app with the work-item panel, the Planner hook for sizing suggested items, and Rovo assignment as a dispatch input. The enterprise door.