Jira

Real statuses and real transitions, over OAuth.

Jira connects over OAuth: Connect Jira, approve the scopes, done. One connection per organization, to one Jira Cloud site — the connected site's name shows in the settings header, and reconnecting switches sites.

• What you connect: a Jira project, with its key as a badge on each row. The whole project syncs in — for a decade-old 10,000-issue project, expect the first sync to take a moment.
• Real statuses, real transitions. The project's workflow statuses are the task's, and Peractor's outbound writes use Jira's own transitions, so your workflow rules and automations still apply.
• Field sync: title, description, status, priority, assignee, labels — by poll, about every 30 seconds. A standard OAuth grant cannot register webhooks, so polling is the transport.
• Artifacts render inline — published images attach to the issue and appear in the comment.

Attachments on Jira issues, including inline images in the description, reach the agent like every tracker's do.