Connect to Atlassian Cloud

Connecting an Atlassian Cloud site lets Colloquial read your Jira Assets object types and map them to Fact Card catalogues, so the two stay in step. The same connection is what Publish to Confluence uses.

One connection covers both. You authorise Colloquial once, against a site, and Colloquial checks what that site will actually let it do.

Before you start

You need to be a Colloquial admin — the integration settings are only visible to admins.
You need an Atlassian account that can grant app access to the site you are connecting.
Object type mapping needs Jira Assets, which is part of Jira Service Management Premium. Confluence publishing does not.

Step 1 — Connect your Atlassian site

Go to Settings → Integrations → Atlassian Cloud. On the Setup tab, choose Connect to Atlassian and sign in to Atlassian when prompted. Atlassian asks you to approve the permissions Colloquial needs, then sends you back.

The connected site appears under Connected Atlassian Clouds.

The Setup tab of Atlassian Cloud settings, showing a connected site named Acme Cloud with its domain, and the Manage instance, Refresh access and Disconnect buttons.

The Setup tab, with one connected site. Connect to Atlassian adds another.

You can connect more than one site. Each gets its own card here and its own object type mappings.

Step 2 — Check Assets access

Choose Manage instance on the site's card to open Update Atlassian Cloud. This screen tells you what the connection can do, and it leads with Assets access.

Colloquial can't work Assets access out from the connection alone — an unlicensed site answers the first few questions quite happily and only refuses when real work starts. So there is a Re-check access button that asks Atlassian directly, and reports one of four answers.

Assets is available

Everything Colloquial needs is in place. Object types appear further down the page, ready to map.

The Update Atlassian Cloud screen with a green Assets is available on this site bar under the Assets access heading.

A site with Assets available. Carry on to Step 3.

Assets access is unavailable

Atlassian refused. This is a licensing answer, not a fault: Assets needs a Jira Service Management Premium plan, and the account you connected with needs a Jira Service Management agent seat. Check both in Atlassian admin, then choose Re-check access.

Object type mappings are hidden while a site is in this state, because none of them could run.

The Update Atlassian Cloud screen with an amber Assets access is unavailable bar explaining that Assets requires a Jira Service Management Premium plan and an agent seat.

Assets refused. The bar names both things to check.

Refresh access to use Assets

The connection is missing a permission that the Assets API needs — usually because it was authorised before Colloquial started asking for it. Go back to the Setup tab and choose Refresh access on the site's card to re-approve the connection, then re-check.

The Update Atlassian Cloud screen with an amber Refresh access to use Assets bar explaining that the connection is missing a permission required by the Assets API.

A missing permission. Refresh access on the Setup tab re-approves the connection.

Could not check Assets access

Colloquial couldn't reach Atlassian to ask. This one is usually temporary and usually ours, not yours — wait a moment and choose Re-check access. If it persists, send us the site's domain.

The Update Atlassian Cloud screen with a red Could not check Assets access bar explaining that the Assets API could not be reached and to try again.

A failed check. Unlike the two amber states, there is nothing to fix in Atlassian.

Not checked yet

Sites connected before this check existed show Assets access has not been checked for this site. until you choose Re-check access. Their existing object type mappings keep working in the meantime.

The Update Atlassian Cloud screen showing the line Assets access has not been checked for this site under the Assets access heading.

An unchecked site. Nothing is wrong — nobody has asked yet.

Step 3 — Map object types to Fact Cards

When Assets is available, Available Object Types lists what Colloquial found, grouped by Assets schema, with a count per schema.

Expand an object type to map it to a Fact Card catalogue. Each mapping tells Colloquial which catalogue an object type corresponds to, and mappings are what the Object Mappings tabs on the settings page are built from.

Choose Save when you're done. A confirmation appears at the top of the card.

The Update Atlassian Cloud screen with a green Atlassian integration updated bar at the top of the card, above the Assets access section and Available Object Types list.

Saved. Atlassian integration updated confirms the mappings were stored.

If you start editing and haven't saved, a Changes are not yet saved marker appears in the same place. It clears when you save.

Manage a connected site

Each card on the Setup tab has three actions:

Manage instance — opens Update Atlassian Cloud, where Assets access and object type mappings live.
Refresh access — re-approves the connection with Atlassian. Use it when a connection has expired, or when a bar asks you to.
Disconnect — removes the connection.

Troubleshooting

The Assets access bar is amber

Amber means something in Atlassian needs changing, and the bar says what: Assets access is unavailable is licensing, Refresh access to use Assets is permissions. Both clear once you fix them and choose Re-check access.

The Assets access bar is red

Red means a check Colloquial couldn't complete, rather than something you've configured. Try Re-check access in a moment.

No object types are listed

Check, in this order:

Does Assets access say Assets is available? Object types are hidden when access was refused.
Has the site been checked at all? Choose Re-check access.
Does the connected Atlassian account have permission to see the schemas you expect? Colloquial only sees what that account sees.

Object types are out of date

The list carries a Last updated time. It refreshes when Colloquial next reads from Atlassian — mapping changes made in Assets show up after that.