Connect a room to Jira

Connecting your Atlassian account to SprintBee makes Jira available. It does not yet make it available anywhere in particular. A room only imports issues once you attach one of those connections to the Workspace that owns it.

That attachment is made in the Workspace's settings on the dashboard, not from inside a live room.

Before you start#

You need all four of these:

• A paid plan. Work item integrations are included on Pro, Pro Plus and Pro Ultra. Free rooms can still bring Jira issues in one at a time with the Browser Companion.
• A Jira connection already on the dashboard. Either a personal OAuth connection or the shared Jira app. If the Integrations page lists none, add one there first.
• An account on a paid plan. Any active member of an organization with a paid plan can attach and change sources — you do not have to be its owner.
• The Workspace you want to connect. A Jira source belongs to one Workspace and is shared by its Planning Room. Other Workspaces are unaffected by what you do here.

Attach the Jira source#

1. Open Workspaces and select the Workspace you want to connect.
2. In the Settings group of the sidebar, choose Integrations & notifications.
3. Find the Work items come from card. It shows the source currently selected, its Jira host, and a badge reading Live, Saved · inactive, or Not active yet.
4. If you have more than one connection, select Switch source and pick the Jira site you want from the list.
5. Decide whether to tick Include Jira descriptions in SprintBee. It is off by default.
6. Select Save Jira source. If the Workspace already imports from something else, the button instead reads Save & make active.

The badge flips to Live once the save lands, and the rest of the panel — Saved searches, Project scope, Estimate write-back and Story splitting — becomes editable. Those sections stay locked until a source exists, because each needs a real connection to read fields and projects from Jira.

If the card shows Reconnect Jira to grant webhook access for automatic queue updates, the connection predates SprintBee's webhook scope. The source still works; only the automatic refresh of queued items is unavailable until you reconnect from the same card.

Confirm the room is importing#

1. Enter the Workspace's Planning Room.
2. As moderator, open Add work items and switch to the Jira tab.
3. Run the room's default search, or paste an issue key.

Results mean the attachment worked. The message Configure a Jira source in room settings before importing issues. means the room still has no source — the save either did not complete, or you configured a different Workspace.

Switch or remove the source#

A Workspace imports from exactly one source at a time. Selecting a different Jira site (or Linear workspace) and saving replaces the live one rather than adding a second.

To switch: reopen Integrations & notifications, choose Switch source, select the new site, and save. While you have a non-live source selected the card tells you which source the room imports from right now, so you can back out before saving.

To detach entirely, select Remove source and confirm.

When the source will not save#

What you see	What it means
External integrations are available on any paid plan.	The signed-in account resolves to Free. Check that your membership of the paid organization is active.
Connect Jira or Linear from the Organization Dashboard before configuring this room.	No connection exists yet to attach. Add one on the dashboard's Integrations page.
Your plan does not include integrations.	The save was rejected server-side for the same reason as the first row.
Connected workspace not found.	The Jira site was reachable when the page loaded but is not now — usually a revoked personal connection or an uninstalled Jira app. Reconnect, then reload this page.
Save button greyed out	Nothing has changed since the last save, or no Jira site is selected.