Jira
Agents read and update Jira tickets, so work requested in a ticket can be planned, executed, and reported on.
5 cataloged agents connectwww.atlassian.com/software/jira
What agents do here
- 1Turn a ticket into an implementation plan or pull request
- 2Summarize ticket history and linked work
- 3Update status and fields as work moves
How they connect
- Atlassian REST API
- Atlassian Remote MCP server
- OAuth 2.0 app
Before you connect
Scope the integration user to the right projects; Jira permissions are often broader than they look.
Who connects
Connected agents (5)
Devin
Cognition · cloud-agent
Devin is Cognition's autonomous software engineer: cloud sandboxes for ticket-in / PR-out work, plus Devin Desktop and CLI on the same plan as Windsurf.
incident.io
incident.io · ops-agent
incident.io is the incident-management platform whose AI assistant drafts timelines, summarizes channels, surfaces similar past incidents, and nudges responders, inside the tool that already runs your incidents.
Rootly
Rootly · ops-agent
Rootly is the incident-response platform with AI woven through it: auto-drafted summaries, suggested next steps, retrospectives, and noise reduction on the alert stream.

Arcade
Arcade · agent-services
Arcade is auth and tools for agent builders, a managed way for agents to act on a user's behalf (email, calendar, Slack, GitHub) with scoped OAuth tokens, plus a tool-calling SDK.
Extended matrix +1
80/20 preview