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. 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. Decide whether to tick Include assignee and reporter. Also off by default, and independent of the description checkbox.
7. 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 Item splitting — becomes editable. Those sections stay locked until a source exists, because each needs a real connection to read fields and projects from Jira.

Everything else an issue carries — its status, its type and priority, its labels, its parent epic, and any estimate it already has — is imported without a checkbox. None of it is free-text, so none of it can carry detail the issue's own key does not already reveal.

Import extra Jira fields#

Plenty of Jira sites keep the thing a team most needs while estimating outside the Description field — Acceptance Criteria in a field of its own is the usual case. The Extra issue fields section of the Import tab imports up to five such fields with each issue and shows them in the room's Full work item panel, under the description.

1. Select Add a field, then pick the Jira field from the list. It offers this site's real fields, so there is no field id to look up or type. Each option names the field's type — Acceptance Criteria (text) — which is how to tell two identically named fields apart. Jira's own fields are marked system.
2. Edit Shown as if the site's own field name is not what the room should read. It defaults to the Jira name.
3. Repeat for each field, then select Save extra fields.

Rich-text fields are rendered the way descriptions are — headings, bullets and links all survive. Single-select, multi-select, number, date and checkbox fields read as plain text. A field an issue has nothing in shows nothing at all, rather than an empty heading.

People fields are deliberately not offered. Assignee and reporter have their own checkbox, and mapping a user field is not a way around it — a mapped people field imports no value.

Fields every issue already brings in are not offered either — its summary, labels, and the dates it was updated. Rooms see those on the queue and in the Full work item metadata already, so mapping one would print the same value twice.

Imported values are a copy, read at import time and refreshed with the rest of the issue. Editing them in SprintBee is not possible; edit them in Jira and refresh the item.

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.

Set up the room's searches#

The Jira tab of Add work items offers exactly the searches this room has saved — SprintBee no longer ships generic ones of its own, because a filter that suits every Jira site suits no team's backlog.

In the Saved searches section of the same panel:

• The Default search is the JQL that runs the moment a moderator opens Add work items. Give it a display name and it labels its own chip.
• Additional searches are up to four more named searches, each a chip beside the default.
• Start from a suggestion / Add a suggested search fill a row with one of three common starting points: work items without points, work items in the current sprint, and work items in future sprints. They are starting points, not finished JQL — the estimate field and sprint names differ per site.
• Run search runs that row against your Jira site there and then, and reports how many work items matched or the error Jira gave. Use it before you save: JQL that parses can still name a field this site does not have.

Select Save searches when the rows read the way you want them to.

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 This Workspace has no Jira source yet. means the room still has no source — the save either did not complete, or you configured a different Workspace. The message links back to Workspace settings so you can check.

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.