Frequently asked questions

Which version of Jira does Pokerly work with?

Pokerly is built for Jira Cloud. You open it from Apps → Pokerly.

Who can vote in a session?

Everyone except observers. Session managers are appointed in Settings, observers can join but can’t vote, and everyone else is a participant. Until managers are appointed, Jira admins act as managers.

Can the session manager see votes before the reveal?

No. Votes stay private until the reveal, including from the session manager.

Which Jira fields can Pokerly save estimates to?

Any number field (such as Story points or Story point estimate), Original estimate (time tracking) or a text field. Set a default in Settings and override it per session.

What happens if Jira rejects the estimate?

The estimate is kept in Pokerly and can be re-synced later. Pokerly writes to Jira as the signed-in user, so the session manager needs permission to edit the issue.

Do “?” and “☕” cards count towards the average?

No. Cards without a value are left out of the statistics.

Can we use our own card deck?

Yes. Alongside Fibonacci, Modified Fibonacci, T-shirt sizes and Powers of 2, teams can create their own decks. Cards can carry numeric values, so T-shirt sizes can map to points.

How does Insights measure actual effort?

As time logged (optionally including sub-tasks) or as cycle time between two statuses (optionally weekdays only).

Where is our data stored?

Pokerly is built on Atlassian Forge and uses Forge-hosted storage within your Atlassian environment. It has no external servers and makes no external data egress calls.

What permissions does Pokerly request?

read:jira-work, write:jira-work, read:jira-user and storage:app. No external permissions.

Does Pokerly support dark mode?

Yes. Pokerly follows Jira’s light and dark themes.