superbot in Jira

Assign an issue to superbot, or mention it in a comment.
You get one comment back with the pull request linked.

What it does

Starts a cloud run when an issue is assigned to the Superbot user or a comment says @superbot.
Comments the result on the issue with the pull request linked. A person merges it.
Attaches a file or a link to an issue when your agent is asked to.
Starts a routine on a Jira event. It is saved as a draft that you turn on.

A Jira site admin sets superbot up on the site once: a Jira user for superbot and a webhook.
Link the superbot desktop or phone app to your account once. That makes the Recovery key Jira needs.
Connect Jira while signed in to superbot. Approve on Atlassian's screen.
Assign an issue to the Superbot user, or write @superbot in a comment.

in an issue comment

@superbot [repo=my-app] fix the flaky login test

ask your agent

Attach the screenshot to PROJ-123.

ask your agent

When a Jira issue is created in PROJ, run a routine that drafts a first reply.

The first is typed in Jira. The other two go to your agent anywhere you use it.

Status: Live with OAuth. Not in the Atlassian Marketplace yet.
Needs: A connected Jira account, on a superbot account that holds a Recovery key. A Jira site admin installs superbot on the site once.
Permissions: Read and write on Jira issues, and who you are on Atlassian. Atlassian shows a warning on its consent screen for an app it has not reviewed yet.
Runs: A run is cloud-only and lands as a pull request a person merges.
Webhook: A site admin registers it with Issue updated and Comment created ticked.

Status as of 2026-10-19.