Planning Poker & Magic Estimation for Jira by Bitwerf – Documentation

Estimate issues with your team in Jira Cloud and save the results in story points, the time estimate or another field.

Start a session

Open Planning poker in the sidebar of a project, or under Apps in the top bar.
Click New session and give it a name.
Choose how you want to estimate (see below).
Choose where the estimates are saved: a number field such as Story Points or Story point estimate, the original time estimate, a single-line text field, or nowhere.
Choose the cards: Fibonacci, modified Fibonacci, powers of two, T-shirt sizes, time, or type your own.
Write a JQL search, click Find issues and untick what you do not want. Issues that already have an estimate are left out unless you clear that box. A session holds up to 100 issues.
Click Start session and share the address of the page with your team. Everyone who opens it joins.

Three ways to estimate

Way	When	How it goes
Planning poker	In a refinement meeting	One issue at a time. Everyone picks a card. The moderator reveals the cards, picks the result and moves on.
Async poker	When the team is not together	Everyone votes on all issues in their own time. The moderator closes the vote and picks the results.
Magic estimation	To size a large backlog quickly	One shared board with a column per card. Drag every issue to the column with its estimate.

Planning poker

Pick your card; click it again to take it back. Until the reveal you only see who has voted, not what. After the reveal you see every card, how often each card was picked, the average and median for number decks, and a consensus badge when everyone agrees.

The moderator picks the result (the middle card is suggested) and clicks Save in Jira and go to the next issue. Vote again starts a new round for the same issue; Skip moves on without a result. The moderator can jump to any issue in the list.

Async poker

Vote on as many issues as you like; your votes are saved right away. When the moderator closes the vote, everyone sees the votes. The moderator checks the suggested results, changes them where needed and saves them all at once. Open voting again lets people change their votes.

Magic estimation

Drag an issue to a column, or click an issue and then the head of a column. Everyone moves issues on the same board and sees the moves of the others. The moderator saves the board when the team is done.

Who can do what

Everyone who can open the app can start a session and take part in one.
The person who starts a session is its moderator. Jira administrators can moderate every session.
Estimates are written to Jira as the moderator. If the moderator may not edit an issue, or the field is not on the issue's screen, the app says which issues were not saved and keeps a Save in Jira button to try again.
Issue details are read from Jira as the person who looks. Someone without access to an issue sees its key, not its summary.

Closing and deleting

Close session ends voting and shows the results; Reopen undoes that. Delete removes the session with its votes. Sessions that nobody touched for 400 days are removed automatically.

Good to know

Up to 60 people can join one session.
"?" and the coffee cup are cards to say "I do not know" or "I need a break". They never count as a result.
For a number field, pick a deck with numbers. "½" is saved as 0.5.
Time cards such as 4h or 2d are saved in the original estimate, so time tracking must be on.

Data and privacy

The app runs on Atlassian (Forge) and has no external servers, analytics or cookies. It stores the sessions (name, issue ids and keys, cards, results) and the votes per person in Forge storage. Issue summaries are not stored. See the privacy policy and security.

Support

Email hello@bizzkitt.ai or see support. Bitwerf is a trade name of BizzKitt B.V., Frederikstraat 67, 3034 LD Rotterdam, the Netherlands (KvK 42149345, VAT NL869932354B01).