Planning poker that keeps Linear estimates in sync
Bring your Linear issues into a fast, collaborative estimation room — vote, reveal, agree — then sync the accepted number straight to Linear's built-in estimate field.
- ✓ Search issues by Linear team
- ✓ Synced to Linear's native estimate field
- ✓ Split large issues, linked as related Linear issues
3Estimate in SprintBee, keep Linear in sync
Search Linear issues by team, not a query language.
Type a search term and SprintBee runs Linear's own full-text search; leave it blank and you get the newest issues first. Scope the Workspace to one or more Linear teams — the same role Jira project keys play — then narrow further by state, assignee, or label. Linear has no JQL-equivalent query language, so structured filters plus search cover the common cases.
Vote privately, reveal together.
Everyone sees the same Linear issue while voting. Cards stay hidden until the reveal, so quieter teammates carry the same weight as the loudest voice in the room. New to the format? See how a planning poker round works.
Split an oversized issue in place.
When an issue turns out to be two or three things, split it right in the room. Keep the original or retire it, same as Jira. Choose a quick Local Split that stays inside SprintBee, or create the new items as real Linear issues linked back to the original — but Linear has no parent/child or epic relation, so the link is a plain “related” issue, not a sub-issue hierarchy.
Written straight to Linear's estimate field.
Accept a result and SprintBee writes the number to the issue's built-in Estimate field — Linear only has the one, so there's no field to map. Non-numeric cards (T-shirt sizes, ?, ∞, Pass) are skipped automatically, and nothing is ever force-written.
Checked against your team's Linear scale — never rounded.
Each Linear team can turn on its own estimation scale — Fibonacci, exponential, linear, or T-shirt — and choose whether zero and extended values count. SprintBee checks the accepted number against that team's scale before writing it. If the value isn't on the scale, or the team hasn't turned estimation on, the write is skipped with a reason shown in the room, not rounded to the nearest valid number.
Connect once per organization.
Connect Linear from Dashboard → Integrations and attach it to as many Workspaces as you need — one organization-wide connection, shared by each Workspace's Planning and Retro Rooms. It's available on every paid plan with a 14-day free trial; see pricing or read the Linear integration setup guide.
Supported estimate fields and current limits
✓ What's supported
- Search Linear issues by keyword, or list the newest issues first
- Scope search to one or more Linear teams
- Filter by state, assignee, or label
- Write accepted estimates to Linear's native Estimate field
- Validate the accepted value against the issue's team estimation scale before writing
- Split a story locally for free, or create linked “related” Linear issues on any paid plan
⚠ Current limitations
- No JQL or saved-filter import — search and structured filters only
- Only one write-back target: Linear's built-in Estimate field (no custom field mapping, unlike Jira)
- Non-numeric decks (T-shirt sizes, ?, ∞, Pass) are never written to Linear
- A numeric estimate that isn't on the issue's team scale is skipped, not rounded
- Split children are linked as generic “related” issues — Linear has no parent/child or epic hierarchy for them
- No per-child issue type or required-field picker on split
Linear integration questions
- Does the Linear integration support JQL or saved filters?
- No. Linear has no JQL-equivalent query language. SprintBee searches with Linear's own full-text search, or lists newest issues first when the search box is empty, and narrows further with structured filters for team, state, assignee, and label.
- What happens if I vote a T-shirt size, "?", or "∞" in a Linear-connected room?
- Nothing is written back. Linear's Estimate field only accepts numbers, so any non-numeric card an accepted round lands on is skipped automatically — it's never rounded or forced into the field.
- Will my accepted estimate always sync to Linear?
- Only if the number is on that issue's team's configured Linear scale. Each Linear team can enable Fibonacci, exponential, linear, or T-shirt-style estimation and choose whether zero or extended values count. SprintBee checks the accepted value against that scale before writing it; if it doesn't match, or the team hasn't turned estimation on in Linear, the write is skipped and the room shows why.
- Does splitting a story create Linear sub-issues?
- No. Linear doesn't have a parent/child or epic relation the way Jira does, so SprintBee links split children back to the original issue as a plain "related" issue instead of a hierarchy.
- Is the Linear integration available on the Free plan?
- No — it's a paid feature, the same as Jira. Every paid plan shares the same integrations feature set, and each includes a 14-day free trial.
Start estimating with Linear
in the time it takes to read this.
Spin up a room, import your Linear issues, and keep your backlog in sync.