Using Autoticket with agents
New work items Autoticket creates are agent-ready: a coding agent assigned to the ticket, or a Rovo/Atlassian MCP client, can read structured context with no human in the loop. This page describes what's on the ticket today and how to use it — it does not describe an Autoticket-hosted MCP server or a Rovo agent module; those are not part of this release. To check this on a real ticket, see step 5 of the evaluation guide.
The Agent brief
Every new work item's description starts with an Agent brief section, ahead of the existing Sentry details: a one-line problem statement, environment, release, first/last seen (when Sentry's issue payload includes them), event and user counts, up to about eight in-app stack frames with file and line, and a few repro hints pulled from breadcrumbs and tags already on the fetched event. Anything Autoticket doesn't have is labeled "not provided" rather than guessed. The existing Sentry section, optional AI summary, and stack trace excerpt still follow it unchanged.
The sentry_bridge issue property
The same facts are also written to a versioned issue property named sentry_bridge
(schema: 1), so an agent can read structured JSON instead of parsing ADF text. It carries the
fields the app already stored (sentryIssueId, dedupeKey, organizationSlug,
shortId, webUrl, status) plus the brief's fields: problem,
environment, release, firstSeen, lastSeen,
eventCount, userCount, inAppFrames (an array of
{file, line, function}), reproHints, and agentReady. Fields with no
data are null rather than invented. The property is refreshed on every status sync; it does not
rewrite the description of an already-created ticket.
Reading the property from an agent
Any Jira-side agent or MCP client reads sentry_bridge with Jira's own platform tool,
getJiraEntityProperty — the same tool Claude Agent for Jira, Cursor, GitHub Copilot for
Jira, and Rovo already expose when they're connected to your Jira site. Autoticket does not ship its own
MCP server or tool for this; it writes a standard issue property that the platform's existing tool already
knows how to read. No extra setup is required beyond however you've connected that agent or MCP client to
Jira.
The agent-ready pickup label
Autoticket adds a label (agent-ready by default) to a new work item when all three are true:
- the event has at least one in-app stack frame (library-only frames don't count),
- the event has a non-empty release, and
- the event's Sentry level is at or above the project's configured minimum (error by default) — an event with no recognized level never qualifies.
Use this label as a saved filter or automation trigger so an agent (or a human) can pick up only the tickets that are actually ready to work, instead of every new ticket. If you've set an agent assignee accountId in that project's Autoticket settings, a qualifying ticket is also assigned to that account — paste the accountId of your site's Claude / Cursor / Copilot agent user, the same way you'd assign any other Jira user. The field is a plain text accountId, not a user picker, so configuring it doesn't need any extra Jira permission.
Changing or turning off the label
Both settings live in the project's Autoticket settings, next to Labels. Clear the pickup label field and save to stop adding it entirely — existing labeled tickets are unaffected, and no new ones get it. Type a different label to rename it going forward (Jira-safe characters only; spaces become hyphens). Raise or lower Agent-ready minimum level to change the severity bar, or choose "Any level" to drop the severity check while still requiring an in-app frame and a release. A project that has never touched these settings still gets the agent-ready default label at the error minimum — no re-save needed.
A note on user counts
The brief and the property only show userCount when Sentry actually sent one. Issue
webhooks (ordinary new/resolved/regressed Sentry issues) usually include it; event_alert and
metric_alert notifications generally don't carry a user count at all, so those tickets omit the
field rather than showing a misleading zero.