Scrum Poker by Eolivion
Scrum Poker by Eolivion lets your team estimate Jira issues together and saves the result to the issue. It runs inside Jira and makes no calls to outside servers.
Open it
- In a project: open the project and pick Scrum Poker by Eolivion in the project's navigation (it may be under More).
- All your sessions: Apps > Scrum Poker by Eolivion in the top bar lists sessions in every project you can see.
- On a single issue: open the issue and choose Scrum Poker by Eolivion: Quick Estimate from the apps button under the summary.
Start a session
Choose New session, give it a name and pick where the issues come from:
- Sprint: the open issues of an active or future sprint of a board.
- Backlog: the project's open issues that aren't in a sprint, in backlog order.
- JQL: any query, from any projects you can see.
- Team: the open issues of a Team, in any project.
- Issue keys: paste keys or issue links.
Up to 100 issues per session. While you play you can add, remove and reorder them.
Vote and reveal
Anyone in the project who opens the session can vote. Cards stay hidden until the person running the session reveals them, or until they reveal on their own once everyone present has voted (when that option is on). Then you see the spread, the average, the median and a suggested estimate.
Tick Just watching if you're there to follow, not to vote. Anyone can choose Run this session to take over from the facilitator.
Save to Jira
Pick the final estimate and choose Save and next. It goes to the field picked for the session: Story points (the one your board uses, detected per issue), Original estimate, Priority, or any number field.
If the field isn't on the issue's edit screen, the app still saves it, after checking that you're allowed to edit that issue. Jira keeps the value and the board, backlog and reports use it. To show it on the issue too, a Jira admin adds the field to that issue type's layout; the app tells you where.
Other ways to vote
- Async, by a deadline: everyone votes on each issue in their own time and can add a short reason. Cards open at the deadline, or earlier if you reveal them.
- Relative sizing: drag issues into size columns, comparing them with each other, then save them all at once.
- Priority: vote importance with MoSCoW, Jira priority or business value, and see the ranking in the summary.
- Two fields: after an issue's first estimate is saved, vote again for a second field with its own deck.
Decks
Fibonacci, modified Fibonacci, powers of 2, T-shirt sizes, or your own cards (up to 20). You can change the deck in the middle of a session; votes that weren't saved start over.
Help while estimating
- Details: the description, acceptance criteria, attachments and latest comments, right below the cards.
- Done issues for comparison: issues from the same project that got the same estimate.
- Summary: how many issues were estimated, how often the team agreed on the first vote, a CSV to copy, and your board's recent velocity.
- Ask Rovo: if your site has Rovo, an agent compares the issue with similar done work and suggests an estimate for the team to discuss.
Permissions and data
The app reads Jira with the permissions of the person using it, so nobody sees issues they can't already see. Sessions and votes are kept in Atlassian's own storage for the app; see the privacy policy for exactly what's kept and for how long.
Looking for the free edition?
Scrum Poker Free by Eolivion is a separate app with its own guide: Scrum Poker Free by Eolivion · Getting started.
Need help?
Open a request on the support portal.