> For the complete documentation index, see [llms.txt](https://help.rhythms.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rhythms.ai/connectivity/connectors/set-up-the-atlassian-connector.md).

# Set up the Atlassian connector: Jira, Confluence and Atlassian Goals

Connect Atlassian, auto-update goals from Jira and Atlassian Goals, use Confluence as context, and move from the legacy connector.

The **Atlassian** connector gives Rhythms access to Jira, Confluence and Atlassian Goals, with your own Atlassian permissions. A Key Result or Initiative can update itself from Jira issues or from an Atlassian goal, and you can use Jira and Confluence as context in Rhythms chat.

{% hint style="info" %}
**Atlassian** replaces **Atlassian (legacy)**, which can't read Atlassian Goals.
{% endhint %}

{% embed url="<https://www.loom.com/embed/cb54515c1eb44f9d952b4965acf45e26>" %}

The video shows connecting Atlassian, switching an Initiative to update from Jira, and editing the connection in place.

## Before you start

* **Atlassian** is enabled by default in **Settings › Workspace › Connectors**. If you can't find it, ask a Rhythms Admin.
* An Atlassian organization admin must allow the Rhythms domain once: [Atlassian Admin Portal](https://admin.atlassian.com/) › **Apps › AI Settings › Rovo MCP Server › Add Domain**. Enter `app.rhythms.ai/**`, then click **Save**. Connecting fails until this is done. If Atlassian (legacy) already works for your site, this is usually already done.
* You need an Atlassian account with access to the Jira projects, Confluence spaces and goals you want to use. Rhythms sees only what you can see.
* Each person connects their own account unless an admin shared a connection. See [Share a connector with your team](https://help.rhythms.ai/connectivity/share-a-connector-with-your-team.md).

## Connect Atlassian

1. Open **My connectors**.
2. Find **Atlassian** under **Popular connectors**. If it isn't listed there, find it under **Browse connectors**. Choose **Atlassian**, not **Atlassian (legacy)**.
3. Click **Connect**.
4. In the Atlassian window, choose the apps and the site, then accept the permissions.

Once connected, Atlassian moves to **Your connections** and shows **Connected**.

<figure><img src="https://4039886202-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEGNgNGJOnocLzqT0TwtU%2Fuploads%2FUM7MCM58gnev6kAOPZIY%2Fatlassian-card-connected-20261109.png?alt=media" alt="The Atlassian card under Your connections in My connectors, showing Connected" width="360"><figcaption></figcaption></figure>

The connection uses OAuth, with no keys required. Admins can restrict read or write tools in **Settings › Workspace › Connectors**, on the connector's **Tools** tab, then click **Save controls**. See [Manage connectors for your workspace](https://help.rhythms.ai/connectivity/manage-connectors-for-your-workspace.md).

## Auto-update from Jira

Only Key Results and Initiatives can auto-update. Objectives can't. The setup flow is the same for every connector: click the **Update mode** chip, then **Set up auto update**, and describe what to track in the chat that opens. See [Set up automatic updates from a connector](https://help.rhythms.ai/connectivity/connectors/set-up-automatic-updates-from-a-connector.md).

### What you can track

* Completion percentage: issues in the Done status category divided by all issues in a project, epic, sprint or JQL scope
* Story points completed versus total
* Bug counts by priority or severity
* Sprint progress: completed versus remaining
* Issue counts by assignee or status category

Give Rhythms a project name or key, or your own JQL. Rhythms builds the query, finds how your Jira names its fields (for example, which custom field holds story points) and groups statuses by category, so it works with custom workflows. The query runs fresh on every sync, so issues that newly match are included.

### Keep a Key Result current from issue completion

**Prompt:** *"Set up auto-update for my Ship Game Engine KR. It's the SMS project in Jira."*

Rhythms shows the current count, for example 7 of 22 issues done (32%), and asks you to confirm. The **Update mode** chip switches to **Update from Atlassian**. Each week Rhythms posts a check-in with the new value and a short note such as *"9 of 22 issues done (41%). 6 in progress, 7 to do."*

### Track story points instead of issue counts

**Prompt:** *"Track this KR as story points completed versus total in the current sprint of project SMS."*

Rhythms finds the estimate field your Jira uses and confirms the totals before saving. The weekly note reports points completed and remaining. If no issues have estimates, Rhythms says so and suggests completion percentage instead.

### Scope with JQL, labels, epics, sprints or assignees

**Prompt:** *"Only count issues in the PAY project labelled `compliance` that are in an open sprint."* Or paste your own JQL.

Rhythms saves the filter as a JQL query and shows it in the connection summary with a link back to Jira. New matching issues are picked up on the next sync.

### Edit, pause or stop

Click the **Update mode** chip. Choose the connection to edit its query, calculation or source in chat, or switch to **Manual update** to stop syncing without losing the connection. Switching back resumes the weekly schedule. **Remove connection** stops the auto-update.

Auto-updates also pause on their own while the goal is closed or postponed, and once its end date has passed by more than a quarter of its duration. The Key Result then shows **Auto-updates paused** with a note asking you to extend the end date.

## Use Jira and Confluence in chat

### Pre-fill a check-in from recent Jira activity

Open **Check-in** on a Jira-connected Key Result or Initiative. No prompt is needed. Rhythms queries Jira live and pre-fills the value, a suggested status and a draft note on what changed since the last check-in. Edit and save. This check-in is recorded as yours, not as an automatic update.

### Ask cross-project questions

**Prompt:** *"Across the PAY, RISK and CORE projects, which issues tagged for the Q3 launch are still open, and who owns them?"*

Rhythms runs the searches and replies with a grouped summary you can turn into a document or paste into a check-in.

### Use Confluence pages as context

**Prompt:** *"Draft this quarter's platform status update from the 'Platform Roadmap 2026' Confluence page and the open issues in the CORE project."*

Rhythms reads the page, pulls the matching Jira issues and drafts the document in Rhythms. A Key Result can't measure a Confluence page.

### Create or update Jira issues

**Prompt:** *"Create a Jira issue in PAY for the fraud-rule regression we just discussed and assign it to me."*

Rhythms creates the issue through your Atlassian account and replies with its key. Creating issues, adding comments and moving statuses happen only when you ask.

## Use Atlassian Goals

### Read goals

Ask Rhythms for a goal's status, owner, target date, latest updates and Key Results. Example: *"Show the status, owner, target date and latest update for the Atlassian goal 'Launch the Season 4 battle pass' and its Key Results."*

<figure><img src="https://4039886202-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEGNgNGJOnocLzqT0TwtU%2Fuploads%2F7YpmEbnqkTkig9uTE8Kp%2Fatlassian-read-goals-20261109.png?alt=media" alt="Rhythms chat answering with a table for the Atlassian goal Launch the Season 4 battle pass and its Key Result: status, owner, target date and latest update"><figcaption></figcaption></figure>

### Create goals and post updates

Rhythms creates or changes Atlassian goals only when you ask. Example: *"Create an Atlassian goal 'Launch the Season 4 battle pass' due December 31, 2026, with a Key Result 'Sell 250,000 battle passes'. Then post an update on the Key Result: '96,000 of 250,000 sold in the first two weeks.'"*

Rhythms replies with links to the new goal and Key Result in Atlassian.

<figure><img src="https://4039886202-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEGNgNGJOnocLzqT0TwtU%2Fuploads%2Fvtp4vqAD5fWemGW3r2Fc%2Fatlassian-create-goal-20261109.gif?alt=media" alt="Asking Rhythms in chat to create an Atlassian goal and Key Result and post an update. Rhythms replies with links to the new goal and Key Result in Atlassian."><figcaption></figcaption></figure>

An update posted as text doesn't change the goal's progress in Atlassian. Progress there comes from the goal's metric targets.

### Bring a goal into Rhythms

Ask in chat to copy an Atlassian goal and its Key Results into Rhythms as an OKR. Example: *"Bring the Atlassian goal 'Expand studio partnerships' and its Key Result into Rhythms as an OKR in the 2026 time period, owned by me. Publish it."*

Rhythms creates an Objective with its Key Results, using the same names and dates. It adds the latest Atlassian update to the description but doesn't record a check-in, so the Key Results start with no value. Set up an auto-update, below, to keep them current.

<figure><img src="https://4039886202-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEGNgNGJOnocLzqT0TwtU%2Fuploads%2F2EferWvn1Ou2wF3UCx66%2Fatlassian-bring-into-rhythms-20261109.gif?alt=media" alt="Asking Rhythms to bring the Atlassian goal Expand studio partnerships into Rhythms. Rhythms creates an Objective and Key Result in the 2026 time period."><figcaption></figcaption></figure>

This is a one-time copy, not a sync. Later changes in Atlassian, such as a new Key Result or a renamed goal, don't appear in Rhythms.

### Auto-update a Key Result or Initiative from an Atlassian goal

1. Open the Key Result or Initiative and click its **Update mode** chip. It shows **Manual update**.
2. Click **Set up auto update**. Chat opens and asks where the data comes from.
3. Name the Atlassian goal, by its key or link, and say how to read its number. Example: *"Use the Atlassian goal 'Sign 12 new studio partnerships' through the Atlassian connector. Read the number of partnerships signed from its latest update."*
4. Review the rule Rhythms proposes. Nothing is saved until you confirm.
5. Confirm. Rhythms checks in the current value right away, then updates weekly.

<figure><img src="https://4039886202-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEGNgNGJOnocLzqT0TwtU%2Fuploads%2FFxn4Tfx3cq17JtzF1hmt%2Fatlassian-auto-update-1-20261110.gif?alt=media" alt="On a Key Result, opening the Update mode chip, clicking Set up auto update, and naming the Atlassian goal in the chat that opens"><figcaption></figcaption></figure>

<figure><img src="https://4039886202-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEGNgNGJOnocLzqT0TwtU%2Fuploads%2FxS0tZ2za5Kl0XWsIry1T%2Fatlassian-auto-update-2-20261110.gif?alt=media" alt="Rhythms proposes the auto-update rule, the user confirms, and the Key Result is updated from Atlassian at 7 of 12 (58%)"><figcaption></figcaption></figure>

The chip now shows **Update from Atlassian**. Click it to see what it tracks, when it last ran and when it runs next. **Edit** changes the rule in chat. **Remove connection** stops the auto-update.

<figure><img src="https://4039886202-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEGNgNGJOnocLzqT0TwtU%2Fuploads%2FstI12RFSJpOSv6iLsNCf%2Fatlassian-update-mode-chip-20261110.png?alt=media" alt="The Update mode chip showing Update from Atlassian, with What it tracks, When (last synced, updates weekly, next run), Edit and Remove connection" width="520"><figcaption></figcaption></figure>

Rhythms reads the Atlassian Key Result's metric target if it has one. Without a metric target, Rhythms reads a consistently written number in the latest update, such as *"7 of 12 partnerships signed, 2 more in legal review"*, which checks in as 7 (58%). If the latest update has no number, that week's check-in is skipped and the value is left as it is.

Updates run weekly by default. See [Set up automatic updates from a connector](https://help.rhythms.ai/connectivity/connectors/set-up-automatic-updates-from-a-connector.md).

## Move from Atlassian (legacy) to Atlassian

**Atlassian (legacy)** keeps working, and nothing moves on its own. The two connectors use different Atlassian sign-ins, so a legacy connection can't be converted: each person connects **Atlassian** once, then moves their own goals. You can keep both connected while you move. New workspaces get Atlassian only. The older **Jira** connector is also deprecated in favor of Atlassian, and existing Jira connections keep working.

### Reconnect doesn't move you

**Reconnect** renews the sign-in for the same connector. Use it when a connector shows **Needs attention**. It doesn't move anything from Atlassian (legacy) or Jira to Atlassian.

<figure><img src="https://4039886202-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEGNgNGJOnocLzqT0TwtU%2Fuploads%2FuU6i8o7vT5oWVKSgCIff%2Fatlassian-card-menu-20261109.png?alt=media" alt="The Connected menu on the Atlassian card in My connectors, with Reconnect and Disconnect" width="360"><figcaption></figcaption></figure>

### Move Key Results and Initiatives that update from legacy

1. Connect **Atlassian**, as above. Leave Atlassian (legacy) connected for now.
2. Open a Key Result or Initiative whose **Update mode** chip shows **Update from Atlassian (legacy)**. Click the chip and copy what it shows under **What it tracks**.
3. Click **Remove connection**, then confirm. This stops the legacy auto-update.
4. Click the chip again, then **Set up auto update**. Ask Rhythms to track the same thing with the Atlassian connector, and paste what you copied.
5. Repeat for each goal.

### Move playbooks that use legacy

A playbook that uses Atlassian (legacy), such as a weekly business review, can be moved by the person who created it:

1. Connect **Atlassian**, as above. Leave Atlassian (legacy) connected for now.
2. Ask Rhythms in chat to switch the playbook to the Atlassian connector. Example: *"Change my weekly business review playbook to use Atlassian instead of Atlassian (legacy)."*
3. Wait for the playbook's next scheduled run. Before it starts, Rhythms attaches your Atlassian connection. Until then, the playbook's page shows Atlassian as not connected.
4. Repeat for each playbook.

Rhythms attaches only the creator's own connection this way. If someone else created the playbook, ask them to make the switch.

### Disconnect Atlassian (legacy)

When nothing uses it any more, disconnect Atlassian (legacy) in **My connectors**. Before anything is removed, the confirmation lists the OKRs still updating from it and any playbooks that would be turned off. If it lists any, cancel and move those first.

## Limits

* Scheduled auto-updates only read from Atlassian. They never change Jira issues or Atlassian goals.
* You can't delete Atlassian goals from Rhythms.
* Rhythms doesn't sync goal structure with Atlassian. Bringing a goal in is a one-time copy.

## FAQ

**How often does an auto-update run?** Weekly by default. The first run happens around 3 AM UTC the day after setup, then on the same weekday each week. Open **Check-in** any time for a fresh draft, or ask in chat to change the schedule.

**Does Rhythms copy the Jira status onto the Key Result?** Not by default. Rhythms sets on track or at risk from progress against the timeline. If you ask during setup, it can read a Jira status field and map its values to Rhythms statuses.

**Why do I have to connect again?** Atlassian (legacy) and Atlassian use different Atlassian sign-ins, so Rhythms can't carry a legacy connection over. Each person connects Atlassian once.

**Does Reconnect move me to the new connector?** No. It renews the sign-in for the same connector. Connect Atlassian and move each goal.

**Will my legacy auto-updates and playbooks stop?** Not on their own. They keep running until you remove them or disconnect Atlassian (legacy). A legacy connection that shows **Needs attention** has already stopped updating: reconnect it or move its goals.

**Do I have to move everything at once?** No. Both connectors can stay connected, so you can move one goal at a time.

**I have an older "Jira" connection. Is it the same thing?** No. The older Jira connector is deprecated for new connections. Existing ones keep working and still sync daily. New setups use **Atlassian**.

**Will Rhythms change my Jira issues or Atlassian goals automatically?** No. Rhythms changes them only when you ask in chat.

## Related articles

* [Set up automatic updates from a connector](https://help.rhythms.ai/connectivity/connectors/set-up-automatic-updates-from-a-connector.md)
* [Manage connectors for your workspace](https://help.rhythms.ai/connectivity/manage-connectors-for-your-workspace.md)
* [Share a connector with your team](https://help.rhythms.ai/connectivity/share-a-connector-with-your-team.md)
* [Create and run a playbook](https://help.rhythms.ai/playbooks/create-and-run-a-playbook.md)
* [Write and submit check-ins](https://help.rhythms.ai/goals-and-okrs/managing-and-tracking-goals/write-and-submit-check-ins.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.rhythms.ai/connectivity/connectors/set-up-the-atlassian-connector.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
