Pokerly

Features

Everything Pokerly does

Pokerly runs planning poker inside Jira Cloud. Teams vote privately, a session manager reveals the cards, and the agreed estimate is written back to the Jira field you choose.

Real-time sessions

Planning poker that lives in Jira, updated in real time for everyone in the session.

  • Live sessions for estimating right now.
  • Upcoming sessions, so you can prepare a queue ahead of time.
  • Completed sessions to look back on.
  • All in the app's lobby, under Apps → Pokerly.

Clear roles

Everyone knows what they can do in a session.

Session managers
Appointed in Settings. They run sessions, reveal the cards and save the final estimate.
Participants
Everyone else. Participants vote on each issue.
Observers
Appointed in Settings. Observers can join a session but can't vote.

Jira admins act as session managers until managers are appointed, and can always open Settings.

Issue queue

Build the list of issues to estimate your way, then keep it tidy as you go.

Add issues

  • Type-ahead search
  • A filter builder: project, type, status, “without estimate” and text
  • Raw JQL

Organise

  • Drag and drop to reorder, or use Alt + ↑ / ↓
  • Skip, remove, re-estimate, or send an issue back to the queue

Private voting

Discuss the same issue, then vote without anchoring on anyone else.

  • The current issue is highlighted for everyone.
  • Full details on the same page: description, assignee, reporter, sprint, labels, parent and current estimate.
  • Votes stay private until reveal, including from the session manager.
  • Vote with the keyboard as well as the mouse.

Reveal and statistics

The session manager reveals the cards and everyone sees the result at once.

  • Flip animation
  • Average
  • Median
  • Agreement
  • Range
  • Vote distribution
  • Consensus detection
  • Suggested card

Cards without a value, such as ? and ☕, are left out of the statistics.

Save to Jira

Agree, save and move on.

  1. The manager picks a card, or types a custom value.
  2. They save it to Jira.
  3. The queue moves on to the next issue automatically.

If Jira rejects the write, the estimate isn't lost. Pokerly keeps it so it can be re-synced later.

Card templates

Start with a built-in deck or create your own.

  • Fibonacci

    Built in

  • Modified Fibonacci

    Built in

  • T-shirt sizes

    Built in. Sizes can map to points.

  • Powers of 2

    Built in

  • Teams can create their own decks.
  • Cards can carry numeric values, so T-shirt sizes can map to points.
  • Cards without a value (?, ☕) are left out of the statistics.

Your estimation field

Save estimates to the field your team already uses.

  • Any number field, such as Story points or Story point estimate
  • Original estimate (time tracking)
  • A text field

Set a default field in Settings, then override it for a single session when you need to.

Estimation Insights

Compare estimates with the actual effort, measured as time logged or cycle time, and see where the team tends to under- or over-estimate.

How Insights works

Themes and accessibility

Small details that make sessions smoother.

  • Light and dark

    Follows Jira's light and dark themes.

  • Keyboard voting

    Pick a card without reaching for the mouse.

  • Accessible labels

    Controls are labelled for assistive technology.

  • Reduced motion

    Respects your reduced-motion setting.

  • Realtime updates

    Changes appear live, with a polling fallback.

Platform and permissions

Built on Atlassian Forge with no external backend. The app has no external servers and keeps its data in Atlassian's cloud.

Jira reads and writes run as the signed-in user, so people only see issues they're allowed to see.

Permissions requested

  • read:jira-work
  • write:jira-work
  • read:jira-user
  • storage:app

No external permissions. See the data and privacy statement for details.

Ready to estimate in Jira?

Coming soon to the Atlassian MarketplaceGetting started