What is Story Point Estimation?
Story point estimation is a collaborative technique used by agile teams to estimate the effort required to complete work items. Instead of estimating in hours or days, teams use abstract units called story points that represent the relative complexity, effort, and uncertainty of a task.
Why Story Points?
- Relative sizing – It is easier to say “this task is twice as hard as that one” than to guess exact hours
- Team calibration – Points are defined by the team, for the team, based on shared experience
- Velocity tracking – Over time, the team learns how many points they can complete in a sprint, enabling more accurate forecasting
- Reduced anchoring – Abstract units avoid the emotional baggage of time-based estimates
How Planning Poker Works
Planning Poker is a consensus-based estimation technique where team members privately select a card representing their estimate, then reveal simultaneously to avoid anchoring bias.
- A work item is presented for estimation
- Each team member privately selects a card value
- Votes are revealed simultaneously
- The team discusses discrepancies and may re-vote
- The final estimate is accepted and recorded
Scrumpy’s Role
Scrumpy automates this process inside Jira. It provides:
- Multiple estimation perspectives – Estimate the same work item from different angles (complexity, time, risk)
- Live voting – See votes appear as team members submit them
- Instant feedback – Changes you make appear right away, and if something cannot be saved the previous state returns
- Automatic result computation – Configurable averaging methods calculate the final estimate
- Certainty signal – A percentage that shows how often participants settled on their votes instead of re-voting
- Variation signal – A percentage that shows how widely the vote values are spread around their average
- Required voters and reminders – Choose who must vote and nudge anyone who has not
- Asynchronous voting – Let participants vote at their own pace, with an optional deadline
- Built-in chat – Discuss estimates and react to messages during a session
- Jira integration – Accepted estimates are written directly to your Jira board or custom fields
Getting Started with Scrumpy
This guide walks you through setting up Scrumpy for your team.
Step 1: Install the App
Scrumpy is installed from the Atlassian Marketplace. After installation, it appears as a panel on Jira work item pages and adds a settings page for your space.
Step 2: Configure Your Team
Open Space settings > Scrumpy Poker > Permissions and assign roles to your team:
- Moderators: people who start, manage, and complete voting sessions. Typically scrum masters, team leads, or product managers.
- Voters: team members who cast estimates during voting sessions.
- Guests: anyone who is not a moderator or a voter. Guests can watch sessions and see results, but they cannot vote or moderate.
By default, everyone with access to the space is a guest. You must give voting or moderating access explicitly. Moderators cannot vote by default; to let a moderator vote, add that person to the voters list as well.
You can also reset the space’s permissions, password, and configured Confluence space to defaults from this page. A confirmation appears first, and the reset cannot be undone. Perspective settings are reset individually from each perspective’s General tab.
Optional: Set a Password
You can protect a space with a password. When a password is set, anyone opening the Scrumpy panel on a work item, or the Space Estimations page, must enter it first. This restricts access without managing each user’s permissions. Passwords must be at least 4 characters, are stored in a scrambled form, and cannot be read back. You can change or remove the password at any time.
After you enter the password once, Scrumpy remembers it for your account for 30 days. The same entry unlocks both the work item panel and the Space Estimations page, so you are not asked again on either surface. The remembered entry expires after 30 days, and it is cleared when the password is changed or removed, at which point you enter it again.
Step 3: Set Up Perspectives
Perspectives define how your team estimates. Each perspective has its own voting rules, card sequences, and target Jira field.
Open Space settings > Scrumpy Poker > Settings to configure your perspectives. A Default perspective is created for you automatically, set up for Story Points estimation, and it cannot be deleted.
Step 4: Start Estimating
Open any Jira work item and look for the Scrumpy panel on the right side of the screen.
- As a moderator, click Start to begin a voting session
- As a voter, cast your estimate by clicking a card
- Once all required voters have submitted, the moderator accepts the result
Step 5: Use the Space Estimations Page
Open Space > Estimations. The page has these tabs: Getting started, Planning sessions, Active sessions, Dashboard, and a right-aligned Feedback tab. A support icon to the right of Feedback shows or hides the quick start guide. If a password is set, the whole page is locked until you enter it. The tab you last opened is remembered for the current browser tab, so a reload returns you to it.
Getting Started
An onboarding walkthrough that explains what estimation is and how to use Scrumpy.
Planning Sessions
Create and manage planning sessions to organize estimation work. See the Planning Sessions page for details.
Active Sessions
A sortable table of every voting session in the space. Click a column header to sort by type, work item, start time, ending time, perspective, state, or completion.
- Type and Work item: centered headers and cells. Work item cells have no leading space before the key.
- State and % complete: left aligned, minimum width, and the % complete header stays on one line.
- Voters: right aligned.
- Started: how long ago the session began.
- Ending: counts down the remaining time.
- Completion: shows a status tag.
Each row also lists the session’s voters by name in small text. Click an issue key to open the work item, where the Scrumpy panel has the voting controls. When there are no sessions, the tab shows an empty state instead of the table.
Moderators can act on several sessions at once: tick the sessions (or use the header checkbox to select all), then use the buttons below the table.
- Complete finishes a session that has real votes and cancels one whose votes are missing or are only extra emoji cards.
- Cancel stops the selected sessions, including completed ones.
- Accept writes the completed sessions’ estimates to Jira.
You do not choose a perspective because each row already names its own. If a write fails, an error dialog reports the affected work items. The buttons stay disabled until the selection contains a session in a matching state; Cancel is enabled for any selected session, started or completed.
On the right of the action row, the avatars show everyone who has voted in any of the listed sessions. Everyone sees this group, and it keeps its place before anyone has voted so the action row does not move when the first voter appears. The action buttons are moderator-only.
A bulk action changes the table right away: the row shows its new state or disappears, and the buttons enable or disable from the updated rows, so you cannot run the same action twice. There is no spinner, and if the change cannot be saved the previous rows return.
Dashboard
Three charts summarize current activity: active sessions by perspective, unique voters by perspective, and sessions by state per perspective. Below the charts, avatars show everyone who has voted, and that row keeps its place even before anyone has voted.
Feedback
The right-aligned Feedback tab lets you rate the app, suggest improvements, and contact the support team. See the Feedback and Support section for details.
Quick start guide
Above the tab list, a Quick start guide shows four steps to get going:
- Set up the space moderators and voters (open the space settings Permissions tab to do this).
- Create a planning session with an optional start and end time using Create new.
- Add Jira work items to the session from an existing Jira filter.
- Arrange the items in the order they will be estimated.
The guide is for new spaces, so it disappears on its own once a planning session contains a work item. Use the support icon in the tab bar to show or hide it again.
Adding Work items to Planning from the Work item View
When you view a Jira work item, open the Scrumpy panel and click Add to planning to add the current work item to an existing planning session, or create a new one on the spot. The panel remembers the planning session you used last on the space.
Filtering Work items with JQL
For advanced users who build Jira filters and boards, Scrumpy provides a custom JQL function, issuesInEstimation(), that returns the work items currently being estimated.
Parameters
| Parameter | Required | Description |
|---|---|---|
projectKey | Yes | The Jira space key (for example "PROJ") |
state | No | Filter by session state. Only "paused" and "completed" are recognized. Omit to include every state |
perspectives | No | Filter by one or more perspective names (for example "Points"). Names must match exactly, including case |
Values after projectKey are read by value: "paused" and "completed" select the state, and any other value is treated as a perspective name.
The function supports both in and not in JQL operators. It only returns work items the current user is allowed to see, so a shared filter shows each viewer the work items they can access.
Examples
issuekey in issuesInEstimation("PROJ")
Return all work items in space PROJ that have an estimation session in any state. This is the most common usage, for a board that shows the work items being estimated.issuekey in issuesInEstimation("PROJ", "paused")
Return work items in PROJ with a paused voting session. Useful for finding work items that need the moderator’s attention.issuekey in issuesInEstimation("PROJ", "completed")
Return work items in PROJ where voting has completed but the moderator has not accepted the result yet.issuekey in issuesInEstimation("PROJ", "paused", "Points")
Return work items in PROJ with a paused session in the Points perspective. You can list several perspective names to match any of them.issuekey not in issuesInEstimation("PROJ", "completed")
Return work items in PROJ that are not in a completed estimation session. Use not in to exclude work items from a filter or board.
Estimation Perspectives
A perspective is one way of estimating work. Each perspective has its own voting behavior, card sequences, and the Jira field where the final estimate is stored.
Why Multiple Perspectives?
Different estimation dimensions help your team look at work from several angles:
- Points: Relative complexity and effort
- Time: Hours or days of work
- T-Shirt Sizes: Coarse-grained sizing (XS, S, M, L, XL)
- Risk: Likelihood or impact of unknowns
Perspective Settings
Each perspective is configured through five sub-tabs: General, Voting, Cards, Estimation, and Backup & Restore.
General
The General tab holds the perspective’s name, optional description, and Work types. The name cannot be empty and must be unique in the space. Names are compared without regard to uppercase or lowercase, so Points and points count as the same name. If another perspective already uses the name, the field shows an error and the name is not saved until you change it. The name and description are displayed on the voting screen. You can limit a perspective to specific Work types (for example, show the Time perspective only for Bug and Task work items). When you create a perspective, all Work types of the space are selected by default; clear the ones that do not apply. If you select no Work types, the perspective appears for all work items.
If no perspective applies to a work item’s work type, the Scrumpy panel shows No voting perspective, names the work type, and asks you to configure the space’s perspective settings rather than showing an empty deck.
Below those fields, the General tab has three actions:
- Reset to defaults: Return the perspective to its initial settings, after a confirmation
- Cancel all sessions: Immediately cancel all active voting sessions for the perspective, after a confirmation. This cannot be undone, and all participants lose their current votes
- Delete perspective: Remove the perspective and all its sessions permanently, after a confirmation. The Default perspective cannot be deleted
Voting
| Setting | Description |
|---|---|
| Open voting | When on, participants see each other’s votes in real time |
| Certainty | Shows how often participants re-voted during the session, not how spread the votes are. One vote per participant gives 100% |
| Variation | Shows how widely the vote values are spread around their average. Lower is better, and it needs at least two numeric votes |
| Automatic completion | Off by default. Completes the session automatically when all required voters have voted. Paused sessions are not completed automatically, and at least one required voter must be set |
| Asynchronous voting | Participants vote at their own pace, without a countdown timer |
| Vote duration | Time limit in seconds for each voting round (10 to 180 seconds, default 60 seconds). A round that ends with no real estimate is cancelled instead of completed |
| Averaging | How votes are combined: Arithmetic mean, Geometric mean, Harmonic mean, Quadratic mean, Midrange, Median, Minimum, Maximum, Mode (most common), PERT, or Count |
The moderator can also try another method on a single completed result before accepting it, to compare outcomes, without changing the perspective’s saved setting. See Voting Session Controls.
Mean averaging
Scrumpy offers five mean-based methods:
- Arithmetic mean adds the votes and divides by the number of votes.
- Geometric mean multiplies the votes and takes the nth root.
- Harmonic mean divides the number of votes by the sum of their reciprocals.
- Quadratic mean squares the votes, averages the squares, and takes the square root.
- Midrange is halfway between the smallest and largest vote.
A zero vote makes the geometric and harmonic means zero. Every result is rounded to the nearest available card, like the other averaging methods.
PERT averaging
PERT (Program Evaluation and Review Technique) is a three-point estimation method. When you choose PERT as the averaging method and the team has cast at least three different values, Scrumpy takes the three points from the votes themselves:
| Point | Meaning |
|---|---|
| Optimistic (O) | The smallest value voted |
| Most Likely (M) | The average of every value strictly between the smallest and the largest |
| Pessimistic (P) | The largest value voted |
The estimate is the weighted PERT average:E = (O + 4M + P) / 6
The result is rounded to the nearest available card, exactly like the other averaging methods. Scrumpy also shows how spread out the three points are, as the Deviation:deviation = (P - O) / 6
While Open voting is on, the Optimistic (smallest) and Pessimistic (largest) votes are highlighted in the vote list, so the two extremes stand out. If the team voted fewer than three different values, PERT falls back to the arithmetic mean. The Deviation indicator follows the same rule as Certainty and Variation: it appears once the session is completed, or live while Open voting is on.
Count averaging
Count ignores the vote values: the estimate is the number of votes cast. The extra emoji cards carry no value and are not counted. The count is rounded to the nearest available card, exactly like the other averaging methods, so four votes on a deck without a 4 (for example Fibonacci) round up to 5.
Cards
| Setting | Description |
|---|---|
| Sequence | Choose the card set from the dropdown: Regular, Fibonacci, Tens, Fingers, Dice, T-Shirt, or Free Scale |
| Available cards | Which cards from the sequence appear to voters during a session |
| Card titles | The name shown for each card, built in per card and editable |
| T-shirt story points | The score each T-shirt card counts for. You can edit the number next to any T-shirt card. The numbers must keep growing from top to bottom |
| Extra cards | Fun cards for team morale (infinity, phoenix, cookie, buffalo, ping pong) |
| Custom images | Upload your own artwork for any individual card by clicking its preview in the Available cards or Available extra cards list. Images must be a PNG or JPEG file, up to 293 kB, with a width to height ratio of 1:1.5 (for example 400 by 600 pixels). Use the same dialog to remove a custom image and restore the built-in artwork |
| Free scale range | Custom minimum and maximum for free-form numeric estimation, with a preview slider that shows the value as story points or as hours |
| Story points to hours | How many hours one story point represents. You can enter a decimal value such as 1.5. A value that is not a number is rejected with an error and is not saved. This only changes how values are displayed, and it is hidden for the T-Shirt sequence |
Custom images are set per card and per sequence. The Available cards list shows the cards of the sequence selected in Sequence (Regular, Fibonacci, Tens, Fingers, Dice, or T-Shirt), and the Available extra cards list shows the fun cards, so you can give any individual card its own artwork without affecting the same card value in another sequence (for example, overriding “1” in Fibonacci leaves “1” in Tens untouched). Custom images are kept with the perspective and appear both in the settings previews and in the voting panel where voters pick their estimate.
Below the Available cards and extra cards sections, a note shows an example image and repeats the supported file types and limits. The example phrase is a link that opens the image in a new tab.
In the voting panel, the cards resize to fit a fixed four-row area. A short deck shows larger cards, and a full deck uses the standard card size, so the panel keeps the same height when you enable or disable cards. The extra cards shown below the free-scale slider stay compact.
Each card also has a title field beside its preview. Every card starts with a built-in playful title, such as “Low hanging fruit” for 1 or “When pigs fly” for infinity. Edit the field to give the card your own name for this perspective; the title appears in the settings preview and in the card’s tooltip in the voting panel. A custom title also replaces the estimate value that minimalistic card visuals would otherwise show in the tooltip.
Clearing the field shows an error because every custom title must contain at least one letter. Press the small reset control that appears beside an edited title to restore the built-in one.
Custom titles must also be unique within the card sequence; built-in titles are exempt because several intentionally repeat. Titles follow the card value, so sequences that contain the same value share a custom title, while custom images stay separate per sequence.
When you use the T-shirt sequence, a number appears beside each card title. This is the story point value that card counts for when Scrumpy calculates the result. Change a number to match your team’s scale. Each card must be higher than the card before it, so the numbers always form a growing sequence. To make bigger jumps, start at the bottom of the list and work upward. The card still shows its size label, such as M, during voting and in Jira.
To edit T-shirt story points:
- Open the perspective settings.
- Go to Cards.
- Choose T-Shirt in Sequence.
- In Available cards, change the number next to a card title.
Estimation Target
| Setting | Description |
|---|---|
| None | Estimates stay within Scrumpy and are not written to Jira |
| Default | Use Jira’s built-in board estimation (recommended). The first board is selected automatically, and a link opens the board’s estimation settings |
| Field | Write to custom Jira fields for story points, time tracking, or T-shirt sizes |
When you use the Field target, the fields shown depend on the sequence and conversion:
- T-Shirt Size: A text or select field for size labels. A T-shirt perspective can also choose a story points field; the accepted estimate is then written as the story point value mapped to the chosen card (for example, S = 10) instead of the size label. If you choose both fields, both are updated
- Story Points: A number field for story point values, shown for the numeric sequences and optionally for T-shirt perspectives
- Time: A time tracking field for hour-based estimates, shown only when Story points to hours is set to a non-zero value
With the Default target, a T-shirt estimate is written as the story point number you set for the chosen card. For a T-shirt perspective, the T-shirt field also appears right next to the Estimation board selector so the same accepted estimate can be written as its size label to that field as well.
With the Field target, choose a story points field to write that mapped number, a T-shirt field to write the size label, or both. The field controls are indented to line up with the board selector.
When a field no longer applies after you change the sequence or clear the conversion factor, it is hidden and its saved field selection is reset, so a later switch does not silently restore a stale field.
Backup & Restore
The Backup & Restore tab holds:
- Download: Download the perspective settings as a JSON file you can share. The file includes every setting except the estimation board, so it can be loaded into another space
- Load: Import a previously downloaded settings JSON file to apply it to this perspective. The target perspective keeps its own estimation board. The same file can be loaded into another perspective, including a perspective in another Jira space or another Jira site. Emoji and other non-ASCII card values survive the round trip. Files that are not valid settings are ignored
The download link is prepared when you open the tab and stays valid for one hour.
Managing Perspectives
In the space settings page, each perspective is a tab, and you can add more with Add new perspective. A new perspective starts with the name New view; rename it to a short, recognizable name. For each perspective you can:
- Reset to defaults (General): Return the perspective to its initial settings
- Cancel all sessions (General): Immediately cancel all active voting sessions for the perspective. This cannot be undone, and all participants lose their current votes
- Delete perspective (General): Remove the perspective and all its sessions permanently. The Default perspective cannot be deleted
- Download (Backup & Restore): Download the perspective settings as a JSON file you can share. The file includes every setting except the estimation board, so it can be loaded into another space
- Load (Backup & Restore): Load a previously downloaded settings file to apply it to this perspective. The target perspective keeps its own estimation board. The same file can be loaded into another perspective, including a perspective in another Jira space or another Jira site. Files that are not valid settings are ignored
Any change you make is shared with everyone viewing the Scrumpy panel right away, so they see the updated settings without refreshing. If a change cannot be saved, the setting returns to its previous value.
The space settings page remembers the outer tab, the perspective tab, and the perspective sub-tab you last opened for the current browser tab, so a reload returns you to the same view. The same applies to the Space Estimations page and the work item panel.
Chat and Communication
Every voting session includes a built-in chat panel for real-time team communication. The chat is shared with all planning session participants and persists for 24 hours.
When a work item has no messages yet, the chat shows an empty state that invites you to start the conversation. Messages are shared with the work item’s planning session participants.
Chat Features
- Rich text editing: bold, italic, links, lists, and code blocks
- Private messages: moderators and voters can mark a message as private
- Thumbs up/down: react to messages with voting buttons
- Edit and delete: authors can edit or delete their own messages
- Live delivery: messages appear instantly, no page refresh needed
Sending a Message
Write in the message box and press Send. Your message appears in the conversation right away and the message box clears at the same time, so you can keep typing without waiting for the server. The Send button never shows a spinner and never blocks you while the message is being saved.
If the message cannot be saved, it is removed from the conversation and your text comes back in the message box so you can try again. The same happens when an edit cannot be saved: the message keeps its previous text and stays open for editing.
Message Details
Each message shows its author, the author’s role (Moderator, Voter, or Guest), and the time it was sent. A message that has been changed shows an Edited tag, and a private message shows a Private tag. Only the five newest messages are shown at first; use Load more … to load the next five until the full history is visible.
Reactions
Every message has thumbs up and thumbs down buttons. Each reaction is a per-user count: clicking a button adds your reaction, and clicking the same button again removes it. Your reaction and the counts update right away. The pressed button shows a spinner and both reaction buttons are briefly unavailable while the change is saved, then become usable again. Counts also update for everyone right away. If a reaction cannot be saved, it is rolled back.
Editing and Deleting
You can edit or delete only the messages you wrote. Deleting a message asks for confirmation, since the action cannot be undone. The message disappears as soon as you confirm, without a spinner on either button. If the delete cannot be saved, the message comes back. Editing a private message keeps its privacy setting, and you can change that setting while editing.
Private Messages
The Private toggle is available to moderators and voters. Private messages are visible to moderators and voters only; guests can read public messages but cannot send or see private ones (unless they wrote the message). Guests always send public messages even if a private toggle is visible.
New Message Notifications
When a new message arrives while you are on another part of the panel, a red dot appears on the Chat tab. Guests are not notified about private messages.
When to Use Chat
- Discussing estimation discrepancies during a voting round
- Clarifying requirements before casting votes
- Note-taking and context sharing during planning sessions
- Quick polling with thumbs up/down reactions
Voting Session Controls
This page explains the moderator and voter controls available during a voting session.
Session Lifecycle
A voting session moves through these states:
- Inactive: No session is running. The moderator clicks Start to begin.
- Active: Participants cast votes. A progress bar shows the remaining time.
- Paused: The moderator can pause to discuss before continuing.
- Completed: All votes are in. The moderator reviews and accepts the result.
A timed round is completed by the server when its countdown ends, even when nobody has the work item panel open. If the round produced no real estimate, it is cancelled instead of completed. Votes made only with the extra emoji cards count as no votes.
Start, Pause, Resume, Cancel, and Complete take effect right away. If an action cannot be saved, the panel returns to the previous state. A delayed update from an earlier session never affects a newly started one.
Voting Card Sequences
Scrumpy supports seven card sequences, set per perspective. The full deck of a sequence is listed below; the Available cards setting can narrow it to a subset.
| Sequence | Cards |
|---|---|
| Regular | 0, 0.5, 1, 2, 3, 5, 8, 13, 20, 40, 100, 200, … up to 700 |
| Fibonacci | 1, 2, 3, 5, 8, 13, 21, 34, 55, 89, 144, 233, … up to 2584 |
| Tens | 0, 10, 20, 30, … up to 160 |
| Fingers | 0 through 16 |
| Dice | 1 through 18 |
| T-Shirt | XS, XS/S, S, S/M, M, M/L, L, L/XL, XL, XXL, XXXL, A, B, C, D, E, F |
| Free Scale | Any integer between a configurable minimum and maximum |
T-shirt cards have an editable story point value beside each card title in the perspective settings. Scrumpy uses these values when it calculates the result, so you can match the sizes to your team’s own story point scale. The values must always grow from the first card to the last, and the final result still appears as the size label.
The highest values in the Regular (200 to 700) and Fibonacci (233 to 2584) sequences have no dedicated illustration. Their cards use the built-in lettered fallback artwork instead, while the tooltip still shows the number.
For Free Scale, voters use a slider to pick any number in the defined range instead of clicking fixed cards. Moving the slider only updates the preview; the vote is cast by pressing the Vote button below the slider. Once a vote is recorded, a Withdraw button appears beside it, and pressing it removes the vote (the same as removing a card vote).
Extra cards are optional fun values (infinity, phoenix, cookie, buffalo, ping pong) that appear after the regular deck when you enable them in the perspective settings. Hovering a Regular or Fibonacci card shows a playful label such as “Piece of cake” or “When pigs fly”. With minimalistic card visuals, the tooltip shows the estimate value instead of the playful label. A custom card title, set per card in the perspective’s Cards settings, replaces both the playful label and the estimate value in the tooltip. Custom titles must contain at least one letter and be unique within the card sequence, including against the built-in title of another card. Typing a card’s built-in title removes the custom title and restores the default.
Perspective Tabs
Each perspective appears as a tab above the voting stage. Hovering a tab shows the state of that perspective’s session: “No voting session yet” when idle, or how many voters have already voted and how much time is left when a session is active.
In the Planning Sessions tab, the moderator’s selected perspective tab (including Chat) is shared with everyone in the planning. Participants who are locked to the moderator follow it. If you click another tab, the lock turns off and your own tab is remembered for the current browser tab.
A yellow M badge marks the tab the moderator is viewing while the moderator has the same work item selected, even when it is the tab you are on. The badge is hidden when you have unlocked and focused a different work item. In the work item issue panel, the tab you last opened, or the Chat tab, is remembered for the current browser tab.
Below the tabs, the perspective’s description appears in bold; when it has no description, No description is shown. The small gear beside it opens that perspective’s settings in a new tab.
When you open the work item panel and its voting session belongs to a planning session, a small line below the description says so, and the words planning session link to it. The line stays visible after the session completes. The link opens the space page with the planning session selected, in a new browser tab. The line is not shown in the Planning sessions tab, where the planning session is already open.
If no perspective applies to the work item’s work type, the panel shows No voting perspective with the work type name and asks you to configure the space’s perspective settings.
Link to the Space Page
Above the perspective and chat tabs, a short note invites you to try the space page for the full planning session experience when the work item is not already part of a planning session. Click space page to open it in a new tab, or choose Dismiss to hide the note. Once dismissed, it stays hidden for the rest of your browser tab session, and it does not appear in the planning sessions tab.
Moderator Controls
Start
Begins a new voting session for the current perspective. All eligible voters can now submit their estimates.
Pause / Resume
Temporarily stops the session. This is useful for team discussions when votes differ a lot. The stopwatch is suspended while paused, and the panel shows who paused the session. Asynchronous sessions cannot be paused or resumed.
Cancel
Ends the session entirely. All votes are discarded and the session is removed.
Complete
Ends voting and reveals all submitted votes. The result is computed using the configured averaging method. If the session produced no real estimate (no vote, no vote matching an active card, or only extra emoji card votes), it is cancelled instead, whether the moderator completes it or a timed round ends on its own.
Accept
Finalizes the estimate. Writes the result to Jira (according to the perspective’s estimation target) and saves the session in the estimation history.
While the write is in progress the panel shows “Updating estimation fields, please wait…”. Before accepting, the moderator sees “Cancel to reset or accept to update work item.”, while voters see “Waiting for the moderator to accept the result.”. If the estimate is accepted but cannot be written to Jira, an error dialog reports the affected issue key.
Set Estimate
Before accepting, the moderator can set a different estimate. Card sequences show an Override final result dropdown of the available values, and Free Scale shows a number field bounded by the configured minimum and maximum. When the perspective converts story points to hours, the converted duration appears as a badge after the number field. This is useful when the team’s discussion leads to a consensus that differs from the averaged result.
Beside it, the Override averaging method dropdown lets the moderator recalculate the result with a different method for the current session only. It starts on the perspective’s configured method. Choosing another method immediately recomputes the estimate from the submitted votes and updates the override field, so you can compare how different methods read the same votes. The perspective settings do not change, and the next session starts from the configured method again. After recalculating, you can still fine-tune the value by hand.
Remind
The moderator can send a reminder to participants who have not voted yet. The reminder control appears only while there are unvoted participants and no reminder has been sent for the current round. It disappears as soon as you send the reminder, without a loading wait. Each reminder is recorded in the voting audit. If sending fails, the control appears again so you can retry.
Required Voters
The Who is required? control opens a participant picker where the moderator chooses who must vote before the session can complete. By default every configured voter is required. Non-moderators can open the same control to see who is required, but they cannot change it. When all required voters have submitted, the session completes automatically if automatic completion is on.
Voter Controls
Voters see a set of cards matching the perspective’s sequence and active cards. Clicking a card selects it right away. Clicking the selected card again removes your vote, so a vote can be taken back as well as cast. The change is recorded in the voting audit. In open voting, all votes are visible in real time. In closed voting, votes stay hidden until the session completes. Only voters can cast a vote: a moderator who is not also in the voters list cannot click a card, and the server rejects the vote as well.
Each click is saved as soon as you make it, and the card changes immediately. You can change your pick at any time. If you click again while an earlier change is still saving, the newest choice is the one that is sent next. If saving fails, the card returns to the last confirmed vote. Free-scale voters use the Vote and Withdraw buttons below the slider for the same cast and remove actions.
Ranking Above the Cards
If a work item has already been ranked in the space page’s alternative voting, the voting panel shows a centered rank above the cards:
- Affinity rank for the work item’s affinity position
- Dot rank for the number of dots the work item has
Each line reads like “Affinity rank is 3 out of 10 or 30%”. The rank is calculated live from the planning session’s rankings, so it follows every rerank and dot. A line appears only when the work item has that rank, so an unranked work item shows nothing, and both lines appear together when a work item has both rankings. A ranking does not disable the cards; voters still vote normally in the panel.
When the moderator enforces a ranking in the Bucket voting panel of the work item’s planning session, a dismissable informational message above the cards tells you that your vote may count for several work items. If your vote changes more than one voting session, the message is replaced by a dismissable message that lists the affected work items. Each work item opens its Jira issue view.
Panel Header Controls
The voting panel header has two controls:
- Sound toggle: mutes or unmutes sound notifications. This is a quick toggle, separate from the volume slider in your Personal settings.
- Your role badge: shows M for a Moderator who cannot vote, M/V for a Moderator who is also a Voter, V for a Voter, or G for a Guest. Hover it for a tooltip that states the current role, and click it to open the permissions settings.
Viewing Results
When a voting session completes, the results are shown in a chart. Three chart types are available (set in your Personal settings):
- Pie: Circle chart showing vote distribution
- Vertical bar: Bar chart for comparing vote values
- Horizontal bar: Bar chart with readable labels
The result also shows the computed estimate using the perspective’s averaging method. With the Count averaging method the estimate is the number of votes cast, ignoring their values and not counting the extra emoji cards, rounded to the nearest available card. When open voting is on, the results also list each individual vote next to the computed average, marked with a tilde. When the PERT averaging method is selected and at least three different values were voted, the result also shows the deviation, and the smallest and largest votes are highlighted in that list (see Perspectives). Before accepting, the moderator can recalculate the result with a different averaging method or override it by hand (see Set Estimate).
Certainty, Variation, and Deviation
Optional indicators help you read a result. Certainty and Variation are set per perspective in the Voting settings; Deviation appears automatically when PERT applies.
- Certainty reflects how often participants re-voted within the session, not how spread the votes are. When every participant votes exactly once, certainty is 100%, and each extra vote a participant casts lowers it. Certainty is green at 75% or above, yellow from 50% to 74%, and red below 50%.
- Variation measures how widely the vote values are spread around their average. Lower is better. Variation is green at 15% or below, yellow above 15% and up to 30%, and red above 30%. It uses the numeric votes, so it needs at least two numeric votes to appear: T-shirt sizes use the story points you set for each card, and the extra emoji cards are not counted.
- Deviation is how spread out the PERT three points are:
(P - O) / 6. It appears only when the PERT averaging method is selected and at least three different values were voted. While open voting is on, the Optimistic (smallest) and Pessimistic (largest) votes are highlighted in the vote list.
In short, certainty tells you whether participants settled on their votes, variation tells you whether the votes agreed on a value, and deviation tells you how confident the PERT estimate is.
Certainty, Variation, and Deviation appear once the session is completed. When open voting is on, they also appear live while the session is running.
Participant List
During a voting session, the participant panel shows the avatars of everyone who has voted, with a percentage and count of how many of the required voters have voted. While a session is waiting to start, the panel instead shows the avatars of participants who have not yet voted.
Voting Indicators
After casting a vote, you see an Already voted confirmation. If the session uses closed voting (open voting off), you see a Waiting for others indicator while other participants finish voting, keeping estimates hidden until the session completes. When the moderator sends a reminder, unvoted voters see a Please vote! indicator in their own panel.
Asynchronous Voting
When asynchronous voting is on:
- Participants vote at their own convenience
- The moderator collects results when ready
- Sessions cannot be paused or resumed
- There is no countdown timer or progress bar unless a deadline is set
Voting must complete until
Async sessions have no fixed voting window, so the moderator can set a deadline. While a session is active and not yet completed, moderators see a Voting must complete until control with a date picker and a time picker:
- The date cannot be in the past, and times are offered in 30-minute slots.
- Choosing both a date and a time sets the deadline.
- Once set, a progress bar and a countdown appear, and the session completes when the deadline is reached.
- Clearing either the date or the time removes the deadline and hides the countdown again.
The control is visible only to moderators, and only while the session is not completed.
Password Protection
If the moderator has set a password in space settings, anyone opening the Scrumpy panel must enter it before reaching the voting interface. This is a simple access gate that does not require managing each user’s permissions. The password is stored in a scrambled form and cannot be read back, only changed or removed. After you enter it once, Scrumpy remembers it for your account for 30 days and shares it with the Space Estimations page, so you do not have to enter it again on either surface. The remembered entry is cleared when the password is changed or removed.
While a password is set, the Permissions tab shows a warning message that the space’s voting sessions are protected, with Remove protection and Dismiss actions.
Team Information
The Team panel in the Scrumpy sidebar shows how many moderators and voters are set for the space, so everyone can see who can start sessions and who can participate. It shows counts rather than names.
Your Role
The Scrumpy voting panel header shows a badge with your current role: M for a Moderator who cannot vote, M/V for a Moderator who is also a Voter, V for a Voter, and G for a Guest. Hover it for a tooltip that states your role. The badge is a link to the Space settings > Scrumpy Poker permissions, where a space administrator assigns the roles; when the permissions change, the badge updates in real time without a refresh. A moderator can vote only when also added to the voters list.
When a voting session is active and you cannot vote, the panel shows a note below the perspective description: it explains that you must be in the voters list to cast a vote and links the words voters list to the Space settings > Scrumpy Poker permissions in a new tab.
Personal Settings
Personal settings let each team member customize their Scrumpy experience. These settings are stored per user and follow you across all spaces.
Changes apply immediately and are synced to your other open panels right away. If a change cannot be saved, the setting returns to its previous value.
Chart Type
Controls how voting results are visualized after a session completes. The default is Pie.
| Option | Best for |
|---|---|
| Pie | Quick glance at vote distribution |
| Vertical bar | Comparing individual vote values |
| Horizontal bar | Reading vote labels comfortably |
Card Visuals
Adjusts the appearance of voting cards in the estimation panel. The default is Colorful.
- Colorful: Bright, visually distinct cards with gradients
- Minimalistic: Subdued, flat design for less visual distraction. Cards show the estimate value instead of a playful label
Choose minimalistic if you find colorful visuals distracting during focused estimation sessions.
Sound Volume
Controls the volume of audio notifications, from 0% to 100%. The default is 50%. Scrumpy plays sounds for key events:
- Vote: When another participant casts a vote
- Start: When the moderator starts a voting session
- End: When the voting session reveals results
- Reminder: When the moderator sends a reminder to unvoted participants
- Message: When a new chat message arrives
Scrumpy does not play a sound for your own action. For example, you hear the vote sound when someone else votes, and the message sound for incoming messages, not for the one you just sent.
Set the volume to 0% to mute all sounds. Your preference is remembered across sessions. The voting panel header also has a quick mute toggle that turns sound on or off without changing this volume.
Resetting
You can reset all personal settings to their defaults from the Personal settings panel. A confirmation appears first, and the reset cannot be undone.
Audit Logs and Dashboard
Scrumpy maintains two separate audit trails for full transparency and compliance. Every timestamp in the audits, dashboards, chat, and estimation history is shown in your Jira timezone.
Voting Audit
The Voting Audit tab shows a chronological log of all significant events that occurred in voting sessions for the space.
Events recorded include:
- Session created, voted, paused, resumed, completed, cancelled
- Estimate set or modified by the moderator
- Required voters updated
- Async complete-until deadline set or cleared
- Estimate accepted and written to Jira
- Reminders sent to unvoted participants
Each event shows:
- Occurred: Timestamp of the event
- Type: Work type icon for the work item
- Work item: Clickable issue key that opens the work item in a modal
- Perspective: Which estimation perspective was used
- Actor: The user who triggered the event
- Description: Human-readable summary of what happened
Enter a search term and click Search to filter by event type, participant, or other details. Choose 15, 30, 45, or 60 rows per page, and use the pagination controls to browse large histories.
Use the Delete audit log action to delete all voting audit entries for the space. A confirmation dialog appears first, and the deletion cannot be undone.
Configuration Audit
The Configuration Audit tab tracks every change made to space permissions and perspective settings. Each entry records:
- Who made the change
- What was changed (with a human-readable description)
- When the change was made
- Which perspective was affected (if applicable)
Like the voting audit, this table is searchable with a Search button, paginated with the same page-size selector, and can be fully cleared with the Delete audit log action.
Dashboards
Scrumpy has two dashboards with different purposes.
Space Settings Dashboard
The Dashboard tab in Space settings provides the full analytics view. Use the range selector to choose 1, 2, 4, or 8 weeks, or All time. Your choice is remembered for next time. All time is still limited to the 90-day retention window, and the charts update as new estimates are accepted.
Charts shown:
- Total votes per perspective (donut)
- Total estimates per perspective (donut)
- Average certainty per perspective (bar)
- Average variation per perspective (bar)
- Average duration per perspective (stacked active and paused time, shown in seconds or minutes)
- Total estimates per day (line)
- Average voters per day (line)
- Average certainty per day (bar)
- Average variation per day (bar)
- Total duration in minutes per day (stacked)
You can delete all accepted session records with Delete estimation log at the bottom of the tab. A confirmation appears first, and the deletion cannot be undone.
Estimations Page Dashboard
The Dashboard tab on the Space Estimations page is a lighter, live overview with three charts and no time filter or delete action:
- Active Sessions by Perspective
- Unique Voters by Perspective
- Sessions by State per Perspective
Each chart shows its own empty state when there is nothing to display. Below the charts, avatars show everyone who has voted in any active session. The avatar row keeps its place even before anyone has voted, so the charts do not move when a participant appears.
Data Retention
Scrumpy keeps voting audit entries, configuration audit entries, accepted estimates, and planning sessions for three months (90 days). Older data is removed automatically every day. Chat messages are kept for 24 hours. You can also delete all audit entries or estimation log data at once from their respective tabs; those deletions cannot be undone.
Planning Sessions
Planning sessions group related work items for organized estimation. They help you prepare for sprint planning by collecting work items and tracking estimation progress across perspectives.
Creating a Planning Session
From the Planning Sessions tab on the Space Estimations page:
- Click Create new.
- Enter a title, such as “Sprint 42”. Each title must be unique per space. A title is required: if the field is empty or contains only spaces, it is marked in error and a message tells you that the name of the planning session is required.
- Optionally add a description, a start date and time, and an end date and time. You can pick a date and type any time, or choose a suggested time step of 10, 15, 30, or 60 minutes to change which times the picker suggests. A typed time is always kept, whatever step you choose. Past dates and times are allowed. A start date and an end date must be set together: if only one is set, the missing date field is marked in error and Create stays disabled. The end must be later than the start: if it is not, the end field is marked in error with a message and Create stays disabled. Create also stays disabled while the title is empty or contains only spaces.
- Click Create. The dialog closes right away and the new planning session appears in the list immediately. If it cannot be saved, it is removed again.
Only moderators can create planning sessions. With no sessions yet, moderators see a prompt to create the first one, while non-moderators see an informational message that explains how a space administrator can assign roles from the space settings Permissions tab. Each planning session appears as its own tab, and a newly created session is focused automatically. The planning session tab you last opened is remembered for the current browser tab, so a reload returns you to it.
Planning sessions are kept for three months (90 days) after their last change and are removed automatically after that.
Editing and Deleting
Click Edit on a planning session to change its title, description, or date range. Changes appear for everyone viewing the Space Estimations page without a refresh. The dialog closes as soon as you confirm, and the change shows in the list right away. If the change cannot be saved, the previous values come back.
The title is required: if you clear it, the field is marked in error, a message tells you that the name of the planning session is required, and Apply does not save the change. A start date and an end date must be set together: if only one is set, the missing date field is marked in error and Apply stays disabled until both are set or both are cleared. The end must be later than the start: if it is not, the end field is marked in error with a message and Apply stays disabled. The start and end rows each offer the same 10, 15, 30, or 60 minute suggestions, and you can type any time.
There is no separate delete action. To remove a planning session, use Complete, which removes it and all of its items permanently after a confirmation. See Completing a Planning Session.
Adding Work Items
You can add work items to a planning session in two ways.
From the Work Item View
Open a Jira work item, open the Scrumpy panel, and click Add to planning. You can also open the same dialog from the work item’s more actions (…) menu by choosing Add to planning. The dialog preselects the planning session you used last on this space; when the space has no planning sessions, Create new is selected instead. Choose another existing session, or choose Create new to create one inline with a title and description; a title is required before the item can be added. A work item can belong to only one planning session in a space. If it is already in the selected session, you are told that it is already there. If it is in another session, you are told which one and it is not added; remove it from that session first. The dialog closes after the item is added.
Add from Jira Filter
Click Add from filter to import work items from a saved Jira filter. The picker groups favourited filters under Favorite, your own filters under My filters, and shared filters under their owner’s name; favourited filters show a star. Select a filter to preview its work items, tick the ones you want, and add them. You can create filters on the Jira filters page. A planning session can only hold work items from its own space, so any work item from another space cannot be added.
In the preview you can:
- Tick individual work items, or use the header checkbox to select all selectable ones.
- Reorder rows by dragging them. The ticked items are added in the order the preview shows.
- See Type, Work item, Status, and Summary columns. The Type and Work item column headers and all their cells are center aligned. A warning-colored status icon in the Status column marks work items that cannot be added. Hover the icon to see why: it is not from this space, it is already in this planning session, or it is already in another planning session in the space, and the tooltip names that session.
Add stays disabled until you select at least one work item.
Managing Items
- Drag and drop: Reorder items by dragging rows (moderators only). Everyone sees the new order right away, without a reload, and the perspective rows stay below the work items.
- Select: Tick the checkboxes to select items for bulk actions.
- Highlight: Use the radio button to select a work item for estimation. It loads into the Voting Panel on the right, so you can estimate directly from the planning table.
The Type and Work item columns in the planning table are center aligned. The affinity and dot ranking columns, when they appear, are center aligned as well.
Edit mode
The Edit mode dropdown to the right of the session description chooses how voting is driven: Single voting (the default) or Bulk voting. A moderator changes the shared mode, and it appears for everyone right away, so every participant follows the same mode. A voter can also change the mode. That change applies only to that voter, unchecks Lock to moderator, and is remembered for the current browser tab. Checking the lock again returns the dropdown to the moderator’s current mode. The moderator’s mode is saved with the planning session. A voter’s local mode is not shared and does not change what the moderator sees.
Who is highlighted
Moderators pick the highlighted work item for everyone, and the selected row shows a yellow M with the tooltip “Work item currently selected by the moderator”.
In bulk mode a moderator can instead select a card-based perspective row, which opens alternative voting for it. That selection is also shared, and it replaces any selected work item. Other participants see the same yellow M in the first column of that perspective row, with the tooltip “Perspective currently selected by the moderator”.
The selected perspective is also the perspective tab of the inline voting panel, so highlighting a work item opens that tab. Participants who are locked to the moderator follow the moderator’s tab, and a yellow M badge marks it, even when it matches the tab they are on. The badge is shown only while the moderator’s selected work item is the one being shown; it is hidden when an unlocked participant focuses a different work item.
By default, other participants follow the moderator’s work item selection, edit mode, and alternative-voting tab. A Lock to moderator checkbox (on by default) controls this.
If you pick a row, switch the edit mode, or open another alternative-voting tab yourself, the lock turns off and your choices are remembered in this browser tab only. They survive a reload but are not shared with anyone else and do not change what the moderator sees. The lock setting also survives a reload.
Turn the lock back on to follow the moderator again; the edit mode dropdown and the alternative-voting tab then return to the moderator’s current choices.
Bulk actions
Below the table, a Perspective select (disabled until you tick at least one work item) chooses which perspective the session actions apply to, followed by icon-only actions. Each action has a tooltip stating that it applies to the selected work items. The chosen perspective and the ticked work items are remembered for the current browser tab, so a reload restores them.
| Action | What it does |
|---|---|
| Start | Opens voting sessions for the ticked items in the chosen perspective |
| Complete | Completes their started sessions. A session with no votes (no real estimate) is cancelled instead, matching the voting panel’s Complete button. Votes made only with the extra emoji cards count as no votes |
| Cancel | Cancels their voting sessions, including completed ones |
| Accept | Accepts their completed sessions and writes the estimates to Jira. The estimate appears in the perspective column right away. If the Jira write fails, the session and the column return to their previous state and an error dialog explains why |
| Remove | Removes the ticked items from the planning session |
An action is disabled when no ticked work item applies: Start when every session has already started, Complete when there is no started session, Cancel when no ticked item has a session, Accept when there is no completed session, and Remove until something is ticked. Removing the highlighted item clears the highlight.
Each action takes effect in the table immediately. The rows are added, completed, or removed right away, and the buttons enable or disable from those updated rows, so the same action cannot run twice. There is no spinner. If the change cannot be saved, the previous rows return.
After a drag or a bulk removal, the table updates right away. The change is confirmed in the background, and if the write fails the previous order returns.
Bulk Voting
Anyone can switch the Edit mode from Single voting to Bulk voting. A moderator changes the shared mode, and a voter switches locally. In bulk mode, the planning table keeps all of its rows and buttons, and its perspective cells become voting controls, so the description, the Edit mode dropdown, the buttons, the progress bar, and the estimation panel all stay in place.
A perspective cell shows a voting control only when that work item has a started session in that perspective:
- A clearable dropdown of the deck’s cards (for example “2 SP” or “XXL”), with the extra cards grouped under an Extra cards heading, preselected with your current vote.
- A number field bounded by the perspective’s minimum and maximum for free scale perspectives. When the perspective converts story points to a duration, the field shows the value in story points with an “SP” suffix and a short duration such as “1d 4h”. A free scale that does not convert story points stays a small number field with no suffix.
Changing a control casts your vote for that work item and perspective. The value appears right away and is saved in the background. If the save fails, the control returns to your previous vote. In a free scale field, type the number and then click away to save it. Clearing the dropdown (or emptying the number field) removes your vote, exactly like clicking the same voting card again. When a session completes or is cancelled, its voting control disappears and the cell returns to its usual state or estimate.
Until you vote in a cell, the control shows the work item’s current estimate as a placeholder, or Vote when there is none, and the control is marked as needing a vote. Choosing a value clears that hint.
Perspective rows and ranking columns
In bulk mode the table also lists one selectable row per card-based perspective (any sequence other than Free scale) below the work items. Each row has a checkbox, a radio to select it for alternative voting, and the perspective name. These rows always stay at the bottom: they cannot be dragged, and a work item cannot be dropped on or below them.
While a perspective has rankings, its row shows a regular Affinity badge and a regular Dot badge for everyone, one for each ranking the perspective has. A perspective with no rankings shows no badges. Rankings are cleared from the Affinity and Dot panels: the affinity Clear rankings button clears affinity only, and the dot one clears dots only. If the cleared ranking was the enforced ranking for the bucket table, the bucket ranking mode also returns to No ranking. The rankings disappear right away; if the clear cannot be saved, they come back.
A perspective that has affinity rankings is followed by an affinity ranking column, and one that has dot rankings by a dot ranking column, each shown when that ranking exists. Each work item’s value is a badge: its affinity position, or its dot count (0 when it has no dots). The ranking column headers and badges are center aligned.
Alternative Voting
Selecting a perspective row opens alternative voting for that perspective in place of the work item voting panel. A perspective row and a work item row cannot both be selected: selecting a perspective row clears the selected work item.
The perspective you last opened in alternative voting and the Vote or Results sub-tab are remembered for the current browser tab. While Lock to moderator is on, the outer tab (Affinity, Dot, or Bucket) follows the moderator’s current tab. The moderator’s tab is saved with the planning session and appears for everyone right away.
A yellow M badge marks the tab the moderator is viewing while the moderator has the same perspective open, even when it is the same tab you are on. It is hidden when the moderator has selected a work item or another perspective. If you click another tab, the lock turns off. Clicking the moderator’s tab again does not change the lock. Checking the lock returns you to the moderator’s tab.
The panel has three tabs: Affinity, Dot, and Bucket. Each tab shows the perspective title in bold, its description, and the settings gear link above its table. All three tabs list only the work items that apply to the perspective and have a started voting session. To the right of the Bucket tab, the panel shows the same role badge and sound bell as the voting panel: the badge links to the Permissions settings, and the bell toggles sound notifications.
Cancelling or accepting a work item’s voting session removes it from both rankings for that perspective. Starting a new session for the item adds it back unranked, at the end of the affinity order and without a dot.
Affinity
Affinity ranks the work items. It has two sub-tabs, Vote and Results: Vote holds the table and all the controls, and Results shows a bar chart of the ranking.
To the right of the perspective title, a moderator sets the ranking algorithm: Mean rank (averages the participants’ rankings) or Median rank (uses the middle of their positions). Only a moderator can change it, and the choice is shared live. If the change is refused, the selector returns to the last saved algorithm.
On the Vote tab, only voters can drag, and the table is read-only for everyone else. Drag a row to change its position. A short hint above the table reminds voters to drag work items; it disappears for you once you have submitted a ranking.
The table shows these columns:
| Column | Meaning |
|---|---|
| Type | Work type icon |
| Work item | Issue key |
| My rank | Your own position (1 for the top row), shown in a plain badge |
| Deviation | The gap between your rank and the group rank (your rank minus the group rank), shown as a signed number. It is a plain badge below 1, yellow below 2, and red otherwise |
| Rank | The work item’s shared position (1 is best), computed with the selected algorithm. The header and cells are right aligned |
Until you submit a ranking, the My rank and Deviation cells stay empty. They fill in when you rank, and clear again when you withdraw.
The Type, Work item, My rank, and Deviation column headers and all their cells are center aligned. Every displayed work item takes part, even when no one has rearranged it.
Your ranking is saved as you drag and shared live, so the other participants see the new order. Your own order is remembered per planning session and perspective, so a reload restores it, and it also follows you into your other open windows.
Below the table you see the participants who have submitted a ranking. The participants group updates right away as you rank or withdraw, without waiting for the server. A voter can withdraw their own ranking with Withdraw, which returns the table to the work item order and removes their ranking from the consensus right away. A moderator can clear all affinity rankings with Clear rankings, shown only while rankings exist. The participant row and the Clear rankings button appear once someone has ranked. If affinity was the enforced ranking, clearing it also returns the bucket ranking mode to No ranking.
The Results tab shows a horizontal bar chart of each work item’s position, best at the top. It is read-only.
Dot
Dot ranks the work items by dots. It has two sub-tabs, Vote and Results: Vote holds the table and the controls, and Results shows a horizontal bar chart of each work item’s total dots, lowest at the top, with no controls.
A moderator sets the dot budget below the table. A per-participant budget is between 1 and the number of work items, because each participant can dot a work item once. A shared budget has no upper limit: it can be any number at least the dots already placed.
Tick Share this budget between participants to make it one shared pool given first come, first served. The budget is not shared by default, so each participant gets the full budget. Everyone sees the same budget; non-moderators see only how many dots remain.
Your own budget change appears at once; if the server refuses it, the number field and the sharing checkbox return to the last saved values. If you change the number quickly, the field keeps your latest value instead of flickering back to an earlier one. A late update never replaces a newer budget, and a budget change and a ranking change do not overwrite each other. If you switch to a shared budget that is lower than the dots already given, all dot rankings are reset and a dismissable message tells you why.
Each work item can hold at most one dot per participant. Clicking an unvoted row’s dot spends one of your dots, and clicking a dotted row gives it back.
The table shows Type, Work item, Dot, and Rank columns. No column is sortable and the rows cannot be dragged. The Type, Work item, and Dot column headers and cells are center aligned, and the Dot header shows the medium stroke-weight dot icon instead of the word. The Rank header and cells are right aligned. The Type, Work item, and Rank columns use the planning table’s minimum widths:
- Dot holds a small button with a dot icon. Click it to place your dot, click again to remove it, returning the dot to the budget. It is disabled once your budget is empty and the work item has no dot.
- Rank is the total number of dots the work item holds across all participants.
- Withdraw clears your dots and returns your whole budget.
A short hint above the table reminds voters to place dots; it disappears for you once you have dotted a work item. If the shared pool is already used up by other participants when your dot reaches the server, the dot is not kept: it disappears from the table, your dots return to the last saved selection, and a dismissable informational message saying the shared dot budget is exhausted replaces the hint.
The number field cannot be set below the dots already given: its minimum is the dots the participant with the most dots has given, or the whole placed pool when the budget is shared. Switching to a shared budget below the placed dots resets all dot rankings instead.
The dots left are shown in a badge colored by how many remain: grey above half, yellow above a quarter, and red otherwise.
A moderator can clear all dot rankings with Clear rankings beside Withdraw, shown only while dot rankings exist. If dot was the enforced ranking, clearing the dot rankings, including the reset when switching to a shared budget, also returns the bucket ranking mode to No ranking. The rankings disappear right away; if the clear cannot be saved, they come back.
The participants who have dotted a work item are shown below the table, and that row keeps its place before anyone has dotted, so the budget controls and description do not move when the first dot appears. The group updates right away as you dot or withdraw, without waiting for the server.
Bucket
Bucket groups the work items under the cards as buckets. Only the perspective’s enabled cards are shown: the active cards of its sequence plus the enabled extra cards. An Unassigned row at the top holds the work items you have not voted on in this session. A short hint above the table reminds voters to drag a work item under a card; it disappears for you after your first drop.
A work item you have voted on in this session starts under the card matching your vote; a vote stored before the session does not affect where it starts. When your vote arrives, the work item moves under its card without dragging, and removing your vote returns it to Unassigned. Drag a work item under a card row to vote for that card, and drop it under Unassigned to clear the vote. The move appears right away and is saved in the background. If the save fails, the work item returns to the card it was under before the drop. A voter can withdraw all of their votes for the items in this panel with Withdraw below the voters group. The items return to Unassigned right away, and the button is disabled once the voter has no votes left in the panel.
Each card row shows the card image at 32 pixels high in the Type column, its label in bold in the Work item column (story points with the ” SP” suffix, T-Shirt sizes with their size), and the card name in regular text left aligned in the Participants column (the configured title, or the built-in playful title such as “Low hanging fruit” for 1 SP). The Type and Work item column headers and every cell in those columns are center aligned. The Unassigned row shows the archive-box icon in the Type column, center aligned. Card and Unassigned rows are highlighted and cannot be dragged, and the Unassigned row shows its label in the Work item column. The Participants column also shows each work item’s vote progress, for example “33% or 1 out of 3 already voted.”. The participants row below the table keeps its place before anyone has voted, so the description below it does not move when the first vote appears. The voters group updates right away when you vote or withdraw, without waiting for the server.
A moderator sets the bucket table’s ranking mode from the control beside the perspective title: No ranking (the default, plain table), Affinity ranking, or Dot ranking. Only a moderator can change it, and a ranking option becomes available once someone has submitted that ranking.
The choice is saved on the planning session and applies to everyone. If the change is refused, the selector returns to the last saved mode.
Switching into Affinity ranking or Dot ranking from No ranking, or between the two ranking modes, moves every listed work item to Unassigned right away, before the server responds. If the change is refused, the previous mode and votes return. Switching back to No ranking keeps the votes. If the last active session for an enforced ranking is cancelled or completed, the bucket ranking mode returns to No ranking automatically. A completed session that is still awaiting acceptance does not keep the ranking enforced.
When a ranking is enforced, the planning session tab shows a dismissable informational message above the table in both single and bulk voting. The single voting panel in the issue view shows the same message above the cards. In both places, a vote moves the work items that must follow the rank order, so the order is never broken. A work item that shares the voted item’s rank is never pulled or pushed; only work items with a different rank move.
If a vote changes more than one voting session, the message is replaced by a warning-style dismissable message that lists the affected work items. Each work item opens its Jira issue view. The voting panel and the bulk voting widgets each keep their own message.
The informational message stays visible in both places while the enforced ranking has recorded rankings, and it disappears after the rankings are cleared. The affected work items message still appears whenever a vote changes more than one session, even after the rankings are cleared.
Once an enforced ranking has at least one vote in the bucket table, that ranking is locked so the votes and their order cannot be scrambled. An affinity-enforced ranking locks drag and drop in the affinity table and makes its algorithm selector read-only; a dot-enforced ranking disables the dot column and Withdraw button. A notice appears in the affected tab, and the other ranking tab stays editable. Changing the enforced ranking clears the votes and unlocks the ranking again.
In the ranked views, work items are listed from best to worst, and each row shows a Rank column. Work items of equal rank can be reordered freely within the same card or the Unassigned group, but the card rows never move and keep their configured order. Unassigned work items stay in the Unassigned group at the top. Reordering within the same card or Unassigned cannot cross a rank boundary: you cannot drop the item below a better-ranked item or above a worse-ranked item. A refused reorder snaps back and casts no votes. Dropping a work item under a different card is a card assignment: the same push and pull applies as before, so the final item order stays rank-sorted and a run of other work items can move under that card. Work items that share the dragged item’s rank are never pulled or pushed; only the dragged item changes card among its rank peers. The Rank header and cells are right aligned. Scrumpy estimates every work item that lands under the card together, not only the one you dragged, so they all get that card’s estimate.
Perspective Columns
The table shows a column for every perspective that applies to the work item’s type; cells for perspectives that do not apply are left blank. Each cell displays:
- Participation percentage: the fraction of voters who have voted, shown as a color-coded badge (red below 25%, yellow below 50%, grey below 75%, blue below 100%, and green at 100%). It appears only when required voters are set.
- Voting session state: In progress, Paused, or Complete, shown as a badge.
- Current estimate: the latest estimate value from Jira, shown when no session is active. Story points show an “SP” suffix, T-shirt sizes show their size label, and time values show work-day durations. When a T-shirt perspective writes to a numeric field or the board estimation, a story point value that exactly matches one of the configured T-shirt card values shows the mapped size beside it as a second badge, for example
10 SP/S; a value with no matching card shows only10 SP. When both a numeric target and a T-shirt field are set, the T-shirt field label is always shown as the second badge; when only a T-shirt field is set, the cell shows only that size label.
Progress and Status
When a planning session has a date range, its panel shows a progress bar and a status below the buttons at the bottom: Completed once the end date has passed, a countdown before the start date, or the remaining time while it is in progress.
Completing a Planning Session
When all estimation work in a planning session is finished, click Complete. A confirmation appears first, because completing a planning session removes it and all of its items permanently, so it disappears from the tab list.
If there are still active voting sessions, the confirmation becomes a Pending estimation sessions warning with three choices:
- Do nothing (the default): complete the planning session and leave the active voting sessions untouched.
- Cancel all: cancel every voting session, including completed ones, before completing the planning session.
- Accept completed: accept the estimates of every completed voting session, including any value the moderator set, before completing the planning session.
Choose Go back to keep the planning session. The dialog closes as soon as you confirm and the planning session disappears from the tab list right away. If it cannot be completed, it comes back. If a Jira write fails during Accept completed, the work items whose write succeeded are accepted, the failed session stays completed so it can be retried, and an error dialog after completion lists the failed work item and the reason.
Estimating Inline
The Planning Sessions tab keeps an inline Voting Panel in a fixed column on the right. Highlight a work item to load it into the panel; until you pick one, it shows a No work item selected empty state.
Estimation History
Every accepted estimate is recorded in the estimation log, giving your team a record of sizing decisions for the last 90 days.
Viewing Estimation History
Open any Jira work item and look for the Estimation Log panel. This activity panel shows each accepted estimate for the work item, organized by perspective. When the work item has no accepted estimates yet, the panel shows an empty state instead of a table.
Pagination and Navigation
The estimation log is paginated for easy browsing through long histories. You can adjust the page size to 5, 10, 15, or 20 entries per page using the selector at the bottom of the table. Use the pagination controls to move between pages.
Live Updates
When a new estimate is accepted for the current work item, the estimation log updates automatically without needing to refresh the page. If you are on page one the new entry appears at the top. If you are on a later page, the table returns to page one so you can see the new entry.
What’s Recorded
Each estimation history entry shows:
- Moderator: the moderator who finalized the estimate, shown as the entry’s avatar
- Completion: how many of the required voters had voted
- Perspective: which estimation perspective was used
- Duration: how long the session took, shown as “for {duration}”
- Result: the final accepted estimate, plus all individual votes as comma-separated badges and the participants who cast them. Values use the perspective’s deck labels, so story points carry the “SP” suffix, T-shirt sizes show their size, and a time perspective shows a work-day duration
- Timestamp: when the estimate was accepted, shown in your Jira timezone
The result is shown in a green badge. If the moderator set a different value before accepting, the badge is yellow and hovering it shows Overridden by the moderator.
Retention and Deletion
Estimation history entries are kept for three months (90 days). Older entries are removed automatically every day. To remove every entry for the space at once, use Delete estimation log on the space settings Dashboard tab; that action is permanent and cannot be undone. Archiving a planning session to Confluence keeps its estimates as a Confluence page beyond the 90-day window.
How Results Flow to Jira
When a moderator accepts an estimate:
- The final estimate is computed from all votes using the perspective’s averaging method
- The result is written to Jira based on the perspective’s estimation target:
- Default: Updates the board’s estimation statistic (Story Points by default). For T-shirt cards, this uses the story point value you set for the chosen card
- Field: Updates the configured custom fields for points, time, or T-shirt sizes. A T-shirt field receives the size label
- The full voting session is saved for reference
Dashboard Analytics
The space Dashboard aggregates estimation history across all work items and perspectives to provide:
- Daily accepted estimate counts
- Average estimates by perspective
- Average voting duration by perspective
- Average certainty scores
- Average variation scores
- Average number of voters per session
Use the date range selector to focus on recent sprints or compare long-term trends.
Feedback and Support
The Feedback tab is the rightmost tab on the Space Estimations page, aligned to the right of the tab bar after Dashboard. Use it to tell the Scrumpy team what you think and to reach support. Everyone can use it, whatever their role. The form sits beside an illustration, under a short message that your feedback is valuable and helps improve the app.
Rating the App
Choose one of five ratings, from Not satisfied to Excellent. Rating is optional when you also leave a suggestion.
Suggesting an Improvement
Describe an idea, a problem, or a request in the How can we improve the app? box, up to 4000 characters. You can send a suggestion on its own, a rating on its own, or both together.
Click Submit to send it. The button stays disabled until you provide at least a rating or a suggestion. A confirmation appears when the feedback is sent and the form clears for a new message; if it could not be sent, an error appears and you can try again.
Support and Contact
- Support forum: opens the Scrumpy support portal in a new tab, where you can report an issue or ask for help
- Follow us: links to Facebook, LinkedIn, and YouTube
- Copyright: the AELBOX copyright notice links to scrumpy.poker
- Contact: the support email address for direct questions
App Language
Scrumpy is available in 26 languages and follows the language of your Jira user interface. There is nothing to configure: when your Jira language is one of the supported languages, every Scrumpy surface is shown in that language, including the estimation panel, chat, space settings, the Space Estimations page, personal settings, and the audit logs.
The supported languages are English (US and UK), Czech, Danish, German, Spanish, Estonian, Finnish, French, Hungarian, Icelandic, Italian, Japanese, Korean, Dutch, Norwegian, Polish, Portuguese (Brazil and Portugal), Romanian, Russian, Slovak, Swedish, Turkish, and Chinese (Simplified and Traditional).
If your Jira language is not supported, Scrumpy falls back to English. Changing your Jira language takes effect the next time a Scrumpy surface is loaded.
Archiving to Confluence
A moderator can archive a planning session to a Confluence page, giving the team a permanent record of the accepted estimates. Archiving is optional and only available after a Confluence space has been configured for the Jira space.
Configuring the Confluence Space
In space settings, open the Permissions tab and find Confluence space, below the roles. Use the search box to find a space by name or key and select it; only the space key is stored. Leave it empty to disable archiving. Only a space administrator can change this setting.
Archiving a Planning Session
On the Planning Sessions tab, the Archive button sits immediately before Complete and appears only when a Confluence space is configured. Clicking Archive opens a dialog that shows the planning window and previews exactly what will be written:
- The window is shown as a start badge and an end badge
- The preview table lists the work items that have an accepted estimate inside the window, with Type, Work item, Perspective, and Estimate columns, and can be sorted
- When nothing is listed, the dialog explains why: no estimates have been accepted for this session yet, or the session has accepted estimates but none fall inside the planning window
Confirm with Archive. On success the dialog shows a link to the created page. The Archive button is disabled whenever the preview lists no work items (while it is loading, when none have been accepted, when they all fall outside the planning window, or when the preview fails to load). Only moderators can archive.
Archiving While Completing
When a Confluence space is configured, both Complete dialogs offer a Create a Confluence archive page checkbox. When checked, the archive runs after any chosen accept or cancel action and before the planning session is removed. The resulting page link, or the failure message, is shown as a banner in the Planning Sessions tab. The banner offers a Dismiss action that hides it.
The Archive Page
The generated page contains:
- The planning title, followed by the start date, time, and timezone (for example Sprint 42 – 2025-06-01 09:00 (Europe/Berlin))
- The description, then the start and end on separate lines, with each date shown as a Confluence date chip and each time highlighted in a blue badge
- The timezone the dates are valid in
- A Participants section listing every voter who actually voted, with their number of votes, as a small table with a Votes column and a Participant column (each voter is one row)
- An Estimated work items table of the accepted estimates, with columns Work item, Perspective, Duration, Votes (each given vote as a badge), Participants (the voters shown as a group of users), Estimate (a badge that is green when the computed average was chosen and yellow when the moderator set a different value), and Moderated by (the user who started the voting session)
The page includes only the accepted estimates that fall between the planning session’s start and end. All dates and times are rendered in the archiver’s preferred timezone.
Page Hierarchy and Re-Archiving
Pages are written under a fixed hierarchy: a root Estimations parent page, then a child page named after the Jira space, then the archive page. Re-archiving the same session updates the existing page (matched by exact title) instead of creating a duplicate. The created page is a normal Confluence page and is not removed when Scrumpy purges estimation data after its 90-day retention window.
