Atlassian

The Atlassian integration connects both Jira and Confluence. Jira issues trigger implementation work; Confluence pages can trigger agents on page and comment activity.

​

Jira

​

Features

• Add the Tembo label to trigger implementation
• Use tembo/{repo-name} labels to target specific repositories
• Status updates and PR links posted as comments

​

Installation

​

Service account

A service account is a non-human Atlassian account that exists only for Tembo. Once connected, Tembo uses it to work on Jira issues and post comments. The OAuth connection from installation stays in place and is still required.

​

Prerequisites

• The Atlassian integration is installed through OAuth (see Installation)
• Permission to manage integrations in your Tembo organization
• Access to Atlassian Administration for the organization that owns your Jira site

​

Set up a Tembo service account

When you connect, Tembo checks the credentials before saving them. The credential must:

• Exchange successfully for an access token
• Include all four required scopes
• Belong to an active Jira user
• Have access to at least one project on the connected site

If any check fails, nothing is saved. When it succeeds, the settings page shows Connected as followed by the service account’s display name. Tembo stores the client secret as an integration credential and never returns it in the settings page or API responses.

​

Which identity Tembo uses

If the service account can’t get a token or is refused access, the Jira action fails. Tembo never falls back to the OAuth user for that action.

​

Agent tools in bot mode

With a service account connected, agents can use only these core Jira tools:

• Read: search, get issue, list projects, list project issues, get worklogs, get transitions, search fields, list issue link types, get user profile, list project versions, list project components
• Write: create issue, batch create issues, update issue, add comment, transition issue, add worklog, create issue link, remove issue link

Board, sprint, and administration tools are unavailable in bot mode. Confluence tools keep working through the OAuth connection. New agent sessions start using the service account immediately. Existing sessions pick up the change the next time their credentials refresh.

​

Mentions and comments

Once a service account is connected, Tembo treats the service account as its own Jira user:

• Tembo ignores comments written by the service account, so it doesn’t respond to its own comments.
• @-mentioning the service account triggers Tembo only if the account’s display name contains Tembo. Writing @tembo or /tembo in a comment still works whatever the account is named.

If Jira refuses to let Tembo edit a status comment it posted earlier, for example one posted before you connected the service account, Tembo posts the completion update as a new comment.

​

Replace or disconnect

• Replace credentials runs the same checks on the new Client ID and Client Secret, then swaps them in.
• Disconnect service account deletes the stored service account credentials. Jira actions and comments go back to the OAuth user. The Atlassian integration and its webhooks stay connected.

Reconnecting through OAuth keeps an existing service account. If the reconnect would switch to a different Jira site than the service account belongs to, Tembo rejects it and leaves your existing integration settings unchanged.

​

Limitations

• A service account can’t replace the OAuth installation. Webhooks and the other features that use the OAuth connection still need it.
• Jira and Confluence must use the same Atlassian site. If your integration uses Confluence on a different site from Jira, you can’t connect a service account.

​

Usage

Add the Tembo label to any issue. Tembo reads the description, creates a coding session, and opens a PR. If you add a tembo/{repo-name} label, that also triggers Tembo and routes the task to the selected repository.

​

Target a specific repository

Add a label in the format tembo/{repo-name} (for example, tembo/monorepo). This label also triggers processing on its own, so you do not need a separate Tembo label.

• {repo-name} must match the repository name as it appears in Tembo (the name field on the connected repository).
• The tembo/ prefix is case-sensitive: use lowercase tembo/.
• Valid characters in {repo-name} are letters, numbers, _, ., and -.

When multiple tembo/{repo-name} labels are present, Tembo uses the first one that matches a connected, enabled repository.

​

Fallback behavior

If no tembo/{repo-name} label matches a connected, enabled repository, Tembo falls back in this order:

1. The default repository configured for your Jira integration in Tembo
2. The first available enabled repository in your Tembo organization

​

Agents

See Agents for available Jira event triggers.

​

Advanced

​

Confluence

Confluence page and comment activity can trigger agents once Confluence triggers are enabled on your Atlassian integration.

​

Setup

​

Triggers

See Agents for how to use these as agent triggers.

​

Filters

Each Confluence trigger supports optional filters so an automation only fires for the pages, spaces, or content you care about. Configure filters when you add the trigger to an agent. Leave a filter empty to match every event for that trigger.