# Jira and Confluence

> Let your assistants read Jira issues and Confluence pages while they plan and build. Read only, through Atlassian's own hosted connector. Coming soon.

Status: Coming soon

Jira holds your tickets and Confluence holds your team's documents. Once you connect them, your assistants can read an issue or a page before they start, so the work follows what your team already wrote down.

> [!SOON]
> The Jira and Confluence integration is Coming soon. This page describes how it will work. The integrations open at launch are GitHub, GitLab, and Bitbucket.

## Which assistants use it

| Assistant | Status |
| --- | --- |
| [Coder](/docs/personas/coder) | Available |
| [Product owner](/docs/personas/product-owner) | Coming soon |
| [Support](/docs/personas/support) | Coming soon |

The Coder is the only persona available today. The Product owner and Support are Coming soon.

## What assistants can do

Jira and Confluence connect through Atlassian's own hosted connector, and they are read only.

| Ability | How it runs |
| --- | --- |
| Read Jira issues | Reads on its own |
| Read Confluence pages | Reads on its own |
| Anything that would create or change an issue or a page | Never run from chat |

## Setup (when it opens)

1. Ask an administrator of your Atlassian organization to allow token sign-in for the hosted connector. Without that, Atlassian refuses the connection.
2. Create a token. Either make a personal token in your Atlassian account (you will also enter your account email), or ask your administrator for a service-account token (no email needed).
3. Open [Integrations](https://stellarfirm.ai/app/integrations) in StellarFirm and pick Jira and Confluence.
4. Paste the token, add your account email if you used a personal token, switch on the live option, and press Connect.

## Permissions

- The assistants see what the token's owner can see. A service account that can read only one project keeps the assistants to that project.
- Nothing here waits for an Approve because nothing here changes data. Creating or editing issues and pages is never run from chat.
- Revoke the token in Atlassian whenever you want to cut access.

## Good to know

- A personal token is quick to try, but a service-account token is the better long-term choice: it does not depend on one person's account.
- During a coding session the Coder gets read-only tools for the connected tools. A personal token with an email is used for chat reads only, so use a service-account token if you want coding sessions to see Jira and Confluence too.
- Give the issue key (for example `PROJ-123`) in your message. It is the fastest way to point at the right ticket.

## Prompts to try

```prompt title="Work the top ticket"
Coder, find the highest-priority open Jira issue in [project], implement it, and wait for my Approve before you push.
```

```prompt title="Read a ticket first"
Read Jira issue [issue key] and tell me what is being asked and what is still unclear. Read only.
```

```prompt title="Check the docs"
Coder, find the Confluence page about [topic] and tell me whether our code still follows it.
```

---

Source: https://stellarfirm.ai/docs/integrations/jira-and-confluence