Jira

SprintBee works with Jira Cloud. Jira Data Center and Jira Server are not supported by either connection described here.

What a Jira connection adds#

Without a connection, a room still estimates anything — you type work items in by hand. A connection replaces that typing with a link back to Jira:

• Search Jira from inside a room and import issues into the queue in one click.
• Keep imported items fresh as their Jira issues change.
• Write an accepted estimate back onto the issue's story-point field.
• Split an oversized item into real new Jira issues rather than local rows.
• Pick a Jira sprint as the period a Sprint Retro looks back over.

Two ways to connect#

Both are full, API-backed connections to a Jira Cloud site. They differ mainly in who authorizes them and whose name appears on the changes.

Personal connection#

One teammate signs in with their Atlassian account and authorizes SprintBee. SprintBee itself asks for no Jira administrator, though your Atlassian organization may still apply its own app-approval policy. Comments and field updates arrive in Jira under that person's Atlassian identity, and the connection appears in the dashboard only for the teammate who created it.

Organization connection#

A Jira site administrator installs the SprintBee Jira app — an Atlassian Forge app — and pairs it to one SprintBee organization using a short-lived code the organization's owner generates. Changes are attributed to SprintBee rather than a person, and every active owner and admin of that organization sees the connection and can attach it to a Workspace.

Each Jira site pairs with exactly one SprintBee organization; a single organization can pair several Jira sites.

Which one to choose#

	Personal	Organization app
Who sets it up	Any teammate with Jira access	Jira site admin and organization owner
Jira shows changes as	That teammate	SprintBee
Visible to	Only its author	All organization owners and admins
Survives someone leaving	No — reconnect as someone else	Yes

Personal connections are the fastest way to try Jira import in an afternoon. The organization app is the one to standardize on, because it does not quietly depend on one colleague's Atlassian account still existing next quarter.

A SprintBee organization can run both at once, and different Workspaces can use different connections.

Where Jira is configured#

Jira lives on two dashboard surfaces. Organization → Integrations is where connections are created, listed and disconnected: Add connection starts either an Atlassian sign-in for a personal connection, or a Create pairing code flow for the Jira app. Workspace → Integrations & notifications is where a Workspace picks which connection and Jira site it uses, then sets search scope, write-back and splitting. When something refuses, the error messages are catalogued here.

A room's own settings dialog has no integrations tab — it covers the room and its participants. Everything Jira-related lives in the dashboard, and a Workspace's Planning and Retro Rooms share the source it selects.

When you cannot connect the API#

If Jira API access or app approval is out of reach, the Browser Companion is a free alternative on every plan. It pairs a Jira Cloud tab you already have open with a room and captures the visible issue's key and title into the queue. It cannot search, bulk-import or write anything back to Jira.

Plan and permissions#

Jira connections are part of SprintBee's paid Pro plan. Free rooms can estimate Jira work only by typing it in or capturing it with the Browser Companion.

Make the connection from the account that owns the paid organization. SprintBee reads a person's plan from the organization they own, so a teammate who is only a member of a paid organization is treated as being on Free and the connect screens refuse them. Pairing the Jira app narrows it further: only the organization owner can generate a pairing code, not an admin.