Jira

Connect Jira when a workflow or an agent should work with your issues: file a bug from a support message, comment on a ticket, log work, or start a run when an issue is created or updated.

Who can connect it

An owner or admin connects Jira once for the whole organization. A member asks one of them. Every workflow and agent then acts as that Atlassian user on that Jira site. See Connecting apps.

Connect Jira

1. Open the Apps page.
2. Press Connect an app.
3. Choose Jira in the Super Connect window.
4. Sign in to Atlassian, choose the Jira site, and approve the access it asks for.
5. Finish when the window reaches Done.

A connection reaches one Jira site. On the Apps page, the Workspace column shows the site’s address. Open the row to see the site link, its Cloud ID and the scopes. To work on a second site, connect it as a second connection.

What you get

A Jira connection brings actions and events. Actions search, read, create and update issues, add comments and worklogs, link issues, and look up projects, fields and users. Events start a run when an issue is created or updated, when a comment is added, or when a version is created or released. The live list of both is in the builder: the Action node’s picker for actions, and the Event list of an App event trigger for events. An agent uses only the actions you grant it. Action steps never offer a destructive action; an agent can be granted one, and it always waits for a member’s approval.

Good to know

• An issue or comment trigger needs a project key or a JQL filter. When both are set, the JQL filter wins.
• Jira allows 5 webhooks per app, per user, per site, and each distinct project or JQL filter uses one. The Access column on the Apps page shows how many the connection’s triggers use.
• A version trigger needs a project. Jira sends version events for the whole site, and the trigger keeps only that project’s.

Reauthorize Jira

When the connection’s health reads failing or needs reauthorization, an owner or admin opens the Apps page, presses … on its row, then Reauthorize, and signs in to Atlassian again. The connection stays the same, so workflows, triggers and agent grants need no change. See Reauthorize a connection.