Atlassian (Rovo)
Connect with JIRA, JSM and other Atlassian products
Work with Jira, Jira Service Management (JSM) and other Atlassian apps directly from tickets
The Atlassian connector links Suptask to your Atlassian Cloud site through Atlassian Rovo. Once connected, the AI Assistant on an Inbox can search and read Jira work items and other Atlassian products - and, depending on the tools you enable, create Jira work items, comment, change status or write documentation directly from a ticket in Slack.
The connector uses Atlassian's official Rovo MCP server. There is no app registration and no API token to create: you click Authorize, sign in to Atlassian, and approve access.
What you can use it for
Escalate to engineering — turn a ticket into a Jira work item with the right project, type and fields, without leaving Slack.
Check the status of a bug — an agent asks whether a reported issue is already known, who owns it, or when it ships.
Answer from your documentation — the Assistant searches Confluence and replies to the requester or the agent.
Keep teams in sync — add comments to Jira work items or move them to a new status as the ticket progresses.
Capture new knowledge — draft a Confluence page from a resolved ticket.
Search across Atlassian — find related work items, pages and people with one natural-language search.
Supported Atlassian apps
Jira
Search with JQL, read work items and comments, create and edit work items, comment, transition, link, log time
Jira Service Management
Requests are Jira work items, so they're read and updated with the Jira tools
Confluence
Search with CQL, read pages, create and update pages, comment, add labels
Rovo search
Search across Jira, Confluence and connected apps using natural language
Other Atlassian apps
Bitbucket, Loom, Goals, Projects and Teams, when they're part of your Atlassian organization
Before you begin
You'll need:
An admin role in Suptask.
An Atlassian Cloud site. Server and Data Center are not supported.
An Atlassian user with the permissions you want the Assistant to have. The connector acts as the user who authorizes it - see How permissions work.
The Inbox you want to connect Atlassian to.
What you'll do:
Check that your Atlassian organization allows the connection
Add the Atlassian connector on your Inbox and authorize with OAuth
Choose which tools your Assistant may use
Step 1: Check your Atlassian organization settings
Atlassian organization admins control which AI tools can connect to Rovo. Ask your Atlassian admin to confirm the following in Atlassian Administration:
Rovo MCP server access is allowed for your organization.
Suptask's domain is allowed under the Rovo MCP server Domains settings.
IP allowlisting (if you use it) includes Suptask's outbound IP addresses.
Step 2: Connect Atlassian in Suptask
In the Suptask Web App, go to Intelligence and select the Inbox you want to connect Atlassian to.
Open Connectors and add the Atlassian connector.
Click Authorize.
An Atlassian sign-in window opens. Sign in with the account you want the Assistant to act as, select your site, and approve access.
When it's done, the connector status changes to Connected.
Step 3: Choose which tools your Assistant may use
The connector provides a set of tools to the AI Assistant. Each tool can be set individually, so you can let the Assistant read Jira and Confluence without allowing it to change anything.
Each tool can be set to:
Auto — the Assistant uses the tool on its own when it's relevant.
Ask — the Assistant prepares the action and pauses for an agent to approve before it runs.
Off — the Assistant can't use the tool at all.
Delete and project-management tools are disabled by default in Atlassian. They only work if your Atlassian admin has enabled them for the organization.
How permissions work
Three layers decide what the Assistant can do. Each one narrows the layer above it.
The Atlassian user — the connector inherits the permissions of the user who authorized it. It only sees the projects, spaces and pages that user can see.
Your Atlassian organization settings — admins can turn tool groups (read, write, search, delete) on or off for all AI tools connecting to Rovo.
The Assistant's tools in Suptask — you choose Off, Ask or Auto per tool.
Tool settings in Suptask can restrict what the Assistant does, never expand it.
Authorize with an account that has the right scope — no more. If you authorize with a Jira or Confluence administrator, every tool set to Auto runs with administrator rights.
Use different Atlassian access per Inbox
Each Inbox in Suptask has its own connector, so different teams can work against Atlassian in different ways:
IT Helpdesk Inbox — read the IT Confluence space, create Jira work items on Ask.
Customer Support Inbox — search known bugs in Jira, comment on work items on Ask.
HR Inbox — read HR policy pages in Confluence only.
A ticket in one Inbox only reaches the tools enabled on that Inbox's connector. To separate access fully, authorize each Inbox with a different Atlassian user.
How to use the integration
The connector is used by the AI Assistants you set up in Suptask. Agents work with it in Slack, from inside the ticket.
Examples of what an agent can ask in a ticket thread:
When a tool is set to Ask, the Assistant posts the prepared action in the ticket and waits for an agent to approve it before running.
AI AssistantsRovo credits
Some tools consume Rovo credits from your Atlassian organization's shared credit pool — the same pool used by Rovo Chat, Studio and Agents. This mainly applies to Rovo search and cross-app context lookups, which can use up to 10 credits per call.
If your organization's credits run low, set the Rovo search tool to Ask or Off and rely on the Jira and Confluence search tools instead.
How this compares to other Atlassian integrations
Suptask offers other ways to work with Atlassian. Use the one that fits your workflow:
Atlassian (Rovo) — this article
AI Assistant working across Jira, Confluence and more, set up with OAuth
Atlassian Confluence
Confluence-only knowledge, authenticated with a scoped API token
Auditing and revoking access
Actions the Assistant takes in Jira or Confluence appear in each app's history under the account that authorized the connector. Atlassian organization admins can also monitor Rovo MCP activity in the Atlassian audit log.
To revoke access, the authorizing user can remove Suptask from Connected apps in their Atlassian account settings. The connector stops working until it's authorized again.
Troubleshooting
Sign-in works, but every tool call fails — your Atlassian organization is blocking the connection. Ask your Atlassian admin to check Rovo MCP access, the allowed domains and IP allowlisting.
"You don't have permission to connect from this IP address" — IP allowlisting is enabled in Atlassian. Your admin needs to allow Suptask's IP addresses.
The Assistant can't find a work item or page — the authorizing user doesn't have access to that project, space or page, or it belongs to another Atlassian site.
The Assistant can read but won't create or update — the write tool is set to Off, or it's set to Ask and waiting for an agent to approve. Check the tool settings on the Assistant.
Atlassian denies an action the tool allows — the authorizing user lacks that permission in Jira or Confluence, or the tool group is disabled in your Atlassian organization settings.
Jira work item creation fails on required fields — the project requires fields the request didn't include. Ask the Assistant to include them, or name the work item type and project in your request.
Rovo search stops returning results — your organization may be out of Rovo credits.
It worked before and stopped — the connection was revoked, or the authorizing account was deactivated. Reconnect the connector.
Need help?
Reach out to Suptask Support and our team will help you connect Atlassian.
Last updated
Was this helpful?