Estimates nobody can anchor to.
Everyone plays a card face-down. Nobody can see anybody else's.
Then everyone flips at once.
No anchoring, no deferring to whoever spoke first.
The number lands in Jira.
One click, the field you chose, no copying between tabs.
Why teams stick with it.
Genuinely hidden votes
Card values never leave the server until the reveal — not hidden with CSS, simply absent from the data. Nobody can peek in devtools.
Scales you define
Fibonacci, t-shirt sizes, or something of your own. Map each card to the number Jira should receive, and keep '?' and '☕' for when they are the honest answer.
Straight into Jira
Connect your Jira Cloud site once. We discover which numeric field holds your estimates and confirm it is actually writable before you rely on it.
A record you can keep
Every round is stored with who voted what, the agreed value and whether Jira accepted it. Export the lot as CSV.
Built around teams
Scales and the Jira connection belong to the team, not to whoever set them up. New teammates get the right configuration by joining.
About the Jira connection.
An admin connects your Jira Cloud site with an Atlassian API token. The token is encrypted before it is stored and is never sent back to the browser.
Estimate fields are not standardised across Jira sites — the id differs between instances, and between team-managed and company-managed projects. So we read the list of numeric fields from your site, let you pick one, and then verify against a real issue that Jira will actually accept a write. Better to find that out during setup than mid-refinement.
- What we write
- One numeric field on the issue you are estimating, only when a moderator explicitly asks for it.
- What we read
- Issue keys, summaries, descriptions and the current estimate, for the issues you choose to import.
- Cards without a number
- “?” and “☕” are excluded from the median and cannot be written to a numeric field — the app tells you why rather than failing quietly.
- Jira Cloud only
- Server and Data Center are not supported.
Your next refinement could be the good one.
Set up a team, define a scale, and run a round in a couple of minutes.