Filter results by tag
PROJ-128
Allow multiple tags, persist across page reloads.
Queue
Profile avatar uploads
Filter by tag
Notification preferences
Export to CSV
Works with the tools you already use
Connect Atlassian once and your projects show up. Pick the tickets you want to estimate this sprint, and they land in the queue ready to vote on.
When the team agrees on a number, push it to your Jira story-points field without leaving the room. No copy-paste. No tab-hopping. No standup spent chasing whose estimate was what.
PROJ-128
OAuth refresh token handling
OAuth refresh token handling
PROJ-247
Let users connect their TikTok account so we can pull their videos, follower counts and engagement metrics into the dashboard. Refresh tokens nightly so data stays fresh without forcing them to re-auth.
Walk the team through each issue while the vote deck stays hidden. Title, description, acceptance criteria — everyone reads the same thing at the same time. When the room is ready, the host clicks Start Voting.
Alex Møller
alex@getflowbox.com
Bind a session to a Jira project and only members of that project can join. Backed by Atlassian OAuth — no extra access list to manage, no shared passwords, no leaked links.
Features
Connect once and your backlog flows in. Vote on a ticket, set the final estimate, and it lands in Jira before standup. Create new issues mid-session without leaving the room.
Voting scales
Four built-in scales, switchable per session. Pick one when you create the session — every voter gets the same deck.
Numbers that grow non-linearly: 1, 2, 3, 5, 8, 13, 21. The gaps between values get larger as estimates grow — a clean way to express that uncertainty also grows. Forces a decision between "small" and "much bigger" without false precision.
Best for: Most agile teams. Default choice if you’re unsure.
Adds ½ for trivial tasks and extends to 40 and 100 for epics that probably need to be split. Useful when your backlog has a mix of tiny tweaks and large features and you want one scale that covers both.
Best for: Mature teams comfortable with relative sizing across a wide range.
XS through XXL — no math, no story-point baggage. Great for teams new to estimation, for high-level epic sizing, or when stakeholders are in the room and you want to avoid debating whether something is a 5 or an 8.
Best for: New teams, epic-level planning, cross-functional sessions.
Each value is exactly twice the previous: 1, 2, 4, 8, 16, 32, 64. Some engineering teams prefer the binary cadence — it maps naturally to "this is the same / twice / four times the work" without the irregular Fibonacci jumps.
Best for: Infrastructure, platform, or any team that thinks in doublings.