Jira

OAuth connection to one Jira Cloud site; projects import with their real workflow statuses.

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.

• Import unit: a Jira project (key badge on each row). The whole project imports — 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 columns, 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 can't 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, staged into .peractor/attachment/ at run start.