PLANNING POKER FOR JIRA TEAMS

Estimate together.
Sync to Jira. Move on.

Import a sprint, vote privately, reveal together, and write story points back to Jira in one click. Refinement in 30 minutes, not 90.

Start a free session See how it works
Sprint 42 · Backlog refinement
room/aurora-team
04:005 onlineJira connected
QUEUE · 6 ISSUES
JRA-2837  Rate-limit API keys5
JRA-2839  Audit-log retention3
JRA-2841  Billing webhooks
JRA-2842  Dunning email flow
JRA-2844  Proration edge cases
JRA-2845  Invoice PDF retries
JRA-2841StoryVoting

Migrate billing webhooks to the event bus

backendbillingsprint-42

Stripe webhook handlers currently write straight to the ledger. Move them onto the internal event bus so retries, ordering, and dead-lettering are handled by the platform.

AC1 All 14 webhook types published as events
AC2 Replay tool covers the migration window
MK
Mara
JT
Jonah
AR
Asha
PD
Priya
LW
Liam
Waiting for votes · 3/5
YOUR VOTE
BUILT FOREngineering managersScrum mastersProduct managersRemote teams on JiraAgencies across time zones
THE PROBLEM

Estimation today is three jobs glued together with a video call.

01

The call drags

Forty minutes of “wait, was that a 5 or an 8?” across time zones, muted mics, and one shared screen.

02

The loudest voice anchors

Whoever speaks first sets the number. Everyone else quietly rounds toward it — that’s not an estimate, it’s an echo.

03

The sheet drifts from Jira

Votes land in a spreadsheet, points live in Jira. By Thursday the two disagree and nobody knows which one is right.

04

The cleanup pass

Someone copy-pastes estimates into Jira after the call. Usually wrong, always late, never their favorite part of the week.

THE WEDGE

One narrow job, done properly.

PointFlow doesn’t replace Jira and it isn’t an agile suite. It runs the estimation session — and only that.

5

Hidden until reveal

Votes stay private until everyone is in. No anchoring, no waiting to see what the senior dev picks.

pointflow.app/r/aurora · copied

Join by link

Voters don’t need accounts. Drop the link in Slack and the whole team is in the room in seconds.

sprint = "Sprint 42" AND type = Story

Import from Jira

Pull a sprint, an epic, or any JQL query. Issues arrive with descriptions, labels, and acceptance criteria intact.

story_points ← 8 ✓

Write-back to Jira

Accepted estimates land in your estimation field instantly. No copy-paste pass after the call, ever.

1 2 3 5 8…XS S M L XLcustom

Any deck

Fibonacci, T-shirt sizes, powers of two — or define your own scale per room. Mapped to numbers for Jira either way.

spread 5–13Round 2consensus 8

Quick re-vote

Wide spread? Hear the 5 and the 13 out, re-deal in one click, and converge. Every round is logged.

THE FLOW

Three steps. The third one is automatic.

1

Import your backlog

Connect Jira once. Pull tonight’s issues by sprint, epic, or JQL — queue is ready before the call starts.

2

Vote privately, reveal together

Everyone picks a card. Nothing shows until reveal. Spread too wide? Discuss and re-vote in one click.

3

Sync estimates to Jira

Accept the number and it’s written to your story points field immediately. The session summary is your receipt.

WHY POINTFLOW

Better than the workarounds you’re using now.

Spreadsheet + callShouting numbers on ZoomAgile suite add-onPointFlow
Private votingSometimes✓ Always
Points written back to JiraManual pasteManual pasteVia their board✓ One click
Setup per sessionRebuild the sheetNone, but chaosConfigure the suite✓ Pick a sprint
Guests without accountsShare the sheet…✕ Seats required✓ Join by link
Time per 20-issue session~90 min~60 min + bias~60 min~30 min
PRICING

Voters are always free. You pay for facilitators.

Free
$0
For trying it on one team.
1 room, up to 5 voters
Fibonacci deck
Jira import (read-only)
7-day session history
Start free
MOST TEAMS
Team
$8/ facilitator / month
For teams that estimate every sprint.
Unlimited rooms & voters
Two-way Jira sync
Custom decks & re-vote rounds
Full session history
Start 14-day trial
Pro
$14/ facilitator / month
For orgs with rules.
SSO / SAML
JQL presets & field mapping per project
Estimate & spread analytics
Priority support
Talk to us
FAQ

The questions your security team will ask.

Is our Jira data secure?+

PointFlow connects via Jira’s OAuth 2.0 and requests the minimum scopes: read issues, write to one estimation field. We never see your source code, store data encrypted at rest in the EU or US (your choice), and delete session data on request. SOC 2 Type II report available under NDA.

How does the Jira integration work?+

Install the PointFlow app from the Atlassian Marketplace or connect with OAuth. Works with Jira Cloud and Data Center. You map which field receives estimates per project — Story Points, Story point estimate, or any numeric custom field.

Do participants need PointFlow accounts?+

No. Only the facilitator needs an account. Voters join with the room link, pick a name, and vote — from any browser, including their phone.

Can we use our own estimation scale?+

Yes. Fibonacci and T-shirt decks are built in; on Team and Pro you can define any card set per room and map each card to the numeric value written to Jira.

Your next refinement could take 30 minutes.

Connect Jira, import a sprint, and run your first session today. Free for one team, no card required.