Jira & Confluence
What your agent can do
Section titled “What your agent can do”Jira
- List projects
- Search issues with JQL and read them
- Create issues
Confluence: find pages by searching or by space, and read them.
A Jira or Confluence connection can also start a Loop when an issue or a page changes.
Connecting Jira and Confluence
Section titled “Connecting Jira and Confluence”Jira and Confluence are separate Integrations, each with its own connection. Connect each one you need:
- Go to Console → Integrations and open Jira (or Confluence)
- Click Connect Jira (or Connect Confluence), then Connect with OAuth
- Select your Atlassian site (e.g.,
yourcompany.atlassian.net) - Approve the permissions → click Accept
- Back in Auteryn, click Authorize on the new connection. This second approval lets agents use Atlassian’s Rovo MCP server
If your Atlassian admin blocks the Authorize step
Section titled “If your Atlassian admin blocks the Authorize step”Atlassian organisations control which third-party domains may use the Atlassian Rovo MCP server, the Atlassian service your agents call. Newly created organisations have this on, so the first person to try Authorize sees Atlassian’s own consent screen refuse:
Your organization admin must authorize access from this redirect URL to this site.
Nothing is wrong with your connection. Atlassian stopped the approval before it ever reached Auteryn, which is why there is no error to retry here.
The fix. An org admin adds our domain in Atlassian Administration → Rovo → Rovo MCP server → Domains → Add domain:
https://console-api.auteryn.ai/**The field takes a URL pattern: a protocol is required, and
the /** suffix is optional but recommended so the entry covers every path at
or below that domain. Auteryn shows the exact value to paste under Blocked by your admin?
next to the Authorize button, so you can send it to an admin before anyone hits
the error.
If it still refuses right after the domain is added, Atlassian’s own troubleshooting is to delete the entry and re-add it — the admin UI can show a domain that has not yet reached the enforcement service — then retry in a private browser window to clear the cached consent.
Two things worth knowing:
- This blocks Authorize, not Connect. Connecting signs in to Jira or Confluence; Authorize is a second, separate approval that lets agents use Atlassian’s Rovo MCP server. Until the domain is allowed, the connection keeps asking for Authorize.
- The Allow Atlassian supported domains toggle on that page covers AI tools Atlassian partners with. It does not cover your own domains, which is why this entry is needed even with that toggle on.
Reference: Control Atlassian Rovo MCP server settings · Domain patterns · Fix OAuth consent block
Whose account does it act as?
Section titled “Whose account does it act as?”Connecting Jira or Confluence signs in with your own account. The connection acts as you. On a team, it is shared with your team unless you choose otherwise when you connect, and you can change that from its sharing control (Who can use this connection). Or let each teammate act as themselves: on an Internal agent, turn on Acts as each user for Jira/Confluence and everyone connects their own Atlassian login.
Example tasks
Section titled “Example tasks”Jira
- “List all open bugs assigned to me in the BACKEND project”
- “Create a Jira issue: ‘Fix login timeout’, priority High, project BACKEND, assigned to john@acme.com”
- “Find all P1 issues open for more than 7 days”
Confluence
- “Find the Confluence page about our deployment process”
- “Summarize the ‘API Design Guidelines’ page in our Engineering space”
- Include the Jira project key and required fields in your agent’s instructions for issue creation workflows
- Combine with Slack: Slack alert → agent creates Jira issue → posts issue link back to Slack