Connect Atlassian from /connections/atlassian when you want Jira-backed context in aura. This guide shows you which values the app asks for, how to save them correctly, and what to expect after the connection test runs.
What you need before you start
The Atlassian connector is not an OAuth sign-in flow. The app asks for three values on the connector page:
- an Atlassian API token
- your Atlassian Cloud ID
- your Atlassian user name, which is the email you use to sign in
Have all three ready before you open the settings form.
Create an API token
The app points users to Atlassian’s API token page.
Use this path:
- Open Atlassian API Tokens .
- Click Create API token.
- Give the token a label such as
Aura Integration. - Set the expiry far enough out to avoid frequent reconnect work.
- Copy the token as soon as it is created.
You will paste that value into the Atlassian connector form in aura.
Find your Cloud ID and user name
The Atlassian page in the app expects:
Cloud ID: your Atlassian Cloud site identifierUser Name: the email address you use to log in to Atlassian
The UI already links users to Atlassian’s support article for retrieving the Cloud ID. Use that source if you do not already have it.
Connect Atlassian
Once you have the three required values:
- Open the Atlassian card from Connections.
- Open the settings form.
- Paste the API token.
- Enter the Cloud ID.
- Enter your Atlassian user name or email.
- Click Connect Atlassian.
The app stores the integration and then runs an MCP test. That test result is part of the expected setup outcome.
Verify the connection
After saving, look for both of these outcomes:
- the Atlassian card on Connections moves to
Ready - the page reports that the Atlassian MCP test passed
If the credentials save but the MCP test fails, treat the setup as incomplete and correct the token, Cloud ID, or user name before relying on the connector.
Update credentials later
If the connector already exists, the page switches from a connect form to an update flow.
Use that flow when:
- your API token changed
- your Cloud ID was entered incorrectly
- your Atlassian login email changed
After updating, the app runs the MCP test again. Confirm it passes before you treat the connector as healthy.
Use Atlassian after setup
Once the connector is ready, return to Home when you want Jira context inside chat, or use Search when you want direct lookup across connected sources.
This is the right connector for:
- issue lookup and status questions
- blocker and priority checks
- creating or updating Jira issues from aura
Good to know
The product copy still mentions Confluence in places, but the practical setup path here is Jira-first. This page documents the current Atlassian connection flow that users can complete today.