[{"data":1,"prerenderedAt":10465},["ShallowReactive",2],{"guide-en":3},{"docs":4,"tutorials":7922},[5,180,817,1867,2120,3021,3183,3471,4854,5051,5175,5218,5569,6495,7109],{"id":6,"title":7,"body":8,"dateModified":159,"datePublished":160,"description":161,"extension":162,"heading":63,"image":163,"imageAlt":63,"keywords":164,"locale":168,"meta":169,"navigation":170,"order":171,"path":172,"section":173,"seo":174,"sitemap":175,"slug":176,"stem":177,"translationKey":178,"__hash__":179},"guide\u002Fguide\u002Fen\u002Fwhat-is-story-point-estimation.md","What is Story Point Estimation? | Scrumpy Planning Poker",{"type":9,"value":10,"toc":152},"minimark",[11,20,25,53,57,60,65,83,87,90],[12,13,14,15,19],"p",{},"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 ",[16,17,18],"strong",{},"story points"," that represent the relative complexity, effort, and uncertainty of a task.",[21,22,24],"h2",{"id":23},"why-story-points","Why Story Points?",[26,27,28,35,41,47],"ul",{},[29,30,31,34],"li",{},[16,32,33],{},"Relative sizing"," - It is easier to say \"this task is twice as hard as that one\" than to guess exact hours",[29,36,37,40],{},[16,38,39],{},"Team calibration"," - Points are defined by the team, for the team, based on shared experience",[29,42,43,46],{},[16,44,45],{},"Velocity tracking"," - Over time, the team learns how many points they can complete in a sprint, enabling more accurate forecasting",[29,48,49,52],{},[16,50,51],{},"Reduced anchoring"," - Abstract units avoid the emotional baggage of time-based estimates",[21,54,56],{"id":55},"how-planning-poker-works","How Planning Poker Works",[12,58,59],{},"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.",[61,62],"docs-figure",{"alt":63,"caption":63,"stem":64},"What is Story Point Estimation?","guide-voting-cards",[66,67,68,71,74,77,80],"ol",{},[29,69,70],{},"A work item is presented for estimation",[29,72,73],{},"Each team member privately selects a card value",[29,75,76],{},"Votes are revealed simultaneously",[29,78,79],{},"The team discusses discrepancies and may re-vote",[29,81,82],{},"The final estimate is accepted and recorded",[21,84,86],{"id":85},"scrumpys-role","Scrumpy's Role",[12,88,89],{},"Scrumpy automates this process inside Jira. It provides:",[26,91,92,98,104,110,116,122,128,134,140,146],{},[29,93,94,97],{},[16,95,96],{},"Multiple estimation perspectives"," - Estimate the same work item from different angles (complexity, time, risk)",[29,99,100,103],{},[16,101,102],{},"Live voting"," - See votes appear as team members submit them",[29,105,106,109],{},[16,107,108],{},"Instant feedback"," - Changes you make appear right away, and if something cannot be saved the previous state returns",[29,111,112,115],{},[16,113,114],{},"Automatic result computation"," - Configurable averaging methods calculate the final estimate",[29,117,118,121],{},[16,119,120],{},"Certainty signal"," - A percentage that shows how often participants settled on their votes instead of re-voting",[29,123,124,127],{},[16,125,126],{},"Variation signal"," - A percentage that shows how widely the vote values are spread around their average",[29,129,130,133],{},[16,131,132],{},"Required voters and reminders"," - Choose who must vote and nudge anyone who has not",[29,135,136,139],{},[16,137,138],{},"Asynchronous voting"," - Let participants vote at their own pace, with an optional deadline",[29,141,142,145],{},[16,143,144],{},"Built-in chat"," - Discuss estimates and react to messages during a session",[29,147,148,151],{},[16,149,150],{},"Jira integration"," - Accepted estimates are written directly to your Jira board or custom fields",{"title":153,"searchDepth":154,"depth":154,"links":155},"",2,[156,157,158],{"id":23,"depth":154,"text":24},{"id":55,"depth":154,"text":56},{"id":85,"depth":154,"text":86},"2026-11-10","2026-07-26","Story points explained: why agile teams estimate in relative units, how planning poker works, and where Scrumpy fits into Jira.","md","\u002Fog\u002Fguide-what-is-story-point-estimation.jpg",[18,165,166,167],"agile estimation","planning poker","scrum","en",{},true,1,"\u002Fgetting-started\u002Fwhat-is-story-point-estimation","guide",{"title":7,"description":161},{"loc":172,"lastmod":159},"what-is-story-point-estimation","guide\u002Fen\u002Fwhat-is-story-point-estimation","guide\u002Fwhat-is-story-point-estimation","1LvzuatCesskMgp8oWejkQfEzGP5X2z8jPgSLHfRprc",{"id":181,"title":182,"body":183,"dateModified":802,"datePublished":160,"description":803,"extension":162,"heading":366,"image":804,"imageAlt":366,"keywords":805,"locale":168,"meta":810,"navigation":170,"order":154,"path":811,"section":173,"seo":812,"sitemap":813,"slug":370,"stem":814,"translationKey":815,"__hash__":816},"guide\u002Fguide\u002Fen\u002Fgetting-started.md","Getting Started with Scrumpy | Scrumpy Planning Poker",{"type":9,"value":184,"toc":778},[185,188,192,195,199,206,226,229,232,237,240,262,269,273,276,279,282,286,289,295,299,306,321,325,364,368,372,375,378,385,388,391,394,401,404,407,410,413,416,420,423,467,470,473,511,526,529,532,535,538,541,547,551,558,576,583,587,596,600,608,613,689,700,710,714,723,730,736,742,748,753,759,764,770],[12,186,187],{},"This guide walks you through setting up Scrumpy for your team.",[21,189,191],{"id":190},"step-1-install-the-app","Step 1: Install the App",[12,193,194],{},"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.",[21,196,198],{"id":197},"step-2-configure-your-team","Step 2: Configure Your Team",[12,200,201,202,205],{},"Open ",[16,203,204],{},"Space settings > Scrumpy Poker > Permissions"," and assign roles to your team:",[26,207,208,214,220],{},[29,209,210,213],{},[16,211,212],{},"Moderators",": people who start, manage, and complete voting sessions. Typically scrum masters, team leads, or product managers.",[29,215,216,219],{},[16,217,218],{},"Voters",": team members who cast estimates during voting sessions.",[29,221,222,225],{},[16,223,224],{},"Guests",": anyone who is not a moderator or a voter. Guests can watch sessions and see results, but they cannot vote or moderate.",[12,227,228],{},"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.",[12,230,231],{},"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.",[233,234,236],"h3",{"id":235},"choose-where-scrumpy-appears","Choose Where Scrumpy Appears",[12,238,239],{},"The same page controls where Scrumpy appears in Jira. Two checkboxes are selected by default:",[26,241,242,256],{},[29,243,244,247,248,251,252,255],{},[16,245,246],{},"Show the Estimations page"," adds the ",[16,249,250],{},"Estimations"," tab to the space navigation. Clearing it hides the page for everyone in the space. It also hides the ",[16,253,254],{},"Add to planning"," action on work items, because planning sessions live on that page.",[29,257,258,261],{},[16,259,260],{},"Show the Scrumpy panel on work items"," adds the Scrumpy panel to the right of every work item. Clearing it hides the panel for everyone in the space. The estimation log stays available until both the panel and the page are hidden.",[12,263,264,265,268],{},"Your choice applies to everyone in the space, not only to you, and it takes effect the next time Jira loads the space or a work item. These checkboxes hide surfaces in Jira. They do not delete estimates, planning sessions, or estimation history, and they do not replace Jira permissions. ",[16,266,267],{},"Reset to defaults"," does not change them.",[233,270,272],{"id":271},"optional-set-a-password","Optional: Set a Password",[12,274,275],{},"You can protect a space with a password. When a password is set, anyone opening the Scrumpy panel, the Space Estimations page, the estimation log, or the add-to-planning action must enter it first. Live updates for voting, chat, and planning are locked too: without the password, a visitor does not receive them. Live updates also require that you can browse the space in Jira, with or without a password. Space settings stay available to people who can manage the space in Jira. Passwords must be at least 8 characters. Scrumpy checks the password after you pause typing, and it never sends an entry shorter than eight characters, so a partial password does not spend an attempt. The length rule is enforced by the server, and the password is stored as a slow salted hash that cannot be read back or reused to sign in without the password. You can change or remove the password at any time.",[12,277,278],{},"After five incorrect attempts in fifteen minutes, the account is locked out for fifteen minutes and the password field is disabled until the lockout ends. A successful entry clears the failed-attempt count.",[12,280,281],{},"After you enter the password once, Scrumpy remembers it for your account for 30 days. The same entry unlocks every Scrumpy surface, so you are not asked again. 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.",[21,283,285],{"id":284},"step-3-set-up-perspectives","Step 3: Set Up Perspectives",[12,287,288],{},"Perspectives define how your team estimates. Each perspective has its own voting rules, card sequences, and target Jira field.",[12,290,201,291,294],{},[16,292,293],{},"Space settings > Scrumpy Poker > Settings"," to choose the space's working week and configure your perspectives. A Default perspective is created for you automatically, set up for Story Points estimation, and it cannot be deleted.",[21,296,298],{"id":297},"step-4-start-estimating","Step 4: Start Estimating",[12,300,301,302,305],{},"Open any Jira work item and look for the ",[16,303,304],{},"Scrumpy"," panel on the right side of the screen.",[26,307,308,315,318],{},[29,309,310,311,314],{},"As a moderator, click ",[16,312,313],{},"Start"," to begin a voting session",[29,316,317],{},"As a voter, cast your estimate by clicking a card",[29,319,320],{},"Once all required voters have submitted, the moderator accepts the result",[21,322,324],{"id":323},"step-5-use-the-space-estimations-page","Step 5: Use the Space Estimations Page",[12,326,201,327,330,331,334,335,334,338,334,341,334,344,334,347,334,350,334,353,356,357,360,361,363],{},[16,328,329],{},"Space > Estimations",". The page has these tabs: ",[16,332,333],{},"Getting started",", ",[16,336,337],{},"Tutorials",[16,339,340],{},"Refinement\u002Fgrooming",[16,342,343],{},"Capacity planning",[16,345,346],{},"Standup",[16,348,349],{},"Retrospective",[16,351,352],{},"Voting sessions",[16,354,355],{},"Dashboard",", and a right-aligned ",[16,358,359],{},"Feedback"," tab. A support icon to the right of ",[16,362,359],{}," shows or hides the quick start guide. If a password is set, the whole page is locked until you enter it. Space settings are not locked by this password; they follow the Jira permissions for the space. The tab you last opened is remembered for the current browser tab, so a reload returns you to it. If the connection to Jira drops for a moment, the page catches up when it returns, so a voting session that was started, paused, accepted, or cancelled in the meantime shows its current state without a reload.",[61,365],{"alt":366,"caption":366,"stem":367},"Getting Started with Scrumpy","guide-space-tabs",[233,369,371],{"id":370},"getting-started","Getting Started",[12,373,374],{},"An onboarding walkthrough that explains what estimation is and how to use Scrumpy. Most sections include screenshots. They follow your Jira theme, and their captions follow your language. The Chat section shows examples for sending a message, reactions, and private messages.",[233,376,337],{"id":377},"tutorials",[12,379,380,381,384],{},"Short guided tours with screenshots. Choose a tutorial in the ",[16,382,383],{},"Select tutorial"," dropdown at the top center of the tab and read it right away. The tutorial loads when you select it. Each tutorial is a few short steps with a screenshot for every step, so you can follow along without leaving the page. Screenshots follow your Jira theme, so you see the light or dark version that matches the theme you use. Your choice is remembered for the current browser tab. Tutorial text follows your Jira language. Screenshots stay in English and follow your Jira theme.",[233,386,340],{"id":387},"refinementgrooming",[12,389,390],{},"Create and manage planning sessions to organize refinement work. See the Planning sessions page for details.",[233,392,343],{"id":393},"capacity-planning",[12,395,396,397,400],{},"Plan how much work your team can take on in the next sprints. Open the tab, choose a planning session, and select ",[16,398,399],{},"Plan sprint"," to add the closed sprints that set your velocity and the active or future sprints you want to plan. The combined table shows each sprint together with its work items, the target capacity, and a colored timeline, so you can see at a glance whether the plan fits.",[12,402,403],{},"Use the right side to set each team member's utilization and working hours, edit the selected sprint, vote on a work item in its perspective tab, or chat about it. Moderators can rank the work items, apply the plan to Jira, and archive the sprint to Confluence. See the Capacity planning page for the full walkthrough.",[233,405,346],{"id":406},"standup",[12,408,409],{},"Run a standup for a planning session. Choose the board and sprint, then review the work items in their board columns. The moderator marks the item the team is discussing, can limit how many cards each column shows, and controls the shared countdown. Flag work items and stage status moves, then apply them to Jira. See the Standup page for the full walkthrough.",[233,411,349],{"id":412},"retrospective",[12,414,415],{},"Run a sprint retrospective for a planning session. Add notes in the three columns, like and group the notes you agree on, and turn them into action items. The moderator moves the retrospective through Feedback, Vote, and Actions and controls the shared countdown. Archive the results or delete the planning session when you are done. See the Sprint retrospectives page for the full walkthrough.",[233,417,419],{"id":418},"voting-sessions","Voting Sessions",[12,421,422],{},"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. The table shows 25 rows at a time; use the controls below it to move between pages.",[26,424,425,435,444,449,455,461],{},[29,426,427,430,431,434],{},[16,428,429],{},"Type"," and ",[16,432,433],{},"Work item",": centered headers and cells. Work item cells have no leading space before the key.",[29,436,437,430,440,443],{},[16,438,439],{},"State",[16,441,442],{},"% complete",": left aligned, minimum width, and the % complete header stays on one line.",[29,445,446,448],{},[16,447,218],{},": right aligned.",[29,450,451,454],{},[16,452,453],{},"Started",": how long ago the session began. The value updates every 10 seconds, for example 5m 10s, 5m 20s, and 5m 30s. This column keeps 20% of the table width, so the changing timer does not resize the table.",[29,456,457,460],{},[16,458,459],{},"Ending",": counts down the remaining time. It updates every 10 seconds, then every second during the last 10 seconds. This column keeps 15% of the table width for the same reason.",[29,462,463,466],{},[16,464,465],{},"Completion",": shows a status tag.",[12,468,469],{},"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. Only sessions for work items you can open in Jira are listed; a work item hidden from you by Jira issue-level security is omitted. When there are no sessions, the tab shows an empty state instead of the table. If you already viewed sessions on another tab, they appear right away, and the rest of the space's sessions load in the background without a loading placeholder.",[12,471,472],{},"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.",[26,474,475,481,487,493,499,505],{},[29,476,477,480],{},[16,478,479],{},"Pause"," pauses the selected active sessions. Sessions in perspectives with asynchronous voting are skipped.",[29,482,483,486],{},[16,484,485],{},"Resume"," resumes the selected paused sessions. Sessions in perspectives with asynchronous voting are skipped.",[29,488,489,492],{},[16,490,491],{},"Complete"," finishes a session that has real votes and cancels one whose votes are missing or are only extra emoji cards.",[29,494,495,498],{},[16,496,497],{},"Restart"," starts a new round for the selected completed sessions right away, with the configured required voters. The completed result and its votes are discarded, and the work item keeps its place in the perspective's rankings.",[29,500,501,504],{},[16,502,503],{},"Cancel"," stops the selected sessions, including completed ones.",[29,506,507,510],{},[16,508,509],{},"Accept"," writes the completed sessions' estimates to Jira.",[12,512,513,514,516,517,519,520,522,523,525],{},"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; ",[16,515,479],{}," needs an active session, ",[16,518,485],{}," needs a paused session, and both need a perspective without asynchronous voting. ",[16,521,497],{}," needs a completed session. ",[16,524,503],{}," is enabled for any selected session, started or completed.",[12,527,528],{},"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.",[12,530,531],{},"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.",[233,533,355],{"id":534},"dashboard",[12,536,537],{},"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 the row appears once the first person votes. Sessions you already viewed on another tab appear right away, and the charts update as the rest of the space's sessions load in the background.",[233,539,359],{"id":540},"feedback",[12,542,543,544,546],{},"The right-aligned ",[16,545,359],{}," tab lets you rate the app, suggest improvements, and contact the support team. See the Feedback and Support section for details.",[233,548,550],{"id":549},"quick-start-guide","Quick start guide",[12,552,553,554,557],{},"Above the tab list, a ",[16,555,556],{},"Quick start"," guide shows four steps to get going:",[66,559,560,563,570,573],{},[29,561,562],{},"Set up the space moderators and voters (open the space settings Permissions tab to do this).",[29,564,565,566,569],{},"Create a planning session with an optional start and end time using ",[16,567,568],{},"Create",".",[29,571,572],{},"Add Jira work items to the refinement\u002Fgrooming tab from an existing Jira filter.",[29,574,575],{},"Arrange the items in the order they will be estimated.",[12,577,578,579,582],{},"The guide is for new spaces, so it disappears on its own once you add work items to refinement\u002Fgrooming, save a plan on the capacity planning tab, or write a note in a retrospective. Choose ",[16,580,581],{},"Dismiss"," in the message to hide it, or use the support icon in the tab bar to show it again.",[233,584,586],{"id":585},"adding-work-items-to-planning-from-the-work-item-view","Adding Work items to Planning from the Work item View",[12,588,589,590,592,593,595],{},"When you view a Jira work item, open the ",[16,591,304],{}," panel and click ",[16,594,254],{}," to add the current work item to an existing planning session, or create a new one on the spot. Only moderators can add work items; everyone else sees a note explaining this. The panel remembers the planning session you used last on the space.",[233,597,599],{"id":598},"filtering-work-items-with-jql","Filtering Work items with JQL",[12,601,602,603,607],{},"For advanced users who build Jira filters and boards, Scrumpy provides a custom JQL function, ",[604,605,606],"code",{},"issuesInEstimation()",", that returns the work items currently being estimated.",[609,610,612],"h4",{"id":611},"parameters","Parameters",[614,615,616,632],"table",{},[617,618,619],"thead",{},[620,621,622,626,629],"tr",{},[623,624,625],"th",{},"Parameter",[623,627,628],{},"Required",[623,630,631],{},"Description",[633,634,635,653,673],"tbody",{},[620,636,637,643,646],{},[638,639,640],"td",{},[604,641,642],{},"projectKey",[638,644,645],{},"Yes",[638,647,648,649,652],{},"The Jira space key (for example ",[604,650,651],{},"\"PROJ\"",")",[620,654,655,660,663],{},[638,656,657],{},[604,658,659],{},"state",[638,661,662],{},"No",[638,664,665,666,430,669,672],{},"Filter by session state. Only ",[604,667,668],{},"\"paused\"",[604,670,671],{},"\"completed\""," are recognized. Omit to include every state",[620,674,675,680,682],{},[638,676,677],{},[604,678,679],{},"perspectives",[638,681,662],{},[638,683,684,685,688],{},"Filter by one or more perspective names, separated by commas (for example ",[604,686,687],{},"\"Points, Time\"","). Names must match exactly, including case",[12,690,691,692,694,695,430,697,699],{},"Values after ",[604,693,642],{}," are read by value: ",[604,696,668],{},[604,698,671],{}," select the state, and any other value is treated as a comma-separated list of perspective names.",[12,701,702,703,430,706,709],{},"The function supports both ",[604,704,705],{},"in",[604,707,708],{},"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.",[609,711,713],{"id":712},"examples","Examples",[715,716,721],"pre",{"className":717,"code":719,"language":720},[718],"language-text","issuekey in issuesInEstimation(\"PROJ\")\n","text",[604,722,719],{"__ignoreMap":153},[12,724,725,726,729],{},"Return all work items in space ",[604,727,728],{},"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.",[715,731,734],{"className":732,"code":733,"language":720},[718],"issuekey in issuesInEstimation(\"PROJ\", \"paused\")\n",[604,735,733],{"__ignoreMap":153},[12,737,738,739,741],{},"Return work items in ",[604,740,728],{}," with a paused voting session. Useful for finding work items that need the moderator's attention.",[715,743,746],{"className":744,"code":745,"language":720},[718],"issuekey in issuesInEstimation(\"PROJ\", \"completed\")\n",[604,747,745],{"__ignoreMap":153},[12,749,738,750,752],{},[604,751,728],{}," where voting has completed but the moderator has not accepted the result yet.",[715,754,757],{"className":755,"code":756,"language":720},[718],"issuekey in issuesInEstimation(\"PROJ\", \"paused\", \"Points\")\n",[604,758,756],{"__ignoreMap":153},[12,760,738,761,763],{},[604,762,728],{}," with a paused session in the Points perspective. You can list several perspective names to match any of them.",[715,765,768],{"className":766,"code":767,"language":720},[718],"issuekey not in issuesInEstimation(\"PROJ\", \"completed\")\n",[604,769,767],{"__ignoreMap":153},[12,771,738,772,774,775,777],{},[604,773,728],{}," that are not in a completed estimation session. Use ",[604,776,708],{}," to exclude work items from a filter or board.",{"title":153,"searchDepth":154,"depth":154,"links":779},[780,781,786,787,788],{"id":190,"depth":154,"text":191},{"id":197,"depth":154,"text":198,"children":782},[783,785],{"id":235,"depth":784,"text":236},3,{"id":271,"depth":784,"text":272},{"id":284,"depth":154,"text":285},{"id":297,"depth":154,"text":298},{"id":323,"depth":154,"text":324,"children":789},[790,791,792,793,794,795,796,797,798,799,800,801],{"id":370,"depth":784,"text":371},{"id":377,"depth":784,"text":337},{"id":387,"depth":784,"text":340},{"id":393,"depth":784,"text":343},{"id":406,"depth":784,"text":346},{"id":412,"depth":784,"text":349},{"id":418,"depth":784,"text":419},{"id":534,"depth":784,"text":355},{"id":540,"depth":784,"text":359},{"id":549,"depth":784,"text":550},{"id":585,"depth":784,"text":586},{"id":598,"depth":784,"text":599},"2026-11-21","Install Scrumpy Planning Poker in Jira, set up roles and perspectives, and run your first estimation round in five steps.","\u002Fog\u002Fguide-getting-started.jpg",[806,807,808,809],"scrumpy planning poker","jira app","getting started","planning poker setup",{},"\u002Fgetting-started",{"title":182,"description":803},{"loc":811,"lastmod":802},"guide\u002Fen\u002Fgetting-started","guide\u002Fgetting-started","eCmV9QjcKILJk6QcL30Q00LIA5lvRL3gMKp1jyFhXvk",{"id":818,"title":819,"body":820,"dateModified":802,"datePublished":160,"description":1853,"extension":162,"heading":923,"image":1854,"imageAlt":923,"keywords":1855,"locale":168,"meta":1859,"navigation":170,"order":784,"path":1860,"section":173,"seo":1861,"sitemap":1862,"slug":1863,"stem":1864,"translationKey":1865,"__hash__":1866},"guide\u002Fguide\u002Fen\u002Festimation-perspectives.md","Estimation Perspectives | Scrumpy Planning Poker",{"type":9,"value":821,"toc":1837},[822,825,829,843,846,853,865,869,872,898,902,921,925,928,948,955,958,977,980,1062,1070,1074,1077,1109,1112,1116,1123,1161,1164,1170,1177,1183,1192,1196,1199,1202,1321,1327,1330,1333,1336,1340,1346,1501,1504,1507,1510,1517,1520,1544,1548,1579,1584,1589,1607,1613,1616,1638,1651,1656,1670,1676,1690,1693,1696,1699,1704,1718,1721,1727,1730,1755,1758,1761,1783,1786,1789,1793,1804,1831,1834],[12,823,824],{},"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.",[21,826,828],{"id":827},"working-week","Working week",[12,830,831,832,835,836,839,840,842],{},"At the top of the Settings tab, choose the ",[16,833,834],{},"Week starts on"," day and the ",[16,837,838],{},"Weekend days"," your team does not work. The default is Monday, with Saturday and Sunday as weekend days. Pick one or two weekend days, and do not include the week start day in the weekend. If the selection is invalid, the ",[16,841,838],{}," field turns red and explains what to change.",[12,844,845],{},"Capacity planning uses these days to count the working days in each sprint and to calculate the target capacity. The team calendar starts on the chosen day and disables the weekend days, so you cannot mark time off on them.",[12,847,848,849,852],{},"Below the two day fields, ",[16,850,851],{},"Work hours"," sets how many hours one full working day counts for. It accepts a whole number from 1 to 13, and the default is 8. Capacity planning uses it as the regular day for every working day in a sprint.",[12,854,855,856,334,858,861,862,864],{},"Next to ",[16,857,851],{},[16,859,860],{},"Maximum daily hours"," sets the largest number of hours a team member can record for one day. It accepts a whole number from 1 to 13, and the default is 13. It cannot be lower than ",[16,863,851],{},". Capacity planning uses this value as the maximum of every time off hours field. A day above the work hours raises that team member's available hours and the team capacity.",[21,866,868],{"id":867},"why-multiple-perspectives","Why Multiple Perspectives?",[12,870,871],{},"Different estimation dimensions help your team look at work from several angles:",[26,873,874,880,886,892],{},[29,875,876,879],{},[16,877,878],{},"Points",": Relative complexity and effort",[29,881,882,885],{},[16,883,884],{},"Time",": Hours or days of work",[29,887,888,891],{},[16,889,890],{},"T-Shirt Sizes",": Coarse-grained sizing (XS, S, M, L, XL)",[29,893,894,897],{},[16,895,896],{},"Risk",": Likelihood or impact of unknowns",[21,899,901],{"id":900},"perspective-settings","Perspective Settings",[12,903,904,905,334,908,334,911,334,914,917,918,569],{},"Each perspective is configured through five sub-tabs: ",[16,906,907],{},"General",[16,909,910],{},"Voting",[16,912,913],{},"Cards",[16,915,916],{},"Estimation",", and ",[16,919,920],{},"Backup & Restore",[61,922],{"alt":923,"caption":923,"stem":924},"Estimation Perspectives","guide-perspectives",[233,926,907],{"id":927},"general",[12,929,930,931,933,934,937,938,917,941,944,945,947],{},"The ",[16,932,907],{}," tab holds the perspective's ",[16,935,936],{},"name",", optional ",[16,939,940],{},"description",[16,942,943],{},"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 ",[16,946,943],{}," (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.",[12,949,950,951,954],{},"If no perspective applies to a work item's work type, the Scrumpy panel shows ",[16,952,953],{},"No voting perspective",", names the work type, and asks you to configure the space's perspective settings rather than showing an empty deck.",[12,956,957],{},"Below those fields, the General tab has three actions:",[26,959,960,965,971],{},[29,961,962,964],{},[16,963,267],{},": Return the perspective to its initial settings, after a confirmation",[29,966,967,970],{},[16,968,969],{},"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",[29,972,973,976],{},[16,974,975],{},"Delete perspective",": Remove the perspective and all its sessions permanently, after a confirmation. The Default perspective cannot be deleted",[233,978,910],{"id":979},"voting",[614,981,982,991],{},[617,983,984],{},[620,985,986,989],{},[623,987,988],{},"Setting",[623,990,631],{},[633,992,993,1003,1013,1023,1033,1042,1052],{},[620,994,995,1000],{},[638,996,997],{},[16,998,999],{},"Open voting",[638,1001,1002],{},"When on, participants see each other's votes in real time",[620,1004,1005,1010],{},[638,1006,1007],{},[16,1008,1009],{},"Certainty",[638,1011,1012],{},"Shows how often participants re-voted during the session, not how spread the votes are. One vote per participant gives 100%",[620,1014,1015,1020],{},[638,1016,1017],{},[16,1018,1019],{},"Variation",[638,1021,1022],{},"Shows how widely the vote values are spread around their average. Lower is better, and it needs at least two numeric votes",[620,1024,1025,1030],{},[638,1026,1027],{},[16,1028,1029],{},"Automatic completion",[638,1031,1032],{},"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",[620,1034,1035,1039],{},[638,1036,1037],{},[16,1038,138],{},[638,1040,1041],{},"Participants vote at their own pace, without a countdown timer",[620,1043,1044,1049],{},[638,1045,1046],{},[16,1047,1048],{},"Vote duration",[638,1050,1051],{},"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",[620,1053,1054,1059],{},[638,1055,1056],{},[16,1057,1058],{},"Averaging",[638,1060,1061],{},"How votes are combined: Arithmetic mean, Geometric mean, Harmonic mean, Quadratic mean, Midrange, Median, Minimum, Maximum, Mode (most common), PERT, or Count",[12,1063,1064,1065,569],{},"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 ",[1066,1067,1069],"docs-link",{"to":1068},"\u002Fgetting-started\u002Fvoting-session-controls","Voting Session Controls",[233,1071,1073],{"id":1072},"mean-averaging","Mean averaging",[12,1075,1076],{},"Scrumpy offers five mean-based methods:",[26,1078,1079,1085,1091,1097,1103],{},[29,1080,1081,1084],{},[16,1082,1083],{},"Arithmetic mean"," adds the votes and divides by the number of votes.",[29,1086,1087,1090],{},[16,1088,1089],{},"Geometric mean"," multiplies the votes and takes the nth root.",[29,1092,1093,1096],{},[16,1094,1095],{},"Harmonic mean"," divides the number of votes by the sum of their reciprocals.",[29,1098,1099,1102],{},[16,1100,1101],{},"Quadratic mean"," squares the votes, averages the squares, and takes the square root.",[29,1104,1105,1108],{},[16,1106,1107],{},"Midrange"," is halfway between the smallest and largest vote.",[12,1110,1111],{},"A zero vote makes the geometric and harmonic means zero. Every result is rounded to the nearest available card, like the other averaging methods.",[233,1113,1115],{"id":1114},"pert-averaging","PERT averaging",[12,1117,1118,1119,1122],{},"PERT (Program Evaluation and Review Technique) is a three-point estimation method. When you choose ",[16,1120,1121],{},"PERT"," as the averaging method and the team has cast at least three different values, Scrumpy takes the three points from the votes themselves:",[614,1124,1125,1135],{},[617,1126,1127],{},[620,1128,1129,1132],{},[623,1130,1131],{},"Point",[623,1133,1134],{},"Meaning",[633,1136,1137,1145,1153],{},[620,1138,1139,1142],{},[638,1140,1141],{},"Optimistic (O)",[638,1143,1144],{},"The smallest value voted",[620,1146,1147,1150],{},[638,1148,1149],{},"Most Likely (M)",[638,1151,1152],{},"The average of every value strictly between the smallest and the largest",[620,1154,1155,1158],{},[638,1156,1157],{},"Pessimistic (P)",[638,1159,1160],{},"The largest value voted",[12,1162,1163],{},"The estimate is the weighted PERT average:",[715,1165,1168],{"className":1166,"code":1167,"language":720},[718],"E = (O + 4M + P) \u002F 6\n",[604,1169,1167],{"__ignoreMap":153},[12,1171,1172,1173,1176],{},"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 ",[16,1174,1175],{},"Deviation",":",[715,1178,1181],{"className":1179,"code":1180,"language":720},[718],"deviation = (P - O) \u002F 6\n",[604,1182,1180],{"__ignoreMap":153},[12,1184,1185,1186,1188,1189,1191],{},"While ",[16,1187,999],{}," 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 ",[16,1190,999],{}," is on.",[233,1193,1195],{"id":1194},"count-averaging","Count averaging",[12,1197,1198],{},"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.",[233,1200,913],{"id":1201},"cards",[614,1203,1204,1212],{},[617,1205,1206],{},[620,1207,1208,1210],{},[623,1209,988],{},[623,1211,631],{},[633,1213,1214,1224,1234,1244,1254,1264,1274,1288],{},[620,1215,1216,1221],{},[638,1217,1218],{},[16,1219,1220],{},"Sequence",[638,1222,1223],{},"Choose the estimation style from the dropdown: Regular, Fibonacci, Tens, Fingers, Dice, T-Shirt, Free Scale, or Parametric",[620,1225,1226,1231],{},[638,1227,1228],{},[16,1229,1230],{},"Available cards",[638,1232,1233],{},"Which cards from the sequence appear to voters during a session",[620,1235,1236,1241],{},[638,1237,1238],{},[16,1239,1240],{},"Card titles",[638,1242,1243],{},"The name shown for each card, built in per card and editable",[620,1245,1246,1251],{},[638,1247,1248],{},[16,1249,1250],{},"T-shirt story points",[638,1252,1253],{},"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",[620,1255,1256,1261],{},[638,1257,1258],{},[16,1259,1260],{},"Extra cards",[638,1262,1263],{},"Fun cards for team morale (infinity, phoenix, cookie, buffalo, ping pong)",[620,1265,1266,1271],{},[638,1267,1268],{},[16,1269,1270],{},"Custom images",[638,1272,1273],{},"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",[620,1275,1276,1281],{},[638,1277,1278],{},[16,1279,1280],{},"Free scale range",[638,1282,1283,1284,1287],{},"Custom minimum and maximum for free-form numeric estimation, with a preview slider that shows the value in a large, easy-to-read size, as story points with a small ",[16,1285,1286],{},"sp"," suffix. The converted duration appears only when the estimation target writes a time value (a time board or a Time field).",[620,1289,1290,1295],{},[638,1291,1292],{},[16,1293,1294],{},"Story points to hours",[638,1296,1297,1298,1301,1302,1305,1306,1309,1310,1313,1314,1317,1318,1320],{},"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. It is available for every sequence, including T-shirt: a T-shirt size is first converted to the story points configured next to the cards, and then to hours. The voting panel follows the estimation target. A numeric board or a story points field shows story points only. A time board or a Time field shows the duration only. When a Field target has both a story points field and a Time field, both appear, for example ",[16,1299,1300],{},"5 sp · 1 day 3 hours",". A T-shirt result shows only the configured parts in one badge, in the order story points, time, T-shirt size, for example ",[16,1303,1304],{},"1 sp · S",". The same units appear in the vote list, the result chart, the badge beside the narrowed ",[16,1307,1308],{},"Override"," dropdown, and the final result. When the estimation target is ",[16,1311,1312],{},"Field",", a non-zero conversion also shows the ",[16,1315,1316],{},"Time field"," for every sequence, including T-shirt. When ",[16,1319,1294],{}," is set but the target does not write a time value, the duration is not displayed anywhere and an information message in the perspective settings explains why.",[12,1322,1323,1324,1326],{},"Custom images are set per card and per sequence. The Available cards list shows the cards of the sequence selected in ",[16,1325,1220],{}," (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. Parametric perspectives have no cards, so they have no card images.",[12,1328,1329],{},"Only people who can manage the space can upload or remove a custom image. The image belongs to this space and cannot be used by another space.",[12,1331,1332],{},"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.",[12,1334,1335],{},"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.",[233,1337,1339],{"id":1338},"parametric","Parametric",[12,1341,1342,1343,1345],{},"Choose ",[16,1344,1339],{}," when the estimate should come from a formula instead of a card. The card and card image controls are replaced by parameter controls and a formula.",[26,1347,1348,1351,1362,1376,1384,1448,1451,1454,1457,1475,1482,1495],{},[29,1349,1350],{},"The first two parameters are always present. They start with the names \"Parameter 1\" and \"Parameter 2\" in your language. You can rename them, set their minimum and maximum, and set their step size. Clearing a name restores the default name.",[29,1352,1353,1354,1357,1358,1361],{},"Press ",[16,1355,1356],{},"Add parameter"," to add a third parameter, up to ten parameters. Parameters from the third onward have a checkbox. Select one or more and press ",[16,1359,1360],{},"Delete selected"," to remove them.",[29,1363,1364,1365,334,1368,1371,1372,1375],{},"The formula uses the parameter variables shown below the field: ",[604,1366,1367],{},"p1",[604,1369,1370],{},"p2",", and so on. For example, ",[604,1373,1374],{},"(p1 + p2) \u002F 2"," averages the first two parameters.",[29,1377,1378,1379,1381,1382,569],{},"The preview below the formula uses the same parameters voters see. Move a parameter to see the result update. When ",[16,1380,1294],{}," is set, the preview appends the converted duration, for example ",[16,1383,1300],{},[29,1385,1386,1387,334,1390,334,1393,334,1396,334,1399,334,1402,334,1405,334,1408,334,1411,334,1414,334,1417,334,1420,334,1423,334,1426,334,1429,334,1432,334,1435,334,1438,1441,1442,430,1445,569],{},"The formula supports ",[604,1388,1389],{},"+",[604,1391,1392],{},"-",[604,1394,1395],{},"*",[604,1397,1398],{},"\u002F",[604,1400,1401],{},"^",[604,1403,1404],{},"%",[604,1406,1407],{},"min",[604,1409,1410],{},"max",[604,1412,1413],{},"round",[604,1415,1416],{},"floor",[604,1418,1419],{},"ceil",[604,1421,1422],{},"abs",[604,1424,1425],{},"sqrt",[604,1427,1428],{},"sin",[604,1430,1431],{},"cos",[604,1433,1434],{},"tan",[604,1436,1437],{},"log",[604,1439,1440],{},"exp",", and the constants ",[604,1443,1444],{},"pi",[604,1446,1447],{},"e",[29,1449,1450],{},"A parameter name cannot be blank: clearing the field restores the default name. The minimum must be below the maximum, and the step must be greater than zero, no larger than the range, and have at most two decimal places. Parameter minimums and maximums may be negative, and parameter values may be negative. Invalid rows and invalid formulas show an error and are not saved.",[29,1452,1453],{},"The formula result is always a whole number of story points. It is rounded to the nearest whole number with standard rounding (for example 5 \u002F 3 becomes 2, and 5 \u002F 2 becomes 3), and a result below zero becomes 0. The averaged result of a completed parametric session is rounded the same way.",[29,1455,1456],{},"Voters move the parameters and see the formula result below them. They vote the result value, and can change their parameters or withdraw the vote.",[29,1458,1459,1460,1463,1464,1467,1468,1471,1472,1474],{},"A vote records every parameter position together with the result. With open voting and after completion, the chart also draws the averaged positions, using the perspective's averaging method. When a parametric session completes, the voting panel keeps two tabs: ",[16,1461,1462],{},"Results"," with the chart, and the chart tab. A two-parameter perspective shows ",[16,1465,1466],{},"Quadrant"," with one dot per participant drawn from those recorded positions and a dashed crosshair for the averaged position; a perspective with three or more parameters shows ",[16,1469,1470],{},"Radar"," with one polygon per participant and a dotted averaged polygon. The final result and averaging controls stay below both tabs, and the ",[16,1473,612],{}," averaging mode averages each position and then applies the formula.",[29,1476,1477,1478,1481],{},"In the planning table each work item's parametric cell shows the result with an ",[16,1479,1480],{},"Edit vote"," control that opens the sliders and a cross-circle control that withdraws the vote. The result is never typed in directly.",[29,1483,1484,1485,334,1488,917,1491,1494],{},"In bulk voting a parametric perspective also has a selectable row with ",[16,1486,1487],{},"Affinity",[16,1489,1490],{},"Dot",[16,1492,1493],{},"Bucket"," tabs. The Bucket tab lists the voted estimates from the smallest to the largest, and each row opens the same slider popup; nothing in that table can be dragged.",[29,1496,1497,1498,1500],{},"In history, dashboards, and Jira write-back, a parametric result is treated as a number. It shows as story points, or as a work duration when ",[16,1499,1294],{}," is set.",[12,1502,1503],{},"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.",[12,1505,1506],{},"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.",[12,1508,1509],{},"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.",[12,1511,1512,1513,1516],{},"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 ",[16,1514,1515],{},"M",", during voting. The size label is written to Jira only when the perspective writes a T-shirt field.",[12,1518,1519],{},"To edit T-shirt story points:",[66,1521,1522,1525,1530,1538],{},[29,1523,1524],{},"Open the perspective settings.",[29,1526,1527,1528,569],{},"Go to ",[16,1529,913],{},[29,1531,1342,1532,1535,1536,569],{},[16,1533,1534],{},"T-Shirt"," in ",[16,1537,1220],{},[29,1539,1540,1541,1543],{},"In ",[16,1542,1230],{},", change the number next to a card title.",[233,1545,1547],{"id":1546},"estimation-target","Estimation Target",[614,1549,1550,1558],{},[617,1551,1552],{},[620,1553,1554,1556],{},[623,1555,988],{},[623,1557,631],{},[633,1559,1560,1570],{},[620,1561,1562,1567],{},[638,1563,1564],{},[16,1565,1566],{},"Default",[638,1568,1569],{},"Use Jira's built-in board estimation (recommended). The first board is selected automatically, and a link opens the board's estimation settings",[620,1571,1572,1576],{},[638,1573,1574],{},[16,1575,1312],{},[638,1577,1578],{},"Write to custom Jira fields for story points, time tracking, or T-shirt sizes",[12,1580,1581,1582,569],{},"Scrumpy always writes an accepted estimate to Jira, so there is no target that keeps the estimate only in the app. A perspective saved before this change with no target now uses ",[16,1583,1566],{},[12,1585,930,1586,1588],{},[16,1587,1566],{}," target needs an estimation board that has an estimation field. If no board is selected, or the board has no estimation field, an error appears below the board selector and a change to an estimation setting is not saved. Every other setting, such as open voting or the card sequence, is still saved. The option you picked stays selected while you fix the board, so your choice is not lost.",[12,1590,930,1591,1594,1595,334,1598,917,1600,1603,1604,1606],{},[16,1592,1593],{},"Estimation board"," list groups boards under ",[16,1596,1597],{},"Story points",[16,1599,884],{},[16,1601,1602],{},"No estimation",". Boards without an estimation field appear under ",[16,1605,1602],{}," and are disabled, so you can see them but cannot choose them. When no board is selected yet, the first board that has an estimation field is selected automatically.",[12,1608,1609,1610,1612],{},"The estimation board also decides where the perspective appears in Capacity planning. When the target is ",[16,1611,1566],{}," and the estimation board matches the board selected there, the perspective gets its own voting tab in the capacity plan, so you can estimate and vote without leaving the tab. A Field target, or a different board, keeps the perspective out of the capacity tabs.",[12,1614,1615],{},"When you use the Field target, the fields shown depend on the sequence and conversion:",[26,1617,1618,1624,1630],{},[29,1619,1620,1623],{},[16,1621,1622],{},"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 more than one field, each is updated and each appears as its own badge",[29,1625,1626,1629],{},[16,1627,1628],{},"Story Points",": A number field for story point values, shown for the numeric sequences and optionally for T-shirt perspectives",[29,1631,1632,1634,1635,1637],{},[16,1633,884],{},": A time tracking field for hour-based estimates, shown only when ",[16,1636,1294],{}," is set to a non-zero value",[12,1639,1640,1641,1643,1644,1647,1648,1650],{},"With the ",[16,1642,1566],{}," target, a T-shirt estimate is written as the story point number you set for the chosen card. For a T-shirt perspective, the ",[16,1645,1646],{},"T-shirt field"," also appears right next to the ",[16,1649,1593],{}," selector so the same accepted estimate can be written as its size label to that field as well.",[12,1652,1640,1653,1655],{},[16,1654,1312],{}," target, choose a story points field to write that mapped number, a T-shirt field to write the size label, the Time field, or any combination. The field controls are indented to line up with the board selector.",[12,1657,1640,1658,1660,1661,1663,1664,1666,1667,1669],{},[16,1659,1312],{}," target, at least one visible field must be selected. A T-shirt perspective can choose the story points field, the T-shirt field, the Time field when a conversion is set, or any combination of them. If none is selected, the dropdowns are marked invalid and the change is not saved. The ",[16,1662,1312],{}," choice stays selected while you pick a field, so the setting does not jump back to ",[16,1665,1566],{},". The Time field is hidden for every sequence when ",[16,1668,1294],{}," is 0 or empty, and its saved selection is cleared.",[12,1671,1672,1673,1675],{},"When every selected field is set on a T-shirt perspective, the story points field receives the mapped value, the T-shirt field receives the size label, and the Time field receives the converted duration. In the planning table, each configured field appears as its own badge in the order story points, time, T-shirt size, separated by middle dots; a field that is not configured is omitted. With the ",[16,1674,1566],{}," target, a T-shirt perspective writes the mapped story points to the board and the size label to the T-shirt field. The duration is shown only when the board is time-based; a numeric board shows the story points and the size label. A time board shows the duration and the size label. The voting panel uses the same units, so a numeric board shows story points, a time board shows the duration, and a Field target with both a story points field and a Time field shows both in the vote badges, chart labels, and final result. A duration is never shown when the target does not write a time value.",[12,1677,1678,1679,1682,1683,1685,1686,1689],{},"Below the estimation fields, ",[16,1680,1681],{},"Preview"," shows a sample accepted estimate using the same formatting as the voting panel. The sample follows the selected fields and the ",[16,1684,1294],{}," mapping, so it can show story points, the converted duration, and the T-shirt size together, for example ",[16,1687,1688],{},"3 sp · 5 days · XL",". Change a field or the conversion factor and the preview updates immediately. If no estimation field is selected, the preview is hidden.",[12,1691,1692],{},"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.",[12,1694,1695],{},"Changing an estimation setting refreshes any open planning table for that perspective. The table reads the affected work items from Jira again, so a column that showed the old field or board updates to the new one without a page reload. This covers the estimation target, sequence, story points field, time field, T-shirt field, story points to hours, and estimation board.",[233,1697,920],{"id":1698},"backup-restore",[12,1700,930,1701,1703],{},[16,1702,920],{}," tab holds:",[26,1705,1706,1712],{},[29,1707,1708,1711],{},[16,1709,1710],{},"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",[29,1713,1714,1717],{},[16,1715,1716],{},"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",[12,1719,1720],{},"Only space administrators can download or restore perspective settings. The download link is prepared when you open the tab and stays valid for one hour.",[12,1722,1723,1726],{},[16,1724,1725],{},"Changing settings during a session."," Settings fall into two groups. A change in the first group ends the running voting sessions for that perspective, because the round itself would no longer make sense. A change in the second group is safe at any time, so it never ends a session.",[12,1728,1729],{},"Changing any of these ends the running sessions for the perspective:",[26,1731,1732,1735,1738,1741,1744,1747,1750,1753],{},[29,1733,1734],{},"The card sequence",[29,1736,1737],{},"The active cards of the sequence",[29,1739,1740],{},"The extra cards",[29,1742,1743],{},"The free scale minimum or maximum",[29,1745,1746],{},"The parametric parameters and the parametric formula",[29,1748,1749],{},"The vote duration",[29,1751,1752],{},"Auto-complete",[29,1754,138],{},[12,1756,1757],{},"Reset to defaults also ends them, because it resets the settings above.",[12,1759,1760],{},"Changing any of these never ends a session, even while people are voting:",[26,1762,1763,1766,1769,1772,1775,1778,1780],{},[29,1764,1765],{},"The name, the description, and the Work types",[29,1767,1768],{},"Open voting, certainty, and variation",[29,1770,1771],{},"The averaging method",[29,1773,1774],{},"Card titles and card images",[29,1776,1777],{},"The T-shirt story points",[29,1779,1294],{},[29,1781,1782],{},"The estimation target, the estimation board, and the estimation fields",[12,1784,1785],{},"Changing the Work types can hide the perspective, and its session, from a work item whose work type you removed. The session is not cancelled, and it appears again when the work type is included.",[12,1787,1788],{},"A settings download is safe at any time and never affects a session. Loading a backup applies its settings like any other change, so it ends the running sessions only when the imported file changes one of the settings in the first group.",[21,1790,1792],{"id":1791},"managing-perspectives","Managing Perspectives",[12,1794,1795,1796,1799,1800,1803],{},"In the space settings page, each perspective is a tab, and you can add more with ",[16,1797,1798],{},"Add new perspective",". A new perspective starts with the name ",[16,1801,1802],{},"New view","; rename it to a short, recognizable name. For each perspective you can:",[26,1805,1806,1811,1816,1821,1826],{},[29,1807,1808,1810],{},[16,1809,267],{}," (General): Return the perspective to its initial settings",[29,1812,1813,1815],{},[16,1814,969],{}," (General): Immediately cancel all active voting sessions for the perspective. This cannot be undone, and all participants lose their current votes",[29,1817,1818,1820],{},[16,1819,975],{}," (General): Remove the perspective and all its sessions permanently. The Default perspective cannot be deleted",[29,1822,1823,1825],{},[16,1824,1710],{}," (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",[29,1827,1828,1830],{},[16,1829,1716],{}," (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",[12,1832,1833],{},"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.",[12,1835,1836],{},"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.",{"title":153,"searchDepth":154,"depth":154,"links":1838},[1839,1840,1841,1852],{"id":827,"depth":154,"text":828},{"id":867,"depth":154,"text":868},{"id":900,"depth":154,"text":901,"children":1842},[1843,1844,1845,1846,1847,1848,1849,1850,1851],{"id":927,"depth":784,"text":907},{"id":979,"depth":784,"text":910},{"id":1072,"depth":784,"text":1073},{"id":1114,"depth":784,"text":1115},{"id":1194,"depth":784,"text":1195},{"id":1201,"depth":784,"text":913},{"id":1338,"depth":784,"text":1339},{"id":1546,"depth":784,"text":1547},{"id":1698,"depth":784,"text":920},{"id":1791,"depth":154,"text":1792},"Set up perspectives in Scrumpy: voting rules, card sequences, averaging methods and the Jira field each estimate is written to.","\u002Fog\u002Fguide-estimation-perspectives.jpg",[1856,1857,1858,166],"estimation perspectives","jira story points","pert estimation",{},"\u002Fgetting-started\u002Festimation-perspectives",{"title":819,"description":1853},{"loc":1860,"lastmod":802},"estimation-perspectives","guide\u002Fen\u002Festimation-perspectives","guide\u002Festimation-perspectives","G6e_NyDdXo7KjkRHJalTURKglnw_qMcVk88OAPmeSPw",{"id":1868,"title":1869,"body":1870,"dateModified":802,"datePublished":160,"description":2104,"extension":162,"heading":2105,"image":2106,"imageAlt":2105,"keywords":2107,"locale":168,"meta":2111,"navigation":170,"order":2112,"path":2113,"section":173,"seo":2114,"sitemap":2115,"slug":2116,"stem":2117,"translationKey":2118,"__hash__":2119},"guide\u002Fguide\u002Fen\u002Fchat.md","Chat and Communication | Scrumpy Planning Poker",{"type":9,"value":1871,"toc":2093},[1872,1879,1882,1885,1889,1921,1925,1930,1940,1946,1949,1952,1956,1971,1975,1979,1982,1986,1989,1993,1997,2002,2006,2012,2016,2028,2058,2072,2075,2079],[12,1873,1874,1875,1878],{},"Every voting session includes a built-in chat panel for real-time team communication. Chat messages and their reactions are kept for 72 hours after the last change. In a planning session, the planning-session chat and the chats of its work items form one shared conversation: a message sent from any chat tab of the planning session belongs to that session and appears in every chat tab of the session, even when the work item is not shown in the other tab. A message sent from the work item panel outside a planning session is not part of any planning session; it appears only in the chat tabs that show that work item. Completing a planning session also removes its planning-session messages, the work item messages of its items, and their reactions. In Capacity planning, the ",[16,1876,1877],{},"Chat"," tab in the right-hand tabs shows the same session conversation; selecting a work item only chooses where a new message is sent.",[12,1880,1881],{},"You only see chat for work items you can open in Jira. A work item hidden from you by Jira issue-level security is not returned, even if you know its key.",[12,1883,1884],{},"When a work item has no messages yet, the chat shows an empty state that invites you to start the conversation. The work item Chat tab shows every message of that work item, including messages sent from a planning session, and the planning chat of the planning session that lists it as an item. It does not show messages of other work items. Open a planning session chat tab to read the full session conversation. A message you send from the work item panel outside a planning session stays in that work item's chat and appears only in the chat tabs that show that work item. A work item outside every planning session shows only its own chat.",[21,1886,1888],{"id":1887},"chat-features","Chat Features",[26,1890,1891,1897,1903,1909,1915],{},[29,1892,1893,1896],{},[16,1894,1895],{},"Rich text editing",": bold, italic, links, lists, and code blocks",[29,1898,1899,1902],{},[16,1900,1901],{},"Private messages",": moderators and voters can mark a message as private",[29,1904,1905,1908],{},[16,1906,1907],{},"Thumbs up\u002Fdown",": react to messages with voting buttons",[29,1910,1911,1914],{},[16,1912,1913],{},"Edit and delete",": authors can edit or delete their own messages",[29,1916,1917,1920],{},[16,1918,1919],{},"Live delivery",": messages appear instantly, no page refresh needed. If the space has a password, live delivery starts after you enter it. You also need to be able to browse the space in Jira to receive live messages.",[21,1922,1924],{"id":1923},"sending-a-message","Sending a Message",[61,1926],{"alt":1927,"caption":1928,"stem":1929},"A rich chat message being composed with the Send button","Sending a message","guide-chat-sending",[12,1931,1932,1933,1936,1937,1939],{},"Write in the message box and press ",[16,1934,1935],{},"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 ",[16,1938,1935],{}," button never shows a spinner and never blocks you while the message is being saved.",[12,1941,1942,1943,1945],{},"In a planning session, a small note under ",[16,1944,1935],{}," reminds you that the chat history belongs to that planning session.",[12,1947,1948],{},"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.",[12,1950,1951],{},"A message can hold up to 8,000 characters. When new text would push a combined message over that limit, the chat starts a new message instead. To keep one person from flooding the conversation, you can send one message per second, up to 20 per minute and 500 per day in the same work item. When you reach a limit, the chat tells you how many seconds to wait, your text stays in the message box, and no message is sent. A message that uses formatting the chat cannot display is not sent either, and the chat explains why. If a stored message still cannot be displayed, the conversation shows a short note in its place and the rest of the chat keeps working.",[21,1953,1955],{"id":1954},"message-details","Message Details",[12,1957,1958,1959,1962,1963,1966,1967,1970],{},"Each message shows its author, the author's role (Moderator, Voter, or Guest), the time of its first text, and one action row. Every message is the same width, and a colored accent on its left and right side tells your messages from the other participants' messages. When you send a message right after your own previous message, the new text is added to that message after a single newline. The combined message keeps one author header, one time, and one action row. Editing it edits the combined text. A message from another participant, a private or public change, or a role change starts a new message. Your own messages sit on the right side of the conversation, and messages from other participants sit on the left. A message that has been edited shows an ",[16,1960,1961],{},"Edited"," tag, and a private message shows a ",[16,1964,1965],{},"Private"," tag. When this work item belongs to a planning session, its messages also appear in the planning-session chat and in the chat of every other work item in the session. Every work item message shows its work item key as a small link at the start of the action row, in every chat panel, so you can tell which work item it came from. The work item chat also shows the planning session messages and the messages of the other work items in the session. A work item outside every planning session shows only its own messages. Only the five newest messages are shown at first; use ",[16,1968,1969],{},"Load more ..."," to load the next five until the full history is visible.",[21,1972,1974],{"id":1973},"reactions","Reactions",[61,1976],{"alt":1977,"caption":1974,"stem":1978},"A chat message with thumbs up and thumbs down reactions","guide-chat-reactions",[12,1980,1981],{},"Every message has a single action row below the message text. The row has a square thumbs up button and a square thumbs down button, with the number of reactions beside each button. On your own messages the row also has a square edit button and a square delete button, the same size as the reaction buttons. The reaction buttons, and the edit and delete buttons on your own messages, sit at the right edge of the action row for every participant. While a message you just sent is still being saved, its action row is already present but its buttons are disabled, so the layout does not jump when the message is confirmed. 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, and both reaction buttons stay available while the change is saved. Counts also update for everyone right away. If a reaction cannot be saved, it is rolled back.",[21,1983,1985],{"id":1984},"editing-and-deleting","Editing and Deleting",[12,1987,1988],{},"You can edit or delete only the messages you wrote. Editing a combined message changes all of its text. The edit and delete controls in the message action row are the same size as the reaction buttons. While an edit is open, the edit button shows a loading indicator and is disabled. 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.",[21,1990,1992],{"id":1991},"private-messages","Private Messages",[61,1994],{"alt":1995,"caption":1901,"stem":1996},"A private chat message with the Private tag","guide-chat-private",[12,1998,930,1999,2001],{},[16,2000,1965],{}," 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. Reactions follow the same rule: you can react only to messages you can see, so a guest cannot react to a private message.",[21,2003,2005],{"id":2004},"new-message-notifications","New Message Notifications",[12,2007,2008,2009,2011],{},"When a new message arrives while you are on another part of the panel, a red dot appears on the ",[16,2010,1877],{}," tab. Guests are not notified about private messages.",[21,2013,2015],{"id":2014},"planning-session-chat-without-a-selected-work-item","Planning Session Chat Without a Selected Work Item",[12,2017,1540,2018,334,2020,917,2022,2024,2025,2027],{},[16,2019,340],{},[16,2021,343],{},[16,2023,346],{},", the ",[16,2026,1877],{}," tab is always available and always shows the full session conversation: every message sent from the planning session, ordered by publish time, plus messages sent from outside the session for the work items the tab shows.",[26,2029,2030,2045,2050],{},[29,2031,1540,2032,2034,2035,2037,2038,2041,2042,2044],{},[16,2033,340],{},", the same chat appears in the selected work item's ",[16,2036,1877],{}," tab, when a perspective row is open in alternative voting, and when no row is selected. With no work item, the right panel shows a ",[16,2039,2040],{},"Details"," tab with the no-selection message and a ",[16,2043,1877],{}," tab with the session conversation.",[29,2046,1540,2047,2049],{},[16,2048,343],{},", the tab stays available when a work item is selected, when no work item is selected, and when a closed sprint is selected. The conversation is the same in every case and includes every message sent from the session, plus messages sent from outside the session for the work items in the capacity plan. A selected work item only chooses where a new message is sent: the work item chat. With no selection or a closed sprint, a new message goes to the planning session chat.",[29,2051,1540,2052,2054,2055,2057],{},[16,2053,346],{},", the side panel keeps the ",[16,2056,1877],{}," tab available with no work item selected. The conversation is the same merged conversation and includes every message sent from the session, plus messages sent from outside the session for every work item the standup shows. The focused work item only chooses where a new message is sent.",[12,2059,2060,2061,430,2063,2065,2066,2068,2069,2071],{},"The tab you choose is remembered in the planning session. When you follow the moderator, your tab switches with the moderator. The same tab opens after you reload the page. This applies to the ",[16,2062,2040],{},[16,2064,1877],{}," tabs in the Refinement\u002Fgrooming side panel and to the ",[16,2067,1877],{}," tab in alternative voting. Changing the focused work item never moves the Chat tab and never resets its messages or its ",[16,2070,1969],{}," position.",[12,2073,2074],{},"Chat messages and their reactions are kept for 72 hours after the last change. Completing a planning session removes both kinds of message and their reactions.",[21,2076,2078],{"id":2077},"when-to-use-chat","When to Use Chat",[26,2080,2081,2084,2087,2090],{},[29,2082,2083],{},"Discussing estimation discrepancies during a voting round",[29,2085,2086],{},"Clarifying requirements before casting votes",[29,2088,2089],{},"Note-taking and context sharing during planning sessions",[29,2091,2092],{},"Quick polling with thumbs up\u002Fdown reactions",{"title":153,"searchDepth":154,"depth":154,"links":2094},[2095,2096,2097,2098,2099,2100,2101,2102,2103],{"id":1887,"depth":154,"text":1888},{"id":1923,"depth":154,"text":1924},{"id":1954,"depth":154,"text":1955},{"id":1973,"depth":154,"text":1974},{"id":1984,"depth":154,"text":1985},{"id":1991,"depth":154,"text":1992},{"id":2004,"depth":154,"text":2005},{"id":2014,"depth":154,"text":2015},{"id":2077,"depth":154,"text":2078},"Use the built-in chat during voting: messages, reactions, private replies and how chat history follows a planning session.","Chat and Communication","\u002Fog\u002Fguide-chat.jpg",[2108,2109,2110],"planning poker chat","jira estimation","team collaboration",{},4,"\u002Fgetting-started\u002Fchat",{"title":1869,"description":2104},{"loc":2113,"lastmod":802},"chat","guide\u002Fen\u002Fchat","guide\u002Fchat","DNSPlNCmCcrs8Sy4wEzGbw71zpOn9fhN12TIpMnpRtE",{"id":2121,"title":2122,"body":2123,"dateModified":802,"datePublished":160,"description":3007,"extension":162,"heading":1069,"image":3008,"imageAlt":1069,"keywords":3009,"locale":168,"meta":3013,"navigation":170,"order":3014,"path":1068,"section":173,"seo":3015,"sitemap":3016,"slug":3017,"stem":3018,"translationKey":3019,"__hash__":3020},"guide\u002Fguide\u002Fen\u002Fvoting-session-controls.md","Voting Session Controls | Scrumpy Planning Poker",{"type":9,"value":2124,"toc":2975},[2125,2128,2132,2135,2164,2167,2170,2183,2187,2193,2198,2288,2292,2295,2298,2320,2348,2351,2355,2358,2361,2368,2374,2381,2388,2394,2398,2408,2412,2415,2418,2422,2425,2428,2431,2434,2440,2443,2446,2449,2466,2469,2472,2475,2479,2488,2495,2529,2541,2545,2548,2552,2558,2562,2565,2573,2577,2586,2593,2621,2681,2685,2688,2702,2705,2708,2712,2715,2744,2748,2751,2771,2810,2814,2817,2838,2841,2844,2848,2851,2855,2870,2874,2877,2891,2895,2901,2915,2918,2922,2925,2934,2938,2944,2948,2965],[12,2126,2127],{},"This page explains the moderator and voter controls available during a voting session.",[21,2129,2131],{"id":2130},"session-lifecycle","Session Lifecycle",[12,2133,2134],{},"A voting session moves through these states:",[66,2136,2137,2146,2152,2158],{},[29,2138,2139,2142,2143,2145],{},[16,2140,2141],{},"Inactive",": No session is running. The moderator clicks ",[16,2144,313],{}," to begin.",[29,2147,2148,2151],{},[16,2149,2150],{},"Active",": Participants cast votes. A progress bar shows the remaining time.",[29,2153,2154,2157],{},[16,2155,2156],{},"Paused",": The moderator can pause to discuss before continuing.",[29,2159,2160,2163],{},[16,2161,2162],{},"Completed",": All votes are in. The moderator reviews and accepts the result.",[12,2165,2166],{},"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.",[12,2168,2169],{},"Changing a perspective setting that shapes the round ends the running sessions for that perspective. This covers the card deck, the free scale range, the parametric setup, the vote duration, auto-complete, and asynchronous voting. Changing the name, description, Work types, Open voting, certainty, variation, averaging, card titles or images, or the estimation target and fields is safe while people are voting and never ends a session. The perspectives guide lists both groups.",[12,2171,2172,2173,2176,2177,2179,2180,2182],{},"Start, Pause, Resume, Cancel, Restart, and Complete take effect right away. The controls do not lock while a change is saved: pressing Start shows the active controls, Pause shows Resume, Resume shows Pause, Cancel returns to Start, and Complete shows the completed controls at once. You can keep using the panel while the save finishes. Pausing stops the progress bar and the remaining time at once. Resuming continues them from where they stopped, so time spent paused does not count against the round. If an action cannot be saved, the panel returns to the previous controls and the progress bar returns to its previous position. Accept is the exception: it shows ",[16,2174,2175],{},"Updating estimation fields, please wait..."," until the estimate is written. ",[16,2178,491],{}," follows the ",[16,2181,999],{}," setting: with it on, the completed controls appear at once; with it off, the button shows a spinner and stays disabled until the completion is confirmed, so the hidden votes are revealed only then. A delayed update from an earlier session never affects a newly started one. If the same work item is open in the space page and in the Jira issue view at the same time, a vote, a pause, or a completion in one panel appears in the other without a refresh. This also applies when open voting is off: the other panel shows your own card, because it reads the session again for you.",[21,2184,2186],{"id":2185},"voting-card-sequences","Voting Card Sequences",[12,2188,2189,2190,2192],{},"Scrumpy supports seven card sequences, set per perspective. The full deck of a sequence is listed below; the ",[16,2191,1230],{}," setting can narrow it to a subset.",[61,2194],{"alt":2195,"caption":2196,"stem":2197},"The Available cards list in perspective settings","Card sequence settings","guide-card-sequences",[614,2199,2200,2208],{},[617,2201,2202],{},[620,2203,2204,2206],{},[623,2205,1220],{},[623,2207,913],{},[633,2209,2210,2220,2230,2240,2250,2260,2269,2279],{},[620,2211,2212,2217],{},[638,2213,2214],{},[16,2215,2216],{},"Regular",[638,2218,2219],{},"0, 0.5, 1, 2, 3, 5, 8, 13, 20, 40, 100, 200, ... up to 700",[620,2221,2222,2227],{},[638,2223,2224],{},[16,2225,2226],{},"Fibonacci",[638,2228,2229],{},"1, 2, 3, 5, 8, 13, 21, 34, 55, 89, 144, 233, ... up to 2584",[620,2231,2232,2237],{},[638,2233,2234],{},[16,2235,2236],{},"Tens",[638,2238,2239],{},"0, 10, 20, 30, ... up to 160",[620,2241,2242,2247],{},[638,2243,2244],{},[16,2245,2246],{},"Fingers",[638,2248,2249],{},"0 through 16",[620,2251,2252,2257],{},[638,2253,2254],{},[16,2255,2256],{},"Dice",[638,2258,2259],{},"1 through 18",[620,2261,2262,2266],{},[638,2263,2264],{},[16,2265,1534],{},[638,2267,2268],{},"XS, XS\u002FS, S, S\u002FM, M, M\u002FL, L, L\u002FXL, XL, XXL, XXXL, A, B, C, D, E, F",[620,2270,2271,2276],{},[638,2272,2273],{},[16,2274,2275],{},"Free Scale",[638,2277,2278],{},"Any integer between a configurable minimum and maximum",[620,2280,2281,2285],{},[638,2282,2283],{},[16,2284,1339],{},[638,2286,2287],{},"A number calculated from named parameters and a formula",[61,2289],{"alt":2290,"caption":2291,"stem":64},"The card deck in the voting panel","Voting cards",[12,2293,2294],{},"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. The result shows the size label when the perspective writes a T-shirt field, and story points otherwise.",[12,2296,2297],{},"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.",[12,2299,2300,2301,2304,2305,2307,2308,2311,2312,2314,2315,2317,2318,569],{},"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 ",[16,2302,2303],{},"Vote"," button below the slider. The slider position is remembered for this browser tab and this voting session, so a page refresh puts it back where you left it, even before you vote; a new session starts from the middle again. The ",[16,2306,2303],{}," button allows one vote per slider position: it disables right after you press it and becomes available again when you move the slider. It also stays disabled while your recorded vote is an extra emoji card, because no number has been picked yet. Once a vote is recorded, a ",[16,2309,2310],{},"Withdraw"," button appears beside it, and pressing it removes the vote (the same as removing a card vote). The selected number appears large above the slider, with a small ",[16,2313,1286],{}," suffix. The converted duration appears only when the estimation target writes a time value: a time board or a Time field shows the duration, and a Field target with both a story points field and a Time field shows both, for example ",[16,2316,1300],{},". A numeric board or a story points field shows story points only, and the perspective settings explain that the duration is not written. If your current vote is an extra emoji card, that card's value shows there instead, and moving the slider replaces it with the slider value; your vote stays on the extra card until you press ",[16,2319,2303],{},[12,2321,2322,2323,2325,2326,2328,2329,2332,2333,2335,2336,2338,2339,2341,2342,2344,2345,2347],{},"For Parametric, voters see the configured parameters stacked in the order the space administrator set. Each parameter shows its name above, a range control, and its current value below. The formula result appears in large text below the list with an ",[16,2324,1286],{}," suffix. The converted duration is appended only when the estimation target writes a time value: a time board or a Time field shows the duration, and a Field target with both a story points field and a Time field shows both, for example ",[16,2327,1300],{},". A numeric board or a story points field shows story points only, and the perspective settings explain that the duration is not written. It is always a whole number: the value is rounded to the nearest whole number (halves round up), and a result below zero is shown and voted as 0. The averaged result of a completed session is rounded the same way. To the right of the result, a small badge shows how far the rounded number is from the exact formula result, using at most two decimals: a negative value means the exact result is higher than the rounded number, and a positive value means it is lower. The badge shows ",[16,2330,2331],{},"0"," when the result is already whole, and it is hidden when the formula cannot be calculated or when the formula value is below zero, because that result is clamped to zero instead of rounded. The parameter values themselves may be negative when the perspective's minimum is negative. Move any parameter to recalculate the result, then press ",[16,2334,2303],{},". A recorded parametric result is shown when you reopen the panel; move a parameter to change it, or press ",[16,2337,2310],{}," to remove it. A ",[16,2340,2303],{}," button stays disabled until you move a parameter when you already have a recorded result. Parametric perspectives are not available as a bulk voting row in the planning table; use the work item panel. Your vote also records every parameter position, so the Results and Quadrant or Radar views can draw the parameters behind a recorded result after the session completes. Parametric voting also offers a ",[16,2343,1466],{}," view of your current slider positions when the perspective has exactly two parameters, and a ",[16,2346,1470],{}," view when it has three or more, described under Voting Tabs. Your slider positions are remembered for this browser tab and this voting session, so a page refresh puts them back where you left them, even before you vote; a new session starts from the middle again. A recorded parametric vote also puts the sliders on the positions that vote carries, so the voting panel and the planning table's bulk editor always show the same positions: voting here moves the bulk editor, and voting there moves these sliders.",[12,2349,2350],{},"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.",[21,2352,2354],{"id":2353},"perspective-tabs","Perspective Tabs",[12,2356,2357],{},"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 voted and how much time is left when a session is active.",[12,2359,2360],{},"The panel shows this complete view at once. The tabs, the session state, the votes, and any rank labels appear together, so the layout does not shift while it loads.",[12,2362,2363,2364,2367],{},"In the Refinement\u002Fgrooming 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, so the moderator also switches tabs for them. If you click another tab, the lock turns off and your own tab is remembered for the current browser tab. Clearing ",[16,2365,2366],{},"Lock to moderator"," stops you following too, and keeps the panel on the tab you were following.",[12,2369,2370,2371,2373],{},"A yellow ",[16,2372,1515],{}," 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. Use it as your pointer to the moderator's view: it stays on the moderator's tab after you open another tab, so you can see how far your tab has drifted from the moderator's. While you follow the moderator, the two tabs are the same. 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.",[12,2375,2376,2377,2380],{},"Below the tabs, the perspective's description appears in bold; when it has no description, ",[16,2378,2379],{},"No description"," is shown. The small gear beside it opens that perspective's settings in a new tab.",[12,2382,2383,2384,2387],{},"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 ",[16,2385,2386],{},"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 Refinement\u002Fgrooming tab, where the planning session is already open. When a space administrator hides the Space Estimations page in space settings, the line and its link are not shown.",[12,2389,2390,2391,2393],{},"If no perspective applies to the work item's work type, the panel shows ",[16,2392,953],{}," with the work type name and asks you to configure the space's perspective settings.",[21,2395,2397],{"id":2396},"link-to-the-space-page","Link to the Space Page",[12,2399,2400,2401,2404,2405,2407],{},"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 ",[16,2402,2403],{},"space page"," to open it in a new tab, or choose ",[16,2406,581],{}," 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. When a space administrator hides the Space Estimations page in space settings, the note is not shown.",[21,2409,2411],{"id":2410},"moderator-controls","Moderator Controls",[233,2413,313],{"id":2414},"start",[12,2416,2417],{},"Begins a new voting session for the current perspective. All eligible voters can now submit their estimates.",[233,2419,2421],{"id":2420},"pause-resume","Pause \u002F Resume",[12,2423,2424],{},"Temporarily stops the session. This is useful for team discussions when votes differ a lot. The timer is suspended while paused, and the progress bar and remaining time stop at once. After you resume, the countdown continues from where it stopped, so the pause does not use up the round. The panel shows who paused the session. Asynchronous sessions cannot be paused or resumed.",[233,2426,503],{"id":2427},"cancel",[12,2429,2430],{},"Ends the session entirely. All votes are discarded and the session is removed.",[233,2432,497],{"id":2433},"restart",[12,2435,2436,2437,2439],{},"Only a moderator sees this button, and only while the session is completed. It sits before ",[16,2438,503],{},". Pressing it starts a new round for the same perspective right away, with the configured required voters, so the panel returns to fresh voting without leaving the work item. The completed result and its votes are discarded, and the timer starts again from the beginning.",[12,2441,2442],{},"A restart is not a cancel. The work item keeps its place in that perspective's affinity and dot rankings, and an enforced bucket ranking keeps its mode. The panel goes from the completed result to the new round in one step, with no empty voting screen in between, and the other open windows follow at the same time. If the new round cannot be started, the completed session stays on screen with its result, so you can try again.",[233,2444,491],{"id":2445},"complete",[12,2447,2448],{},"Ends voting and reveals all submitted votes. The result is computed using the configured averaging method.",[12,2450,2451,2452,2454,2455,2457,2458,2460,2461,430,2463,2465],{},"With ",[16,2453,999],{}," on, the votes are already on screen, so the completed view appears as soon as you press ",[16,2456,491],{},". With ",[16,2459,999],{}," off, the button shows a spinner and stays disabled, and the votes and the completed view appear when the completion arrives, usually a moment later. While it waits, ",[16,2462,479],{},[16,2464,485],{}," are disabled too, so the session cannot be paused as it completes. If the completion cannot be saved, the button stops spinning and the session stays active with the votes still hidden. 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.",[233,2467,509],{"id":2468},"accept",[12,2470,2471],{},"Finalizes the estimate. Writes the result to Jira (according to the perspective's estimation target) and saves the session in the estimation history.",[12,2473,2474],{},"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.",[233,2476,2478],{"id":2477},"set-estimate","Set Estimate",[12,2480,2481,2482,2484,2485,2487],{},"Before accepting, the moderator can set a different estimate. Card sequences show an ",[16,2483,1308],{}," dropdown of the available values, and Free Scale shows a number field bounded by the configured minimum and maximum. Parametric also uses a number field, with no fixed minimum or maximum. When the estimation target writes a time value, the converted duration appears as a badge: after the number field for Free Scale, and beside the narrowed ",[16,2486,1308],{}," dropdown for card sequences. A numeric board or a story points field shows story points only. A Field target with both a story points field and a Time field shows both. Voters see the same units in the badges, with the story-point value first and the duration beside it when both are written. A time board or Time field shows the duration only, with no story-point badge. The badge follows the value you pick. This is useful when the team's discussion leads to a consensus that differs from the averaged result.",[12,2489,2490,2491,2494],{},"Beside it, the ",[16,2492,2493],{},"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.",[12,2496,2497,2498,430,2500,2502,2503,2505,2506,2508,2509,2511,2512,2514,2515,2517,2518,2520,2521,430,2523,2525,2526,2528],{},"For parametric perspectives the ",[16,2499,1308],{},[16,2501,2493],{}," controls share one line, and an ",[16,2504,1058],{}," dropdown sits directly below the ",[16,2507,2493],{}," dropdown, at the same width, aligned to the right side of the row. It chooses how the final result is built. ",[16,2510,1597],{}," is the default and works as before: average the story points each participant voted. ",[16,2513,612],{}," averages every parameter position across the participants with the averaging method, then applies the parametric formula to those averaged positions. The averaged positions keep their decimals; the formula result is still a whole story point, like every parametric result. Switching between the two modes recomputes the result and updates the override field. With ",[16,2516,612],{}," and no manual override, the same rounding badge appears at the right side of the final result row. It is hidden once you set an override by hand, when the mode is ",[16,2519,1597],{},", and when no vote recorded parameter positions. For card sequences, including T-shirt, ",[16,2522,1308],{},[16,2524,2493],{}," also stay on one line. The ",[16,2527,1308],{}," control is 245px wide, each option shows the combined story points, time, and size label when those units are configured, and no separate unit lozenge is shown beside it.",[12,2530,2531,2532,2534,2535,2537,2538,2540],{},"When a parametric session completes, these controls stay visible below both the ",[16,2533,1462],{}," tab and the chart tab (",[16,2536,1466],{}," or ",[16,2539,1470],{},"), so you can change the result from either tab. Changing the averaging method also redraws the averaged marker in the chart tab.",[233,2542,2544],{"id":2543},"remind","Remind",[12,2546,2547],{},"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.",[233,2549,2551],{"id":2550},"required-voters","Required Voters",[12,2553,930,2554,2557],{},[16,2555,2556],{},"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.",[21,2559,2561],{"id":2560},"voter-controls","Voter Controls",[12,2563,2564],{},"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: the other cards are never sent to your browser, so they cannot be read by inspecting the panel. 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.",[12,2566,2567,2568,430,2570,2572],{},"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 ",[16,2569,2303],{},[16,2571,2310],{}," buttons below the slider for the same cast and remove actions.",[21,2574,2576],{"id":2575},"voting-tabs","Voting Tabs",[12,2578,2579,2580,2582,2583,2585],{},"The planning session's inline voting panel includes a ",[16,2581,2040],{}," tab. ",[16,2584,2040],{}," answers \"what are we estimating?\" without leaving the panel: the current work item summary appears at the top, and below it the work item description is shown as rich text. The summary and description have no section labels. Participants who are not moderators see the description without an avatar. The summary and description are read from Jira once per work item for the open page and are then reused when you switch perspective or tab, so a repeated visit is instant. A summary or description change saved anywhere in the app updates them right away; a change made directly in Jira appears after you reload the page. If the work item has no description, the tab says so. A summary or description change made in the Details tab appears for other participants without a reload. An edit in one perspective also updates the Details tab of every other perspective in the same panel without a reload. A summary or description edit saves when you click away, switch to another tab, or close the panel, even if the short description pause has not finished. The work item key in the planning table shows the summary in a tooltip.",[12,2587,2588,2589,2592],{},"Only moderators can change the work item. A moderator edits the summary inline and the description in the rich-text editor. The summary edit has no action buttons: click away or press Enter to save, and press Escape to cancel. Clearing the summary shows ",[16,2590,2591],{},"The summary cannot be empty."," in the inline edit and does not save it. The new summary appears immediately, and the planning-table tooltip follows it; if Jira rejects the change, the previous summary returns and an error is shown. The description saves in the background shortly after you stop typing, and switching tabs flushes a pending save. A failed save keeps the content and shows an error. Participants see the same content read-only.",[12,2594,2595,2596,2598,2599,2601,2602,2604,2605,2607,2608,430,2610,2612,2613,334,2615,2617,2618,2620],{},"While a session runs in the planning session's inline panel, ",[16,2597,1462],{}," appears with open voting, and a parametric perspective adds its chart tab. The order is ",[16,2600,2303],{},", then ",[16,2603,1462],{}," when open voting is on, then the chart tab, then ",[16,2606,2040],{},". With closed voting and no chart, the panel keeps ",[16,2609,2303],{},[16,2611,2040],{},"; with closed voting and a chart, the chart sits between them. The standalone work item panel keeps ",[16,2614,2303],{},[16,2616,1462],{}," when open voting is on, and the chart tab, but it has no ",[16,2619,2040],{}," tab.",[26,2622,2623,2626,2631,2636,2641,2646,2651,2656],{},[29,2624,2625],{},"Both tab contents use the full width of the voting panel.",[29,2627,2628,2630],{},[16,2629,2303],{}," contains the card, free-scale, or parametric voting controls.",[29,2632,2633,2635],{},[16,2634,2040],{}," in the planning session's inline panel shows the work item summary at the top and the work item description below it. Moderators can edit both; everyone else reads them.",[29,2637,2638,2640],{},[16,2639,1466],{}," appears for a two-parameter parametric perspective and shows a scatter chart with one axis per parameter. The axes use the parameter's real values, including negative ones, so nothing is scaled to a percentage. Your own dot follows the sliders as you move them, so you can preview your next vote. With open voting, every other participant who voted appears as a dot in a different colour, and a dashed crosshair marks the averaged parameter positions calculated with the perspective's averaging method from the recorded votes only. With closed voting, the Quadrant tab draws only your own dot, with no other participants and no averaged crosshair, until the session completes. There is no legend. The chart is a picture: it cannot be clicked, dragged, or focused.",[29,2642,2643,2645],{},[16,2644,1470],{}," appears for a parametric perspective with three or more parameters and shows a radar chart of the votes. Each ray is a parameter, scaled between the parameter's minimum (the centre) and its maximum (the outer ring), so negative minimums work too. Your own polygon follows the sliders as you move them, so you can preview your next vote. With open voting, every other participant who voted appears as its own polygon in a different colour, and a dotted neutral polygon shows the averaged parameter positions calculated with the perspective's averaging method from the recorded votes only. With closed voting, the Radar tab draws only your own live values, with no other participants and no averaged polygon, until the session completes. There is no legend. The chart is a picture: it cannot be clicked, dragged, or focused.",[29,2647,2648,2650],{},[16,2649,1462],{}," appears while the session is running only with open voting. It contains only the result chart. Before anyone votes it shows an empty state saying that there are no votes yet. As votes arrive, the chart updates.",[29,2652,2653,2654,569],{},"The selected tab is remembered in the current browser tab, so a reload keeps your choice. A remembered chart tab on a perspective that is not parametric falls back to ",[16,2655,2303],{},[29,2657,2658,2659,2661,2662,2664,2665,430,2667,2669,2670,2672,2673,2582,2675,2677,2678,2680],{},"When a session completes, the planning session's inline panel keeps tabs whether open voting was on or off. A parametric session shows ",[16,2660,1462],{},", its chart tab, and ",[16,2663,2040],{},"; a non-parametric session shows ",[16,2666,1462],{},[16,2668,2040],{},". The standalone work item panel keeps ",[16,2671,1462],{}," and the chart tab when the perspective is parametric, with no ",[16,2674,2040],{},[16,2676,1466],{}," shows one dot per participant vote in the same colours as the open-voting chart plus the dashed averaged crosshair; ",[16,2679,1470],{}," shows one polygon per participant vote plus the dotted averaged polygon. The final result control and both averaging controls stay visible below the tabs and work the same from either tab. If a vote was recorded without parameter positions, the chart tab says so instead of drawing it.",[21,2682,2684],{"id":2683},"ranking-above-the-cards","Ranking Above the Cards",[12,2686,2687],{},"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:",[26,2689,2690,2696],{},[29,2691,2692,2695],{},[16,2693,2694],{},"Affinity rank"," for the work item's affinity position",[29,2697,2698,2701],{},[16,2699,2700],{},"Dot rank"," for the number of dots the work item has",[12,2703,2704],{},"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.",[12,2706,2707],{},"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.",[21,2709,2711],{"id":2710},"panel-header-controls","Panel Header Controls",[12,2713,2714],{},"The voting panel header has two controls:",[26,2716,2717,2723],{},[29,2718,2719,2722],{},[16,2720,2721],{},"Sound toggle",": mutes or unmutes sound notifications. This is a quick toggle, separate from the volume slider in your Personal settings.",[29,2724,2725,2728,2729,2731,2732,2735,2736,2739,2740,2743],{},[16,2726,2727],{},"Your role badge",": shows ",[16,2730,1515],{}," for a Moderator who cannot vote, ",[16,2733,2734],{},"M\u002FV"," for a Moderator who is also a Voter, ",[16,2737,2738],{},"V"," for a Voter, or ",[16,2741,2742],{},"G"," for a Guest. Hover it for a tooltip that states the current role, and click it to open the permissions settings.",[21,2745,2747],{"id":2746},"viewing-results","Viewing Results",[12,2749,2750],{},"When a voting session completes, the results are shown in a chart. Three chart types are available (set in your Personal settings):",[26,2752,2753,2759,2765],{},[29,2754,2755,2758],{},[16,2756,2757],{},"Pie",": Circle chart showing vote distribution",[29,2760,2761,2764],{},[16,2762,2763],{},"Vertical bar",": Bar chart for comparing vote values",[29,2766,2767,2770],{},[16,2768,2769],{},"Horizontal bar",": Bar chart with readable labels",[12,2772,2773,2774,2777,2778,2780,2781,2783,2784,2786,2787,2789,2790,2793,2794,2796,2797,2800,2801,2804,2805,2809],{},"The result also shows the computed estimate using the perspective's averaging method. Labels follow the estimation target. A numeric board or a story points field shows story points only. A time board or a Time field shows the duration only, for example ",[16,2775,2776],{},"1 day 3 hours",". When a Field target has both a story points field and a Time field, both appear, for example ",[16,2779,1300],{},". A T-shirt perspective shows only the configured parts in one badge, in the order story points, time, T-shirt size, for example ",[16,2782,1304],{},". When the perspective has no T-shirt field, the ",[16,2785,1308],{}," dropdown and the result label show story points instead of T-shirt sizes. When the T-shirt field is configured, every ",[16,2788,1308],{}," option uses the same combined label as the result, for example ",[16,2791,2792],{},"3 sp · 8 days · XL",", and the separate lozenge beside the dropdown is no longer shown. The same combined dropdown labels and the same 245px width apply to the other card sequences, so a card option shows the story points and duration requested by the perspective fields. The same labels appear in the vote list, the result chart, and the final result. If ",[16,2795,1294],{}," is set but the target does not write a time value, the duration is not displayed anywhere and the perspective settings explain why. With the ",[16,2798,2799],{},"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 ",[1066,2802,2803],{"to":1860},"Perspectives","). Before accepting, the moderator can recalculate the result with a different averaging method or override it by hand (see ",[2806,2807,2478],"a",{"href":2808},"#set-estimate",").",[233,2811,2813],{"id":2812},"certainty-variation-and-deviation","Certainty, Variation, and Deviation",[12,2815,2816],{},"Optional indicators help you read a result. Certainty and Variation are set per perspective in the Voting settings; Deviation appears automatically when PERT applies.",[26,2818,2819,2824,2829],{},[29,2820,2821,2823],{},[16,2822,1009],{}," 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%.",[29,2825,2826,2828],{},[16,2827,1019],{}," 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.",[29,2830,2831,2833,2834,2837],{},[16,2832,1175],{}," is how spread out the PERT three points are: ",[604,2835,2836],{},"(P - O) \u002F 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.",[12,2839,2840],{},"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.",[12,2842,2843],{},"Certainty, Variation, and Deviation appear once the session is completed. When open voting is on, they also appear live while the session is running.",[21,2845,2847],{"id":2846},"participant-list","Participant List",[12,2849,2850],{},"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.",[21,2852,2854],{"id":2853},"voting-indicators","Voting Indicators",[12,2856,2857,2858,2861,2862,2865,2866,2869],{},"After casting a vote, you see an ",[16,2859,2860],{},"Already voted"," confirmation. If the session uses closed voting (open voting off), you see a ",[16,2863,2864],{},"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 ",[16,2867,2868],{},"Please vote!"," indicator in their own panel.",[21,2871,2873],{"id":2872},"asynchronous-voting","Asynchronous Voting",[12,2875,2876],{},"When asynchronous voting is on:",[26,2878,2879,2882,2885,2888],{},[29,2880,2881],{},"Participants vote at their own convenience",[29,2883,2884],{},"The moderator collects results when ready",[29,2886,2887],{},"Sessions cannot be paused or resumed",[29,2889,2890],{},"There is no countdown timer or progress bar unless a deadline is set",[233,2892,2894],{"id":2893},"voting-must-complete-until","Voting must complete until",[12,2896,2897,2898,2900],{},"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 ",[16,2899,2894],{}," control with a date picker and a time picker:",[26,2902,2903,2906,2909,2912],{},[29,2904,2905],{},"The date cannot be in the past, and times are offered in 30-minute slots.",[29,2907,2908],{},"Choosing both a date and a time sets the deadline.",[29,2910,2911],{},"Once set, a progress bar and a countdown appear, and the session completes when the deadline is reached.",[29,2913,2914],{},"Clearing either the date or the time removes the deadline and hides the countdown again.",[12,2916,2917],{},"The control is visible only to moderators, and only while the session is not completed.",[21,2919,2921],{"id":2920},"password-protection","Password Protection",[12,2923,2924],{},"If the moderator has set a password in space settings, anyone opening a Scrumpy surface must enter it before reaching the voting interface or live updates. This includes the work item panel, the Space Estimations page, the estimation log, and the add-to-planning action. Live voting, chat, and planning updates are only delivered after the password is entered. Space settings are not locked by this password; they follow the Jira permissions for the space. The password must be at least 8 characters, and the server enforces that limit even when the settings form is bypassed. Scrumpy checks the password after you pause typing, not on every keystroke, and it does not send an entry shorter than eight characters, so an incomplete password never spends an attempt. It is stored as a slow salted hash, so it cannot be read back or reused to sign in without the password, and it can only be changed or removed. Live updates also require that you can browse the space in Jira, with or without a password. After five incorrect attempts in fifteen minutes, the account is locked out for fifteen minutes and the password field is disabled. Every attempt counts on its own, even when several are sent at the same moment. A successful entry clears the failed-attempt count. After you enter it once, Scrumpy remembers it for your account for 30 days and shares it across every Scrumpy surface, so you do not have to enter it again. The remembered entry is cleared when the password is changed or removed.",[12,2926,2927,2928,430,2931,2933],{},"While a password is set, the Permissions tab shows a warning message that the space's data is protected, with ",[16,2929,2930],{},"Remove protection",[16,2932,581],{}," actions.",[21,2935,2937],{"id":2936},"team-information","Team Information",[12,2939,930,2940,2943],{},[16,2941,2942],{},"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.",[21,2945,2947],{"id":2946},"your-role","Your Role",[12,2949,2950,2951,2731,2953,2735,2955,2957,2958,2960,2961,2964],{},"The Scrumpy voting panel header shows a badge with your current role: ",[16,2952,1515],{},[16,2954,2734],{},[16,2956,2738],{}," for a Voter, and ",[16,2959,2742],{}," for a Guest. Hover it for a tooltip that states your role. The badge is a link to the ",[16,2962,2963],{},"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.",[12,2966,2967,2968,2971,2972,2974],{},"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 ",[16,2969,2970],{},"voters list"," to the ",[16,2973,2963],{}," permissions in a new tab.",{"title":153,"searchDepth":154,"depth":154,"links":2976},[2977,2978,2979,2980,2981,2992,2993,2994,2995,2996,2999,3000,3001,3004,3005,3006],{"id":2130,"depth":154,"text":2131},{"id":2185,"depth":154,"text":2186},{"id":2353,"depth":154,"text":2354},{"id":2396,"depth":154,"text":2397},{"id":2410,"depth":154,"text":2411,"children":2982},[2983,2984,2985,2986,2987,2988,2989,2990,2991],{"id":2414,"depth":784,"text":313},{"id":2420,"depth":784,"text":2421},{"id":2427,"depth":784,"text":503},{"id":2433,"depth":784,"text":497},{"id":2445,"depth":784,"text":491},{"id":2468,"depth":784,"text":509},{"id":2477,"depth":784,"text":2478},{"id":2543,"depth":784,"text":2544},{"id":2550,"depth":784,"text":2551},{"id":2560,"depth":154,"text":2561},{"id":2575,"depth":154,"text":2576},{"id":2683,"depth":154,"text":2684},{"id":2710,"depth":154,"text":2711},{"id":2746,"depth":154,"text":2747,"children":2997},[2998],{"id":2812,"depth":784,"text":2813},{"id":2846,"depth":154,"text":2847},{"id":2853,"depth":154,"text":2854},{"id":2872,"depth":154,"text":2873,"children":3002},[3003],{"id":2893,"depth":784,"text":2894},{"id":2920,"depth":154,"text":2921},{"id":2936,"depth":154,"text":2937},{"id":2946,"depth":154,"text":2947},"Moderator and voter controls in a Scrumpy voting session: start, pause, restart, accept, override and required voters.","\u002Fog\u002Fguide-voting-session-controls.jpg",[3010,3011,3012,2109],"planning poker voting","voting session","scrum master",{},5,{"title":2122,"description":3007},{"loc":1068,"lastmod":802},"voting-session-controls","guide\u002Fen\u002Fvoting-session-controls","guide\u002Fvoting-session-controls","9Ny0m9NoshmsBtIFdufMd_uXewwTPX7WtrNvLmSwnpY",{"id":3022,"title":3023,"body":3024,"dateModified":159,"datePublished":160,"description":3168,"extension":162,"heading":3043,"image":3169,"imageAlt":3043,"keywords":3170,"locale":168,"meta":3174,"navigation":170,"order":3175,"path":3176,"section":173,"seo":3177,"sitemap":3178,"slug":3179,"stem":3180,"translationKey":3181,"__hash__":3182},"guide\u002Fguide\u002Fen\u002Fpersonal-settings.md","Personal Settings | Scrumpy Planning Poker",{"type":9,"value":3025,"toc":3162},[3026,3029,3032,3036,3041,3045,3086,3090,3096,3109,3112,3116,3119,3149,3152,3155,3159],[12,3027,3028],{},"Personal settings let each team member customize their Scrumpy experience. These settings are stored per user and follow you across all spaces.",[12,3030,3031],{},"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.",[21,3033,3035],{"id":3034},"chart-type","Chart Type",[12,3037,3038,3039,569],{},"Controls how voting results are visualized after a session completes. The default is ",[16,3040,2757],{},[61,3042],{"alt":3043,"caption":3043,"stem":3044},"Personal Settings","guide-personal-settings",[614,3046,3047,3057],{},[617,3048,3049],{},[620,3050,3051,3054],{},[623,3052,3053],{},"Option",[623,3055,3056],{},"Best for",[633,3058,3059,3068,3077],{},[620,3060,3061,3065],{},[638,3062,3063],{},[16,3064,2757],{},[638,3066,3067],{},"Quick glance at vote distribution",[620,3069,3070,3074],{},[638,3071,3072],{},[16,3073,2763],{},[638,3075,3076],{},"Comparing individual vote values",[620,3078,3079,3083],{},[638,3080,3081],{},[16,3082,2769],{},[638,3084,3085],{},"Reading vote labels comfortably",[21,3087,3089],{"id":3088},"card-visuals","Card Visuals",[12,3091,3092,3093,569],{},"Adjusts the appearance of voting cards in the estimation panel. The default is ",[16,3094,3095],{},"Colorful",[26,3097,3098,3103],{},[29,3099,3100,3102],{},[16,3101,3095],{},": Bright, visually distinct cards with gradients",[29,3104,3105,3108],{},[16,3106,3107],{},"Minimalistic",": Subdued, flat design for less visual distraction. Cards show the estimate value instead of a playful label",[12,3110,3111],{},"Choose minimalistic if you find colorful visuals distracting during focused estimation sessions.",[21,3113,3115],{"id":3114},"sound-volume","Sound Volume",[12,3117,3118],{},"Controls the volume of audio notifications, from 0% to 100%. The default is 50%. Scrumpy plays sounds for key events:",[26,3120,3121,3126,3131,3137,3143],{},[29,3122,3123,3125],{},[16,3124,2303],{},": When another participant casts a vote",[29,3127,3128,3130],{},[16,3129,313],{},": When the moderator starts a voting session",[29,3132,3133,3136],{},[16,3134,3135],{},"End",": When the voting session reveals results",[29,3138,3139,3142],{},[16,3140,3141],{},"Reminder",": When the moderator sends a reminder to unvoted participants",[29,3144,3145,3148],{},[16,3146,3147],{},"Message",": When a new chat message arrives",[12,3150,3151],{},"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.",[12,3153,3154],{},"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.",[21,3156,3158],{"id":3157},"resetting","Resetting",[12,3160,3161],{},"You can reset all personal settings to their defaults from the Personal settings panel. A confirmation appears first, and the reset cannot be undone.",{"title":153,"searchDepth":154,"depth":154,"links":3163},[3164,3165,3166,3167],{"id":3034,"depth":154,"text":3035},{"id":3088,"depth":154,"text":3089},{"id":3114,"depth":154,"text":3115},{"id":3157,"depth":154,"text":3158},"Personal settings in Scrumpy: chart type, card visuals, sound volume and how to reset your own preferences.","\u002Fog\u002Fguide-personal-settings.jpg",[3171,3172,3173],"scrumpy settings","chart type","jira estimation app",{},6,"\u002Fgetting-started\u002Fpersonal-settings",{"title":3023,"description":3168},{"loc":3176,"lastmod":159},"personal-settings","guide\u002Fen\u002Fpersonal-settings","guide\u002Fpersonal-settings","0b68M8kSjL4pUwUkWJv1uat3Xlb4Q695DsSN0vajubo",{"id":3184,"title":3185,"body":3186,"dateModified":802,"datePublished":160,"description":3456,"extension":162,"heading":3322,"image":3457,"imageAlt":3322,"keywords":3458,"locale":168,"meta":3462,"navigation":170,"order":3463,"path":3464,"section":173,"seo":3465,"sitemap":3466,"slug":3467,"stem":3468,"translationKey":3469,"__hash__":3470},"guide\u002Fguide\u002Fen\u002Faudit-logs-and-dashboards.md","Audit Logs and Dashboard | Scrumpy Planning Poker",{"type":9,"value":3187,"toc":3447},[3188,3191,3194,3198,3203,3206,3226,3229,3264,3271,3274,3281,3285,3290,3304,3313,3317,3320,3324,3328,3337,3340,3398,3408,3412,3417,3434,3437,3441,3444],[12,3189,3190],{},"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.",[12,3192,3193],{},"The audit tabs and the Space settings Dashboard live in space settings. You need permission to manage the space in Jira to open them, and that permission is checked again when the data loads. Being able to open a work item panel is not enough. The lighter Dashboard on the Space Estimations page is available to anyone who can open that page, and it only counts work items you can open in Jira.",[21,3195,3197],{"id":3196},"voting-audit","Voting Audit",[12,3199,930,3200,3202],{},[16,3201,3197],{}," tab shows a chronological log of all significant events that occurred in voting sessions for the space.",[12,3204,3205],{},"Events recorded include:",[26,3207,3208,3211,3214,3217,3220,3223],{},[29,3209,3210],{},"Session created, voted, paused, resumed, completed, cancelled",[29,3212,3213],{},"Estimate set or modified by the moderator",[29,3215,3216],{},"Required voters updated",[29,3218,3219],{},"Async complete-until deadline set or cleared",[29,3221,3222],{},"Estimate accepted and written to Jira",[29,3224,3225],{},"Reminders sent to unvoted participants",[12,3227,3228],{},"Each event shows:",[26,3230,3231,3237,3242,3247,3253,3259],{},[29,3232,3233,3236],{},[16,3234,3235],{},"Occurred",": Timestamp of the event",[29,3238,3239,3241],{},[16,3240,429],{},": The icon of the work item's type, including newer and custom types",[29,3243,3244,3246],{},[16,3245,433],{},": Clickable issue key that opens the work item in a modal",[29,3248,3249,3252],{},[16,3250,3251],{},"Perspective",": Which estimation perspective was used",[29,3254,3255,3258],{},[16,3256,3257],{},"Actor",": The user who triggered the event",[29,3260,3261,3263],{},[16,3262,631],{},": Human-readable summary of what happened",[12,3265,3266,3267,3270],{},"Enter a search term and click ",[16,3268,3269],{},"Search"," to filter by work item key, perspective, or description. Choose 15, 30, 45, or 60 rows per page, and use the pagination controls to browse large histories.",[12,3272,3273],{},"The Voting Audit lists only work items you can open in Jira. Events for issues hidden from you by issue-level security are left out, and they are not counted in the page totals.",[12,3275,3276,3277,3280],{},"Only the space owner can delete the voting audit log. If you can open space settings but are not the space owner, the ",[16,3278,3279],{},"Delete audit log"," button is replaced by a note explaining this. When you are the space owner, a confirmation dialog appears first, and the deletion cannot be undone.",[21,3282,3284],{"id":3283},"configuration-audit","Configuration Audit",[12,3286,930,3287,3289],{},[16,3288,3284],{}," tab tracks every change made to space permissions and perspective settings. Each entry records:",[26,3291,3292,3295,3298,3301],{},[29,3293,3294],{},"Who made the change",[29,3296,3297],{},"What was changed (with a human-readable description)",[29,3299,3300],{},"When the change was made",[29,3302,3303],{},"Which perspective was affected (if applicable)",[12,3305,3306,3307,3309,3310,3312],{},"Like the voting audit, this table is searchable with a ",[16,3308,3269],{}," button and paginated with the same page-size selector. Only the space owner can clear it with the ",[16,3311,3279],{}," action. Other users see a note in place of the button.",[21,3314,3316],{"id":3315},"dashboards","Dashboards",[12,3318,3319],{},"Scrumpy has two dashboards with different purposes.",[61,3321],{"alt":3322,"caption":3322,"stem":3323},"Audit Logs and Dashboard","guide-dashboard",[233,3325,3327],{"id":3326},"space-settings-dashboard","Space Settings Dashboard",[12,3329,930,3330,3332,3333,3336],{},[16,3331,355],{}," tab in Space settings provides the full analytics view. Use the range selector to choose 1, 2, 4, or 8 weeks, or ",[16,3334,3335],{},"All time",". Your choice is remembered in this browser tab. All time is still limited to the 90-day retention window, and the charts refresh when you open the tab again.",[12,3338,3339],{},"Charts shown:",[26,3341,3342,3348,3353,3359,3364,3370,3376,3381,3387,3392],{},[29,3343,3344,3347],{},[16,3345,3346],{},"Total votes"," per perspective (donut)",[29,3349,3350,3347],{},[16,3351,3352],{},"Total estimates",[29,3354,3355,3358],{},[16,3356,3357],{},"Average certainty"," per perspective (bar)",[29,3360,3361,3358],{},[16,3362,3363],{},"Average variation",[29,3365,3366,3369],{},[16,3367,3368],{},"Average duration"," per perspective (stacked active and paused time, shown in seconds or minutes)",[29,3371,3372,3375],{},[16,3373,3374],{},"Total estimates per day"," (line)",[29,3377,3378,3375],{},[16,3379,3380],{},"Average voters per day",[29,3382,3383,3386],{},[16,3384,3385],{},"Average certainty per day"," (bar)",[29,3388,3389,3386],{},[16,3390,3391],{},"Average variation per day",[29,3393,3394,3397],{},[16,3395,3396],{},"Total duration in minutes per day"," (stacked)",[12,3399,3400,3401,3404,3405,3407],{},"Only the space owner can delete all accepted session records with ",[16,3402,3403],{},"Delete estimation log"," at the bottom of the tab. A confirmation appears first, and the deletion cannot be undone. If you can open space settings but are not the space owner, the ",[16,3406,3403],{}," button is replaced by a note explaining this.",[233,3409,3411],{"id":3410},"estimations-page-dashboard","Estimations Page Dashboard",[12,3413,930,3414,3416],{},[16,3415,355],{}," tab on the Space Estimations page is a lighter, live overview with three charts and no time filter or delete action:",[26,3418,3419,3424,3429],{},[29,3420,3421],{},[16,3422,3423],{},"Active Sessions by Perspective",[29,3425,3426],{},[16,3427,3428],{},"Unique Voters by Perspective",[29,3430,3431],{},[16,3432,3433],{},"Sessions by State per Perspective",[12,3435,3436],{},"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 row appears once the first person votes. Sessions you already viewed on another tab appear right away, and the charts update as the rest of the space's sessions load in the background.",[21,3438,3440],{"id":3439},"data-retention","Data Retention",[12,3442,3443],{},"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 and their reactions are kept for 72 hours. The space owner can also delete all audit entries and the estimation log from their respective tabs; those deletions cannot be undone.",[12,3445,3446],{},"Space settings are kept until you change them. This includes the voting password, the voter and moderator lists, and every perspective setting. The 90-day retention window does not remove them, so a protected space stays protected and your team keeps its roles.",{"title":153,"searchDepth":154,"depth":154,"links":3448},[3449,3450,3451,3455],{"id":3196,"depth":154,"text":3197},{"id":3283,"depth":154,"text":3284},{"id":3315,"depth":154,"text":3316,"children":3452},[3453,3454],{"id":3326,"depth":784,"text":3327},{"id":3410,"depth":784,"text":3411},{"id":3439,"depth":154,"text":3440},"Voting and configuration audit logs plus dashboards that show estimation trends, participation and team activity in Jira.","\u002Fog\u002Fguide-audit-logs-and-dashboards.jpg",[3459,3460,3461],"voting audit","jira dashboard","estimation analytics",{},7,"\u002Fgetting-started\u002Faudit-logs-and-dashboards",{"title":3185,"description":3456},{"loc":3464,"lastmod":802},"audit-logs-and-dashboards","guide\u002Fen\u002Faudit-logs-and-dashboards","guide\u002Faudit-logs-and-dashboards","rxB8Cd9UAP9a-ZJRjsVKCT4CVQ-iION2XuUAfl38z14",{"id":3472,"title":3473,"body":3474,"dateModified":802,"datePublished":160,"description":4837,"extension":162,"heading":4838,"image":4839,"imageAlt":4838,"keywords":4840,"locale":168,"meta":4845,"navigation":170,"order":4846,"path":4847,"section":173,"seo":4848,"sitemap":4849,"slug":4850,"stem":4851,"translationKey":4852,"__hash__":4853},"guide\u002Fguide\u002Fen\u002Fplanning-sessions.md","Planning Sessions | Scrumpy Planning Poker",{"type":9,"value":3475,"toc":4809},[3476,3479,3485,3489,3495,3500,3567,3577,3580,3582,3587,3609,3625,3637,3650,3654,3657,3661,3687,3691,3723,3738,3741,3744,3758,3761,3767,3771,3797,3800,3804,3820,3832,3836,3846,3852,3855,3859,3865,3871,3877,3897,3912,3915,3918,3922,3931,4021,4048,4051,4054,4058,4073,4076,4099,4102,4108,4124,4128,4131,4153,4156,4160,4163,4182,4187,4206,4209,4212,4215,4234,4248,4251,4254,4314,4322,4325,4328,4342,4355,4362,4365,4370,4373,4390,4396,4403,4406,4409,4412,4437,4440,4443,4446,4457,4460,4463,4473,4493,4511,4517,4528,4546,4549,4568,4571,4574,4577,4589,4595,4599,4614,4629,4642,4646,4661,4665,4668,4702,4706,4712,4715,4723,4730,4750,4759,4762,4766,4773,4776,4782],[12,3477,3478],{},"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.",[12,3480,3481,3482,3484],{},"Planning sessions live on the Space Estimations page. If a space administrator hides that page in space settings, the ",[16,3483,254],{}," action on work items is hidden with it.",[21,3486,3488],{"id":3487},"creating-a-planning-session","Creating a Planning Session",[12,3490,3491,3492,3494],{},"From the ",[16,3493,340],{}," tab on the Space Estimations page:",[61,3496],{"alt":3497,"caption":3498,"stem":3499},"The Create planning session dialog with the title, description, and schedule","Creating a planning session","guide-planning-create",[66,3501,3502,3507,3510,3527,3552],{},[29,3503,3504,3505,569],{},"Click ",[16,3506,568],{},[29,3508,3509],{},"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.",[29,3511,3512,3513,3516,3517,3519,3520,3523,3524,3526],{},"Optionally add a description and a schedule. The ",[16,3514,3515],{},"Show timer"," checkbox is checked by default. Clear it to hide the schedule and create the planning session without a timer. While it is checked, choose the ",[16,3518,2216],{}," tab to set a start date and time on the left and a duration of 15, 30, 45, 60, 90, or 120 minutes on the right, all on one line, with the end time shown below the duration. The dialog shows when the session ends, and the end moves to the next day when the duration crosses midnight. Choose the ",[16,3521,3522],{},"Long lasting"," tab to set a start and an end date and time yourself; the start sits on the left and the end on the right of one line. You can pick a date and type any time; the time list suggests every 15 minutes, and a typed time is always kept. Past dates and times are allowed. The dialog opens with the next half hour and 30 minutes already filled in. Clearing a start date puts today back, clearing an end date puts the day after the start back, and clearing a time puts the next half hour back, so the fields never stay empty. The end must be later than the start. ",[16,3525,568],{}," also stays disabled while the title is empty or contains only spaces.",[29,3528,3529,3530,3533,3534,3537,3538,2537,3541,3544,3545,3548,3549,3551],{},"Optionally add a ",[16,3531,3532],{},"Video\u002Fscreen share"," link, such as ",[604,3535,3536],{},"https:\u002F\u002Fmeet.example.com\u002Fsprint-42",". The link must be a full address that starts with ",[604,3539,3540],{},"http:\u002F\u002F",[604,3542,3543],{},"https:\u002F\u002F",". While the field holds a valid link, a video icon appears inside the field; click it to open the link in a new tab. An incomplete address such as ",[604,3546,3547],{},"meet.example.com\u002Fsprint-42"," is marked in error and ",[16,3550,568],{}," stays disabled until you fix it or clear the field.",[29,3553,3504,3554,3556,3557,430,3560,3563,3564,3566],{},[16,3555,568],{},". The dialog closes right away and the new planning session appears in the list immediately. If it cannot be saved, it is removed again.\nOnly 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. While a planning session is open, its ",[16,3558,3559],{},"Edit",[16,3561,3562],{},"Delete"," actions sit in the row above the tabs, just before ",[16,3565,568],{},". They are not shown while there is no planning session to act on. The planning session tab you last opened is remembered for the current browser tab, so a reload returns you to it. If that planning session no longer exists, the first planning session opens instead.",[12,3568,3569,3570,334,3572,917,3574,3576],{},"The same planning sessions also appear as tabs on the ",[16,3571,343],{},[16,3573,346],{},[16,3575,349],{}," tabs. The planning session you select is shared between those tabs, so switching tab keeps the same session open. See the Sprint standups and Sprint retrospectives guides.",[12,3578,3579],{},"Planning sessions are kept for three months (90 days) after their last change and are removed automatically after that.",[21,3581,1985],{"id":1984},[12,3583,3504,3584,3586],{},[16,3585,3559],{}," on a planning session to change its title, description, video link, 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 and a message tells you that the planning session could not be saved.",[12,3588,3589,3590,3593,3594,3596,3597,3599,3600,3602,3603,3605,3606,3608],{},"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 ",[16,3591,3592],{},"Apply"," does not save the change. The schedule has the same two tabs as the create dialog: ",[16,3595,2216],{}," takes a start and a duration, and ",[16,3598,3522],{}," takes a start and an end. A session saved with one of the offered durations opens on the ",[16,3601,2216],{}," tab with that duration selected; any other length opens on the ",[16,3604,3522],{}," tab. The ",[16,3607,3515],{}," checkbox controls the schedule: clear it to remove the timer, and a session without a timer opens with it cleared. While it is checked, clearing a start date puts today back, clearing an end date puts the day after the start back, and clearing a time puts the next half hour back, so the fields never stay empty. The end must be later than the start. The time list suggests every 15 minutes, and you can type any time.",[12,3610,930,3611,3613,3614,2537,3616,3618,3619,3621,3622,3624],{},[16,3612,3532],{}," link is optional and has the same rules as on the create dialog: it must be a full ",[604,3615,3540],{},[604,3617,3543],{}," address, and a value that is not one is marked in error and keeps ",[16,3620,3592],{}," disabled. Clear the field to remove the link. When a planning session has a link, every participant header shows a small red video icon just before the role badge: on the planning session side panel, in ",[16,3623,343],{},", in alternative voting, and in the work item voting panel. Click the icon to join the video or screen-sharing session in a new tab. The icon appears as soon as the link is saved, without a reload, and disappears when the link is cleared.",[12,3626,3627,3628,3630,3631,2537,3634,3636],{},"A moderator can also change the description in place. In the ",[16,3629,340],{}," tab, click the description above the planning table, type the new text, and click away. There is no ",[16,3632,3633],{},"OK",[16,3635,503],{}," button: the text saves when the field loses focus, appears for everyone right away, and returns to the saved text if the save fails. A session with no description shows a placeholder you can click to add one.",[12,3638,3639,3640,3642,3643,3645,3646,569],{},"To remove a planning session, use ",[16,3641,3562],{}," in the row above the tabs, beside ",[16,3644,568],{},". It removes the planning session and all of its items permanently after a confirmation. It also removes its planning-session chat, the work item chat messages and reactions for its items, its ranking records, capacity planning data, standup data, retrospective data, and any linked voting sessions. See ",[2806,3647,3649],{"href":3648},"#deleting-a-planning-session","Deleting a Planning Session",[21,3651,3653],{"id":3652},"adding-work-items","Adding Work Items",[12,3655,3656],{},"You can add work items to a planning session in two ways.",[233,3658,3660],{"id":3659},"from-the-work-item-view","From the Work Item View",[12,3662,3663,3664,3666,3667,3669,3670,3673,3674,3677,3678,3680,3681,3683,3684,3686],{},"Open a Jira work item, open the ",[16,3665,304],{}," panel, and click ",[16,3668,254],{},". You can also open the same dialog from the work item's ",[16,3671,3672],{},"more actions"," (",[16,3675,3676],{},"...",") menu by choosing ",[16,3679,254],{},". Adding a work item to a planning session is a moderator action: voters, guests, and anyone else see a note that only moderators can add work items, instead of the picker. The dialog preselects the planning session you used last on this space; when the space has no planning sessions, ",[16,3682,568],{}," is selected instead. Choose another existing session, or choose ",[16,3685,568],{}," 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. Each planning session you open loads its work items. Switching to another session loads that session once, and returning to one you already opened shows its work items right away.",[233,3688,3690],{"id":3689},"add-from-jira-filter","Add from Jira Filter",[12,3692,3504,3693,3696,3697,3699,3700,3702,3703,3705,3706,3709,3710,3713,3714,3716,3717,3719,3720,3722],{},[16,3694,3695],{},"Add from filter"," to import work items from a saved Jira filter, a sprint, a capacity planning session, or a retrospective. The picker starts with a ",[16,3698,343],{}," group that lists the planning sessions whose capacity plan has at least one planned work item. Select one to preview every planned work item across that capacity session's sprints. A ",[16,3701,349],{}," group follows it and lists the planning sessions whose retrospective action items are linked to Jira work items. Select one to preview the linked work items. The ",[16,3704,349],{}," group is hidden when no action item is linked to a work item. If the space has a Scrum board, the picker then shows an ",[16,3707,3708],{},"Active sprints"," group that lists the active and future sprints, and a ",[16,3711,3712],{},"Backlog"," group with one entry per Scrum board. The ",[16,3715,3708],{}," group appears only when the space has at least one active or future sprint. The ",[16,3718,3712],{}," group appears whenever the space has a Scrum board, even when no sprint is active or planned; Kanban spaces show neither group. Select a sprint to preview its work items, or select a Scrum board under ",[16,3721,3712],{}," to preview that board's work items that are not in any sprint. Only work items from this space are listed.",[12,3724,3725,3726,3729,3730,3733,3734,3737],{},"Below the backlog, the picker lists the space's Kanban boards under ",[16,3727,3728],{},"Boards","; pick one to preview the work items on that board. Scrum boards are not listed there, because the sprint and backlog entries already cover them. Then come favourited filters under ",[16,3731,3732],{},"Favorite",", your own filters under ",[16,3735,3736],{},"My filters",", and shared filters under their owner's name; favourited filters show a star. Type in the picker to search Jira by any part of a filter name. The same text also narrows the sprint, backlog, and board lists and every filter group. Scrumpy asks Jira for the first 100 shared filters that match. When more shared filters match than that, the dialog says it shows the first ones, and typing more of the name narrows the list. To start over, clear the picker: the chosen filter is dropped, the search box empties, and the first 100 shared filters return. Select a filter to preview its work items, tick the ones you want, and add them. A work item that already belongs to a planning session is marked with that session's title and cannot be added again, even when that session is not open in another tab. 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; the preview lists only this space's work items and says so below the table. You can also add only work items you can open in Jira: a work item hidden from you stays out of the session, even if you know its key.",[12,3739,3740],{},"Only work items you can open in Jira can be added. If a work item is hidden from you by Jira issue-level security, Scrumpy rejects the add, and that work item is omitted from the planning table for you.",[12,3742,3743],{},"In the preview you can:",[26,3745,3746,3749,3752,3755],{},[29,3747,3748],{},"Tick individual work items, or use the header checkbox to select all selectable ones on the page you are looking at.",[29,3750,3751],{},"Page through long results below the table. The preview shows 100 work items per page, and your ticks stay when you change page.",[29,3753,3754],{},"Reorder rows by dragging them. The ticked items are added in the order the preview shows, across every page.",[29,3756,3757],{},"See Type, Work item, Status, and Summary columns. The Type column shows the icon of the work item's type, including newer and custom types. 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.",[12,3759,3760],{},"The preview loads at most 500 work items. When a filter matches more, the dialog says it shows the first 500.",[12,3762,3763,3766],{},[16,3764,3765],{},"Add"," stays disabled until you select at least one work item.",[21,3768,3770],{"id":3769},"managing-items","Managing Items",[26,3772,3773,3779,3785],{},[29,3774,3775,3778],{},[16,3776,3777],{},"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.",[29,3780,3781,3784],{},[16,3782,3783],{},"Select",": Tick the checkboxes to select items for bulk actions.",[29,3786,3787,3790,3791,3793,3794,3796],{},[16,3788,3789],{},"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. When no work item is selected, the right panel shows a planning session side panel with a ",[16,3792,2040],{}," tab for the no-selection message and a ",[16,3795,1877],{}," tab for the planning session chat.",[12,3798,3799],{},"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.",[233,3801,3803],{"id":3802},"edit-mode","Edit mode",[12,3805,930,3806,3808,3809,3812,3813,3816,3817,3819],{},[16,3807,3803],{}," dropdown to the right of the session description chooses how voting is driven: ",[16,3810,3811],{},"Single voting"," (the default) or ",[16,3814,3815],{},"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 ",[16,3818,2366],{},", 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.",[12,3821,3822,3823,3825,3826,3828,3829,569],{},"To the right of the ",[16,3824,3803],{}," dropdown, the app switcher button opens ",[16,3827,343],{}," on the same planning session tab. Its tooltip says ",[16,3830,3831],{},"Switch to capacity planning",[233,3833,3835],{"id":3834},"visible-perspectives","Visible perspectives",[12,3837,3838,3839,3841,3842,3845],{},"The perspectives dropdown sits just before the ",[16,3840,3803],{}," dropdown. It chooses which perspectives the planning table shows, as a column and as a row in bulk voting, and which perspective tabs appear in the voting panel on the right. It appears only when the space has more than one perspective. When the dropdown is empty it shows ",[16,3843,3844],{},"All perspectives",", which is also the default for every planning session.",[12,3847,3848,3849,3851],{},"A moderator changes the list for everyone, and it updates without a reload. A voter can narrow the list for themselves. That change unchecks ",[16,3850,2366],{}," and stays in the current browser tab. Checking the lock again returns the moderator's list. A guest always follows the moderator's list.",[12,3853,3854],{},"Only the perspectives in the list are offered for the bulk Start, Pause, Resume, Complete, Restart, Cancel, and Accept actions. If the moderator hides the perspective that is currently open in the right panel, the panel returns to the highlighted work item. A perspective you add later appears automatically until someone narrows the list.",[233,3856,3858],{"id":3857},"who-is-highlighted","Who is highlighted",[12,3860,3861,3862,3864],{},"Moderators pick the highlighted work item for everyone, and the selected row shows a yellow ",[16,3863,1515],{}," with the tooltip \"Work item currently selected by the moderator\".",[12,3866,3867,3868,3870],{},"In bulk mode a moderator can instead select a 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 ",[16,3869,1515],{}," in the first column of that perspective row, with the tooltip \"Perspective currently selected by the moderator\".",[12,3872,3873,3874,3876],{},"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 ",[16,3875,1515],{}," badge marks it, even when it matches the tab they are on. The badge stays visible when you clear the lock, so you can always see where the moderator is. It 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.",[12,3878,930,3879,3881,3882,3884,3885,3887,3888,3890,3891,3893,3894,3896],{},[16,3880,1515],{}," is also your pointer to the moderator's view. While you follow the moderator, your highlighted row and the ",[16,3883,1515],{}," row are the same. When you pick a row yourself, your highlight moves to that row and the ",[16,3886,1515],{}," stays on the moderator's row, so you can see how far you have drifted. The same holds for the inline panel: the ",[16,3889,1515],{}," stays on the moderator's tab after you open another one. Following the moderator also means that the moderator switches tabs for you: while ",[16,3892,2366],{}," is on, every work item and tab the moderator opens opens for you too. Detaching is one click: pick another row, tab, or edit mode, or clear ",[16,3895,2366],{}," yourself.",[12,3898,3899,3900,3902,3903,334,3905,334,3907,917,3909,3911],{},"By default, other participants follow the moderator's work item selection, edit mode, and alternative-voting tab. A ",[16,3901,2366],{}," checkbox (on by default) controls this. It applies to the planning tab you are on: ",[16,3904,340],{},[16,3906,343],{},[16,3908,346],{},[16,3910,349],{},". It also controls the space page tab: when the moderator switches between those tabs, a locked participant viewing the same planning session moves to the same tab and stays locked. When you switch between those tabs yourself, the checkbox clears, so you start detached on the new tab. Switching to Getting started, Tutorials, or Dashboard and back does not clear it.",[12,3913,3914],{},"If you pick a row, switch the edit mode, or open another alternative-voting tab yourself, the lock turns off. The lock is remembered in this browser tab while you stay on the tab. Your local choices stay with the tab where you made them. Clearing the lock keeps the right panel on the tab you were following; it does not jump back to a tab you opened earlier. Your local choices survive a reload but are not shared with anyone else and do not change what the moderator sees.",[12,3916,3917],{},"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.",[233,3919,3921],{"id":3920},"bulk-actions","Bulk actions",[12,3923,3924,3925,3927,3928,3930],{},"Below the table, a ",[16,3926,3251],{}," select (disabled until you tick at least one work item) chooses which perspective the session actions apply to, followed by icon-only actions. The open list starts with a ",[16,3929,3251],{}," heading that you cannot choose. 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.",[614,3932,3933,3943],{},[617,3934,3935],{},[620,3936,3937,3940],{},[623,3938,3939],{},"Action",[623,3941,3942],{},"What it does",[633,3944,3945,3954,3963,3972,3984,3993,4002,4011],{},[620,3946,3947,3951],{},[638,3948,3949],{},[16,3950,313],{},[638,3952,3953],{},"Opens voting sessions for the ticked items in the chosen perspective",[620,3955,3956,3960],{},[638,3957,3958],{},[16,3959,479],{},[638,3961,3962],{},"Pauses their started sessions. Sessions that are already paused are skipped, and perspectives with asynchronous voting are skipped because their sessions cannot be paused",[620,3964,3965,3969],{},[638,3966,3967],{},[16,3968,485],{},[638,3970,3971],{},"Resumes their paused sessions. Perspectives with asynchronous voting are skipped because their sessions cannot be resumed",[620,3973,3974,3978],{},[638,3975,3976],{},[16,3977,491],{},[638,3979,3980,3981,3983],{},"Completes their started sessions. A session with no votes (no real estimate) is cancelled instead, matching the voting panel's ",[16,3982,491],{}," button. Votes made only with the extra emoji cards count as no votes",[620,3985,3986,3990],{},[638,3987,3988],{},[16,3989,497],{},[638,3991,3992],{},"Restarts their completed sessions in place. The new round starts right away with the configured required voters, and the completed result and its votes are discarded. The work item keeps its place in the perspective's rankings",[620,3994,3995,3999],{},[638,3996,3997],{},[16,3998,503],{},[638,4000,4001],{},"Cancels their voting sessions, including completed ones",[620,4003,4004,4008],{},[638,4005,4006],{},[16,4007,509],{},[638,4009,4010],{},"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",[620,4012,4013,4018],{},[638,4014,4015],{},[16,4016,4017],{},"Remove",[638,4019,4020],{},"Removes the ticked items from the planning session",[12,4022,4023,4024,4026,4027,4029,4030,4032,4033,4035,4036,4038,4039,4041,4042,4044,4045,4047],{},"An action is disabled when no ticked work item applies: ",[16,4025,313],{}," when every session has already started, ",[16,4028,479],{}," when there is no active session or the perspective uses asynchronous voting, ",[16,4031,485],{}," when there is no paused session or the perspective uses asynchronous voting, ",[16,4034,491],{}," when there is no started session, ",[16,4037,497],{}," when there is no completed session, ",[16,4040,503],{}," when no ticked item has a session, ",[16,4043,509],{}," when there is no completed session, and ",[16,4046,4017],{}," until something is ticked. Removing the highlighted item clears the highlight.",[12,4049,4050],{},"Each action takes effect in the table immediately. The rows are added, paused, resumed, completed, restarted, 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. The inline voting panel on the right changes in the same moment, and a vote or session action made in the panel updates the table row at the same moment too. You never need to wait for a refresh to see the other side catch up. If the change cannot be saved, both the table and the panel return to the previous state.",[12,4052,4053],{},"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.",[21,4055,4057],{"id":4056},"bulk-voting","Bulk Voting",[12,4059,4060,4061,4063,4064,4066,4067,4069,4070,4072],{},"Anyone can switch the ",[16,4062,3803],{}," from ",[16,4065,3811],{}," to ",[16,4068,3815],{},". 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 ",[16,4071,3803],{}," dropdown, the buttons, the progress bar, and the estimation panel all stay in place.",[12,4074,4075],{},"A perspective cell shows a voting control only when that work item has a started session in that perspective:",[26,4077,4078,4084,4087],{},[29,4079,4080,4081,4083],{},"A clearable dropdown of the deck's cards (for example \"2 sp\" or \"XXL\"), with the extra cards grouped under an ",[16,4082,1260],{}," heading, preselected with your current vote.",[29,4085,4086],{},"A number field bounded by the perspective's minimum and maximum for free scale perspectives. The field always shows an \"sp\" suffix after the number. When the perspective converts story points to a duration, it also shows a short duration such as \"1d 4h\" beside the suffix. Clearing the field removes the vote, restores the work item's original estimate as the field value, and marks the field as needing a vote. The clear control is always visible and is disabled until the field has a value.",[29,4088,4089,4090,4092,4093,4095,4096,4098],{},"A parametric result in a read-only numeric field with an \"sp\" suffix, a compact withdraw control, and one compact edit vote control inside the suffix area. When you have not voted yet, the field shows the work item's current estimate when it is numeric and is marked as needing a vote. Opening the edit control calculates the current result and shows it in the field straight away, using the perspective formula and the parameter values in the popup. The popup has one compact number field per parameter, labelled with the parameter name and bounded by its minimum and maximum, and a centered primary ",[16,4091,2303],{}," button below the parameters. Changing a parameter updates the value in the field immediately. The edit control is hidden while the popup is open and comes back when it closes. ",[16,4094,2303],{}," closes the popup and casts the result. Clicking outside the popup closes it without saving and restores the previous vote, or returns to the empty error field when there was no vote. When a vote already exists and you have not changed a parameter, ",[16,4097,2303],{}," stays disabled. Press the withdraw control to remove the current parametric vote immediately. The field shows the work item's original estimate again and is marked as needing a vote, and the withdraw control and the \"sp\" suffix stay visible while the withdraw control is disabled. The converted duration and the wider field appear only when the estimation target writes a time value: a time board or a Time field. The numeric fields have a fixed width for each combination of story points and duration, so the columns line up and a field does not change size while you type. A numeric board or a story points field shows story points only, and the perspective settings explain that the duration is not written. Scrumpy remembers the last parameter values you used for the current voting session and puts them back when you reopen the editor. It also opens on the parameter positions recorded with your vote, even when you cast it in the voting panel, so both places always show the same positions. A new voting session starts again from each slider's midpoint. The positions you have not voted with yet are kept only in your browser for the open page, not saved with the vote.",[12,4100,4101],{},"When the session is active and not paused, a compact pause control sits beside the voting control and uses the same height. Pressing it pauses that work item's voting session and hides the control immediately. If the pause fails, the control returns. The pause control is not shown for a paused session or for asynchronous voting.",[12,4103,4104,4105,4107],{},"Changing a control casts your vote for that work item and perspective. The value appears right away and stays in place while it is saved, including when closed voting is on. 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. Parametric is different: opening the editor shows the calculated result in the cell, editing the fields only updates that preview, and the ",[16,4106,2303],{}," button in the popup casts the result. When a session completes or is cancelled, its voting control disappears and the cell returns to its usual state or estimate.",[12,4109,4110,4111,4113,4114,4116,4117,4119,4120,4123],{},"Until you vote in a cell, the control shows the work item's current estimate as a placeholder, or ",[16,4112,2303],{}," when there is none, and the control is marked as needing a vote. Choosing a value clears that hint. Free-scale and parametric cells show the original numeric estimate in the field until you vote. In a parametric cell, opening the editor replaces that estimate with the calculated result, even before your first vote, and closing without pressing ",[16,4115,2303],{}," restores the previous vote or the original estimate and its red error state. When the current estimate is stored as a time value (a time board or a Time field), the bulk editor converts it back to story points with the ",[16,4118,1294],{}," factor, so a 20-hour estimate appears as ",[16,4121,4122],{},"2.5"," in a field that edits story points; the parametric editor also keeps the 20-hour duration beside the value.",[233,4125,4127],{"id":4126},"perspective-rows-and-ranking-columns","Perspective rows and ranking columns",[12,4129,4130],{},"In bulk mode the table also lists one selectable row per perspective below the work items. Free scale perspectives show the Affinity, Dot, and Bucket tabs: the Bucket tab lists the work items from the smallest to the largest estimate with a gap row between different estimates, because there are no cards to drop work items under. Parametric perspectives show the Affinity, Dot, and Bucket tabs too: their Bucket tab lists the same estimates, but a vote is edited through its sliders instead of a field. 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.",[12,4132,4133,4134,4136,4137,4139,4140,430,4142,4144,4145,4148,4149,4152],{},"While a perspective has rankings, its row shows a regular ",[16,4135,1487],{}," badge and a regular ",[16,4138,1490],{}," badge for everyone, one for each ranking the perspective has. A perspective with no rankings shows no badges. Rankings are cleared from the ",[16,4141,1487],{},[16,4143,1490],{}," panels: the affinity ",[16,4146,4147],{},"Clear rankings"," delete icon 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 ",[16,4150,4151],{},"No ranking",". The rankings disappear right away; if the clear cannot be saved, they come back.",[12,4154,4155],{},"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.",[21,4157,4159],{"id":4158},"alternative-voting","Alternative Voting",[12,4161,4162],{},"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.",[12,4164,4165,4166,2537,4168,4170,4171,4173,4174,334,4176,4178,4179,4181],{},"The perspective you last opened in alternative voting and the ",[16,4167,2303],{},[16,4169,1462],{}," sub-tab are remembered for the current browser tab. While ",[16,4172,2366],{}," is on, the outer tab (",[16,4175,1487],{},[16,4177,1490],{},", or ",[16,4180,1493],{},") follows the moderator's current tab. The moderator's tab is saved with the planning session and appears for everyone right away.",[12,4183,2370,4184,4186],{},[16,4185,1515],{}," 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.",[12,4188,4189,4190,334,4192,917,4194,4196,4197,4199,4200,4202,4203,4205],{},"The panel has three tabs: ",[16,4191,1487],{},[16,4193,1490],{},[16,4195,1493],{},". Each tab shows the perspective title in bold, its description, and the settings gear link above its table. All three tabs list the work items that apply to the perspective and have an active, paused, or completed voting session. A work item leaves the panels when its session is cancelled or accepted. Every table has a lock column after the ",[16,4198,433],{}," column. Its header shows the locked padlock. A fully locked panel shows the lock icon on every work item. A single work item that cannot be moved, such as a completed session in a bucket table, shows the locked padlock icon. To the right of the ",[16,4201,1493],{}," tab, the panel shows a ",[16,4204,1877],{}," tab, then the same role badge and sound bell as the voting panel: the badge links to the Permissions settings, the bell toggles sound notifications, and the Chat tab shows the planning session chat.",[12,4207,4208],{},"In every tab, hovering a work item key shows its Jira summary, the same tooltip the planning table uses. The summaries come from the ones the planning table already loaded, so switching tabs does not read Jira again. If a summary is not available, the key shows without a tooltip.",[12,4210,4211],{},"Cancelling or accepting a work item's voting session removes it from both rankings for that perspective and from the Affinity, Dot, and Bucket panels. Starting a new session for the item adds it back unranked, at the end of the affinity order and without a dot.",[233,4213,1487],{"id":4214},"affinity",[12,4216,4217,4218,430,4220,4222,4223,4225,4226,4228,4229,4231,4232,1191],{},"Affinity ranks the work items. It has two sub-tabs, ",[16,4219,2303],{},[16,4221,1462],{},": ",[16,4224,2303],{}," holds the table and all the controls, and ",[16,4227,1462],{}," shows a bar chart of the ranking. Every participant sees ",[16,4230,1462],{},", whether or not ",[16,4233,999],{},[12,4235,4236,4237,4240,4241,4244,4245,4247],{},"To the right of the perspective title, a moderator sets the ranking algorithm: ",[16,4238,4239],{},"Mean rank"," (averages the participants' rankings) or ",[16,4242,4243],{},"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. If the enforced ranking is ",[16,4246,1487],{}," and the bucket panel has a vote or a completed session, the affinity table is locked: you cannot rerank, withdraw, or change the algorithm, and the lock column shows the lock icon on every work item. The other ranking stays editable.",[12,4249,4250],{},"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 as soon as you move a row, without waiting for the save. The affinity rank column in the planning table follows your move at once, so the ranks there never lag behind the table you are dragging.",[12,4252,4253],{},"The table shows these columns:",[614,4255,4256,4265],{},[617,4257,4258],{},[620,4259,4260,4263],{},[623,4261,4262],{},"Column",[623,4264,1134],{},[633,4266,4267,4276,4285,4295,4304],{},[620,4268,4269,4273],{},[638,4270,4271],{},[16,4272,429],{},[638,4274,4275],{},"The icon of the work item's type, including newer and custom types",[620,4277,4278,4282],{},[638,4279,4280],{},[16,4281,433],{},[638,4283,4284],{},"Issue key",[620,4286,4287,4292],{},[638,4288,4289],{},[16,4290,4291],{},"My rank",[638,4293,4294],{},"Your own position (1 for the top row), shown in a plain badge",[620,4296,4297,4301],{},[638,4298,4299],{},[16,4300,1175],{},[638,4302,4303],{},"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",[620,4305,4306,4311],{},[638,4307,4308],{},[16,4309,4310],{},"Rank",[638,4312,4313],{},"The work item's shared position (1 is best), computed with the selected algorithm. The header and cells are right aligned",[12,4315,4316,4317,430,4319,4321],{},"Until you submit a ranking, the ",[16,4318,4291],{},[16,4320,1175],{}," cells stay empty. They fill in when you rank, and clear again when you withdraw.",[12,4323,4324],{},"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.",[12,4326,4327],{},"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.",[12,4329,4330,4331,4333,4334,4336,4337,4339,4340,569],{},"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 ",[16,4332,2310],{},", 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 the ",[16,4335,4147],{}," delete icon, shown to moderators and disabled until rankings exist. The participant row appears once someone has ranked, while the ",[16,4338,4147],{}," icon stays visible and becomes enabled. The tooltip on the icon explains that it deletes the rankings for all users. If affinity was the enforced ranking, clearing it also returns the bucket ranking mode to ",[16,4341,4151],{},[12,4343,4344,4345,4348,4349,4351,4352,4354],{},"A moderator can also send the shared ranking to Jira. The ",[16,4346,4347],{},"Sync to Jira"," transition icon sits after ",[16,4350,2310],{}," and before ",[16,4353,4147],{},", and only a moderator sees it.",[26,4356,4357],{},[29,4358,4359,4361],{},[16,4360,4347],{}," ranks the listed work items in Jira in their shared rank order. Scrumpy uses the rank field configured on the board you opened the space page from. If Jira does not report a board, or the board does not configure a rank field, Jira's default rank field is used. The work item ranked 1 stays where it is in Jira, and the other listed work items follow it in rank order, so the listed work items form one ranked block while other work in the space keeps its place.",[12,4363,4364],{},"The icon shows a spinner while it runs. Hover the icon to see a note that pressing it synchronizes the affinity ranking with the Jira rank. If Jira refuses the change, an error appears below the controls and you can try again. Jira must allow you to rank work items for this to work.",[12,4366,930,4367,4369],{},[16,4368,1462],{}," tab shows a horizontal bar chart of each work item's position, best at the top. It is read-only.",[233,4371,1490],{"id":4372},"dot",[12,4374,4375,4376,430,4378,4222,4380,4382,4383,4385,4386,4231,4388,1191],{},"Dot ranks the work items by dots. It has two sub-tabs, ",[16,4377,2303],{},[16,4379,1462],{},[16,4381,2303],{}," holds the table and the controls, and ",[16,4384,1462],{}," shows a horizontal bar chart of each work item's total dots, lowest at the top, with no controls. Every participant sees ",[16,4387,1462],{},[16,4389,999],{},[12,4391,4392,4393,4395],{},"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. If the enforced ranking is ",[16,4394,1490],{}," and the bucket panel has a vote or a completed session, the dot table is locked: you cannot place or remove dots or withdraw, and the lock column shows the lock icon on every work item. The other ranking stays editable.",[12,4397,4398,4399,4402],{},"Tick ",[16,4400,4401],{},"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.",[12,4404,4405],{},"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.",[12,4407,4408],{},"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.",[12,4410,4411],{},"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:",[26,4413,4414,4419,4424,4429],{},[29,4415,4416,4418],{},[16,4417,1490],{}," 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.",[29,4420,4421,4423],{},[16,4422,4310],{}," is the total number of dots the work item holds across all participants.",[29,4425,4426,4428],{},[16,4427,2310],{}," clears your dots and returns your whole budget.",[29,4430,4431,4433,4434,4436],{},[16,4432,4347],{}," transition icon, beside ",[16,4435,2310],{},", is available to every participant, including non-moderators, and stays enabled whenever at least one work item is listed. It adds your Jira vote to every work item you have dotted in this panel and removes your Jira vote from every work item you have not dotted. The button shows a spinner while it runs. Hover the button to see a note that pressing it synchronizes your dot votes with your Jira votes. If Jira rejects a vote, an error appears below the controls and you can try again. Jira must allow users to vote on issues for this to work.",[12,4438,4439],{},"A short hint above the table reminds voters to place dots; it disappears for you as soon as you place your first dot, without waiting for the save. The dot rank column in the planning table follows each dot at once, so the counts there never lag behind the dots you place. 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.",[12,4441,4442],{},"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.",[12,4444,4445],{},"The dots left are shown in a badge colored by how many remain: grey above half, yellow above a quarter, and red otherwise.",[12,4447,4448,4449,4451,4452,4454,4455,4152],{},"A moderator can clear all dot rankings with the ",[16,4450,4147],{}," delete icon beside ",[16,4453,2310],{},", shown to moderators and disabled while no dot rankings are visible. The tooltip on the icon explains that it deletes the rankings for all users. The icon follows your local dots immediately: it is enabled as soon as you place a dot and disabled again when the last dot is removed, before the save reaches the server. 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 ",[16,4456,4151],{},[12,4458,4459],{},"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.",[233,4461,1493],{"id":4462},"bucket",[12,4464,4465,4466,4469,4470,4472],{},"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. A ",[16,4467,4468],{},"No estimate"," row at the top holds the work items you have not voted on in this session. A short hint above the table in the ",[16,4471,2303],{}," tab reminds voters to drag a work item under a card; it disappears for you after your first drop.",[12,4474,4475,4476,430,4478,4480,4481,4483,4484,4486,4487,4489,4490,4492],{},"The Bucket panel has two tabs below the perspective description: ",[16,4477,2303],{},[16,4479,1462],{},". ",[16,4482,2303],{}," holds the table and its hint. ",[16,4485,1462],{}," shows a vote heat map, and every participant sees the tab whether ",[16,4488,999],{}," is on or off. The voters group, the ",[16,4491,2310],{}," button, and the description stay below the tabs, so they do not move when you switch tabs.",[12,4494,4495,4496,4498,4499,4501,4502,4504,4505,4507,4508,4510],{},"A completed session keeps your recorded vote in the table, so its work item stays under its card until the session is cancelled or accepted. When the perspective has an enforced ranking and at least one voting session in the bucket panel is completed, bucket voting is locked: you cannot drag work items or use ",[16,4497,2310],{},", and the ranking selector allows only ",[16,4500,4151],{},". A message explains the lock. A completed session also cannot be moved or re-estimated when the bucket panel is not fully locked. Cancel or accept completed sessions to unlock them. 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 No estimate. Drag a work item under a card row to vote for that card, and drop it under ",[16,4503,4468],{}," 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 ",[16,4506,2310],{}," below the voters group. The items return to ",[16,4509,4468],{}," right away, and the button is disabled once the voter has no votes left in the panel.",[12,4512,4513,4514,4516],{},"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. When the perspective writes a time value, the card label has a small centered duration below it. A T-shirt card also shows its mapped story points there, for example \"3 sp · 2 days\"; it shows only the units the perspective writes. When neither is written, no small text appears. The ",[16,4515,4468],{}," row shows the backlog icon in the Type column, center aligned, and has no text label. Card and No estimate rows are highlighted and cannot be dragged. The Participants column also shows each work item's vote progress, for example \"33% or 1 out of 3 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.",[12,4518,930,4519,4521,4522,4524,4525,4527],{},[16,4520,1462],{}," tab shows a heat map of the votes per work item and estimate. Each column is an enabled card, each row is a work item, and the cell colour moves from the warning colour to the error colour as more participants vote the same card for the same work item. The number in the cell is the vote count. The heat map stretches across the full width of the bucket panel. With ",[16,4523,999],{}," on, it counts every participant's votes. With ",[16,4526,999],{}," off, it counts your own votes and every vote of completed sessions; the rest of the votes stay hidden until their session completes. The moderator sees the same scope as everyone else.",[12,4529,4530,4531,4533,4534,4178,4537,4540,4541,430,4543,4545],{},"A moderator sets the bucket table's ranking mode from the control beside the perspective title: ",[16,4532,4151],{}," (the default, plain table), ",[16,4535,4536],{},"Affinity ranking",[16,4538,4539],{},"Dot ranking",". Only a moderator can change it, and a ranking option becomes available once someone has submitted that ranking. The plain table has no Rank column. ",[16,4542,4536],{},[16,4544,4539],{}," add a Rank column on the right, where each work item shows its rank in a regular lozenge and a card row leaves that cell empty.",[12,4547,4548],{},"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.",[12,4550,4551,4552,2537,4554,4063,4556,4558,4559,4561,4562,4564,4565,4567],{},"Switching into ",[16,4553,4536],{},[16,4555,4539],{},[16,4557,4151],{},", or between the two ranking modes, moves every listed work item to ",[16,4560,4468],{}," right away, before the server responds. If the change is refused, the previous mode and votes return. Switching back to ",[16,4563,4151],{}," keeps the votes. If the last session for an enforced ranking is cancelled or accepted, the bucket ranking mode returns to ",[16,4566,4151],{}," automatically. A completed session keeps the ranking enforced and locks it until the session is cancelled or accepted.",[12,4569,4570],{},"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.",[12,4572,4573],{},"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.",[12,4575,4576],{},"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.",[12,4578,4579,4580,4582,4583,4585,4586,4588],{},"Once an enforced ranking has at least one vote or completed session 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 ",[16,4581,2310],{}," button. A completed session also locks bucket voting and allows the ranking selector to switch only to ",[16,4584,4151],{},". A notice appears in the affected tab, and the other ranking tab stays editable. Changing into or between enforced rankings clears the votes; with a completed session, only switching to ",[16,4587,4151],{}," is allowed.",[12,4590,4591,4592,4594],{},"In the ranked views, work items are listed from best to worst, and each row shows a ",[16,4593,4310],{}," column. Work items of equal rank can be reordered freely within the same card or the No estimate group, but the card rows never move and keep their configured order. No estimate work items stay in the No estimate group at the top. Reordering within the same card or No estimate 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. A free scale perspective follows the same rule with the estimate in place of the card: with a ranking enforced, changing an estimate also moves the work items the change passes to the new estimate, from the estimate field, from the single voting panel and from a planning table bulk field alike, so the rank order stays intact. This holds even when the perspective also has the extra cards enabled, because the numeric estimate always follows the estimate rules.",[233,4596,4598],{"id":4597},"free-scale-bucket","Free scale Bucket",[12,4600,4601,4602,4604,4605,4607,4608,4610,4611,4613],{},"A free scale perspective has no cards, so its Bucket tab replaces the card rows with gap rows. A completed session keeps your recorded vote, so its work item stays at its estimate instead of moving to ",[16,4603,4468],{}," until the session is cancelled or accepted. A completed session cannot be moved or re-estimated. When the ranking is enforced and a completed session exists, every free scale estimate field is disabled and the lock column shows the lock icon on every work item. The ",[16,4606,2303],{}," tab lists the work items from the smallest to the largest estimate. Work items with the same estimate sit together, and no gap row separates them. A highlighted gap row between two different estimates shows the distance, for example \"3 sp gap\". Its height is relative to the other gap rows in the table: the smallest gap present is 21 pixels high and the largest gap present is 90 pixels high, and any gap in between is scaled proportionally, so a table whose gaps are 4 sp, 5 sp and 6 sp still shows 21 pixels, 56 pixels and 90 pixels. Every gap row in a table with one gap, or with gaps of the same size, keeps the 21 pixel height. Work items without a story point vote sit in a highlighted ",[16,4609,4468],{}," group at the top. A narrow first column draws the story point timeline. It has no labels: a 4 pixel line starts at the first work item's dot and ends at the last work item's dot, each work item row with an estimate has a 12 pixel dot on it, and the first and last estimated work items have a 16 pixel dot with a 4 pixel hollow center that closes the timeline. When the perspective writes a time value, each estimation field shows the humanized duration in small text below the story points, centered. The ",[16,4612,4468],{}," group has no dot and no line, so a work item without an estimate never shows a circle on the timeline. Gap rows have no dot, no vertical padding or margins, draw their stretch of the timeline as a dotted line of 4 pixel squares with 4 pixel gaps, and keep their height to show the distance between estimates.",[12,4615,4616,4617,4619,4620,4622,4623,4625,4626,4628],{},"Each work item row shows its Jira key, a compact story point field, and the ",[16,4618,4310],{}," column from the selected ranking mode. Type in the field and click away to save an exact estimate. With a ranking enforced, changing an estimate keeps the ascending rank order: the work items the change passes take the new estimate and join that estimate group, work items of the same rank stay where they are, and withdrawing the estimate also clears the better-ranked estimated work items above it, the way dropping a card into No estimate works. A cross-circle ",[16,4621,2310],{}," button inside the field clears that one vote without editing the number. Drag a work item into a gap to set its estimate to the rounded midpoint of the two neighbouring estimates, drag it onto another work item to give it the same estimate, or drag it into ",[16,4624,4468],{}," to withdraw its vote. The move appears right away and is saved in the background; if the save fails, the row returns to the previous estimate. A voter can withdraw every vote in the panel with ",[16,4627,2310],{}," below the voters group. The description stays below the tabs.",[12,4630,930,4631,4633,4634,2457,4636,4638,4639,4641],{},[16,4632,1462],{}," tab shows the recorded votes in a chart: the horizontal axis is story points, each work item has its own row, and every vote is a dot in that work item's colour. Votes at the same story points fan out so they stay visible. The axis labels are whole story point numbers. A dashed cross marks the perspective's averaged story points on each work item row, rounded to a whole number. The cross appears only when more than one participant voted on that work item; with a single vote it would sit on the dot, so it is hidden. Like the card bucket, every participant sees ",[16,4635,1462],{},[16,4637,999],{}," on, the chart plots every participant's vote. With ",[16,4640,999],{}," off, it plots your own votes and every vote of completed sessions, and the moderator follows the same scope.",[233,4643,4645],{"id":4644},"parametric-bucket","Parametric Bucket",[12,4647,4648,4649,4651,4652,4654,4655,4657,4658,4660],{},"A parametric perspective has a Bucket tab with the same layout, ordering, gap rows and timeline as the free scale one, with two differences. Nothing can be dragged: the table is read only and every vote is cast from its row or from the voting panel. Each row shows the computed result in a read only, compact, subtle number field with the ",[16,4650,1286],{}," suffix, a cross-circle ",[16,4653,2310],{}," button and an ",[16,4656,1480],{}," button inside the field. The edit button opens the same slider popup as the planning table, and pressing ",[16,4659,2303],{}," there saves that work item's vote with its slider positions. When the perspective writes a time value, the humanized duration of the result appears in small text below the field, centred. With a ranking enforced, a vote from this tab, from the voting panel or from the planning table bulk field keeps the ascending rank order the same way a free scale vote does, and the work items it passes take the same result and slider positions. A work item that already voted shows its recorded sliders when the popup opens, so the numbers always match the saved result.",[21,4662,4664],{"id":4663},"perspective-columns","Perspective Columns",[12,4666,4667],{},"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:",[26,4669,4670,4676,4682],{},[29,4671,4672,4675],{},[16,4673,4674],{},"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.",[29,4677,4678,4681],{},[16,4679,4680],{},"Voting session state",": In progress, Paused, or Complete, shown as a badge.",[29,4683,4684,4687,4688,4691,4692,4691,4695,4698,4699,4701],{},[16,4685,4686],{},"Current estimate",": the latest estimate value from Jira, shown when no session is active. Each configured estimate field appears as its own badge in the order story points, time, T-shirt size, separated by middle dots; a field that is not configured is omitted. Story points show an \"sp\" suffix, time values show work-day durations, and T-shirt sizes show the size label. Field target badges match the selected fields, so a perspective with story points, time, and T-shirt fields can show ",[604,4689,4690],{},"10 sp"," · ",[604,4693,4694],{},"1 day",[604,4696,4697],{},"S",". With the ",[16,4700,1566],{}," target, a T-shirt perspective writes the mapped story points to the board and the size label to the T-shirt field; the cell shows the story points and the size label. A time board shows the duration and the size label. A numeric board never shows a duration. The duration appears only when the estimation target writes a time value: a time board or a Time field, or a Field target with both a story points field and a Time field. The bulk voting cell and the inline voting panel use the same units, so a time board shows the duration in the editor preview and in the open-voting badges, while a numeric board keeps story points. If you change the perspective's estimation target, sequence, story points field, time field, T-shirt field, story points to hours, or estimation board while the planning table is open, the perspective column reloads its values from Jira, so the shown estimates match the new configuration without a page reload.",[21,4703,4705],{"id":4704},"progress-and-status","Progress and Status",[12,4707,4708,4709,4711],{},"When a planning session has a date range, its panel shows a progress bar and a status below the buttons at the bottom: ",[16,4710,2162],{}," once the end date has passed, a countdown before the start date, or the remaining time while it is in progress.",[21,4713,3649],{"id":4714},"deleting-a-planning-session",[12,4716,4717,4718,3642,4720,4722],{},"When a planning session is no longer needed, click ",[16,4719,3562],{},[16,4721,568],{},". A confirmation appears first, because deleting a planning session removes it and all of its items permanently, so it disappears from the tab list. Deleting it also removes every record that belongs to the planning session: its chat, the work item chat and reactions of its items, rankings, capacity planning data, standup data, retrospective data, and linked voting sessions.",[12,4724,4725,4726,4729],{},"If there are still active voting sessions, the confirmation becomes a ",[16,4727,4728],{},"Pending estimation sessions"," warning with three choices:",[26,4731,4732,4738,4744],{},[29,4733,4734,4737],{},[16,4735,4736],{},"Do nothing"," (the default): delete the planning session without accepting or cancelling its voting sessions first. The linked voting sessions are removed with the planning session.",[29,4739,4740,4743],{},[16,4741,4742],{},"Cancel all",": cancel every voting session, including completed ones, before deleting the planning session.",[29,4745,4746,4749],{},[16,4747,4748],{},"Accept completed",": accept the estimates of every completed voting session, including any value the moderator set, before deleting the planning session.",[12,4751,1342,4752,4755,4756,4758],{},[16,4753,4754],{},"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 deleted, it comes back. If a Jira write fails during ",[16,4757,4748],{},", the work items whose write succeeded are accepted, the failed session stays completed so it can be retried, and an error dialog after the delete lists the failed work item and the reason.",[12,4760,4761],{},"If another moderator deletes a planning session while your page is open, its tab disappears from your list by itself and the first remaining session opens. You see no error message and nothing asks you to reload.",[21,4763,4765],{"id":4764},"estimating-inline","Estimating Inline",[12,4767,4768,4769,4772],{},"The Refinement\u002Fgrooming 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 ",[16,4770,4771],{},"No work item selected"," empty state.",[12,4774,4775],{},"The panel and the planning table stay in step while you work. A vote, a pause, a resume, a completion, a cancellation, or a changed required-voter list made in one place appears in the other straight away. An accepted estimate updates both places as soon as the estimate is written. If a save fails, both places return to the previous state together.",[12,4777,4778,4779,4781],{},"The work item key in the table shows the summary in a tooltip. When a moderator edits the summary in the panel's ",[16,4780,2040],{}," tab, the tooltip updates without a reload. When a perspective estimates with a board, the current estimate comes from Jira's board estimation, so it appears even when the estimation field is hidden from the work item screen.",[12,4783,4784,4785,430,4787,4789,4790,4792,4793,4795,4796,4799,4800,4802,4803,4805,4806,4808],{},"The inline panel has ",[16,4786,2303],{},[16,4788,2040],{}," while the session runs, plus ",[16,4791,1462],{}," with open voting and the perspective's chart tab when the perspective is parametric. ",[16,4794,2040],{}," shows a ",[16,4797,4798],{},"Summary"," label above the current Jira summary and a ",[16,4801,631],{}," label above the work item description rendered as rich text; participants who are not moderators see the description without an avatar. It is read once per work item and reused while the page stays open; a summary or description change made in the Details tab appears for other participants without a reload, and an edit in one perspective also updates the Details tab of every other perspective in the same panel; moderators can edit both the summary and the description there, and every participant sees the current Jira content. An edit saves when you click away, switch to another tab, or close the panel, even if the short description pause has not finished. After completion the inline panel keeps ",[16,4804,1462],{},", the chart tab for a parametric perspective, and ",[16,4807,2040],{},", with the final result below the tabs.",{"title":153,"searchDepth":154,"depth":154,"links":4810},[4811,4812,4813,4817,4823,4826,4833,4834,4835,4836],{"id":3487,"depth":154,"text":3488},{"id":1984,"depth":154,"text":1985},{"id":3652,"depth":154,"text":3653,"children":4814},[4815,4816],{"id":3659,"depth":784,"text":3660},{"id":3689,"depth":784,"text":3690},{"id":3769,"depth":154,"text":3770,"children":4818},[4819,4820,4821,4822],{"id":3802,"depth":784,"text":3803},{"id":3834,"depth":784,"text":3835},{"id":3857,"depth":784,"text":3858},{"id":3920,"depth":784,"text":3921},{"id":4056,"depth":154,"text":4057,"children":4824},[4825],{"id":4126,"depth":784,"text":4127},{"id":4158,"depth":154,"text":4159,"children":4827},[4828,4829,4830,4831,4832],{"id":4214,"depth":784,"text":1487},{"id":4372,"depth":784,"text":1490},{"id":4462,"depth":784,"text":1493},{"id":4597,"depth":784,"text":4598},{"id":4644,"depth":784,"text":4645},{"id":4663,"depth":154,"text":4664},{"id":4704,"depth":154,"text":4705},{"id":4714,"depth":154,"text":3649},{"id":4764,"depth":154,"text":4765},"Create planning sessions in Jira, add work items from a filter or work item view, and estimate a backlog in bulk.","Planning Sessions","\u002Fog\u002Fguide-planning-sessions.jpg",[4841,4842,4843,4844],"sprint planning","backlog refinement","bulk voting","jira planning",{},8,"\u002Fgetting-started\u002Fplanning-sessions",{"title":3473,"description":4837},{"loc":4847,"lastmod":802},"planning-sessions","guide\u002Fen\u002Fplanning-sessions","guide\u002Fplanning-sessions","Fqq0SvXd6Di2LRZ7TN9xfb0KrOEosUwjoiSwxpkPlcs",{"id":4855,"title":4856,"body":4857,"dateModified":159,"datePublished":160,"description":5036,"extension":162,"heading":4883,"image":5037,"imageAlt":4883,"keywords":5038,"locale":168,"meta":5042,"navigation":170,"order":5043,"path":5044,"section":173,"seo":5045,"sitemap":5046,"slug":5047,"stem":5048,"translationKey":5049,"__hash__":5050},"guide\u002Fguide\u002Fen\u002Festimation-history.md","Estimation History | Scrumpy Planning Poker",{"type":9,"value":4858,"toc":5027},[4859,4862,4866,4881,4885,4888,4891,4895,4898,4902,4905,4909,4912,4948,4954,4958,4967,4971,4974,4997,5001,5004,5024],[12,4860,4861],{},"Every accepted estimate is recorded in the estimation log, giving your team a record of sizing decisions for the last 90 days.",[21,4863,4865],{"id":4864},"viewing-estimation-history","Viewing Estimation History",[12,4867,4868,4869,4872,4873,4876,4877,4880],{},"Open any Jira work item, expand the ",[16,4870,4871],{},"Activity"," area, open ",[16,4874,4875],{},"Apps",", and choose ",[16,4878,4879],{},"Estimation log",". This log shows each accepted estimate for the work item, newest first, with the perspective that produced it. When the work item has no accepted estimates yet, the log shows an empty state instead of a list. If the space has a password, the log asks for it first.",[61,4882],{"alt":4883,"caption":4883,"stem":4884},"Estimation History","guide-estimation-log",[12,4886,4887],{},"Scrumpy checks that you can open the work item in Jira before it shows the history. A work item hidden from you by Jira issue-level security is not returned.",[12,4889,4890],{},"A space administrator can hide the Scrumpy panel on work items and the Space Estimations page in space settings. The estimation log is hidden only when both of those are hidden. While either one is shown, the log stays available.",[21,4892,4894],{"id":4893},"pagination-and-navigation","Pagination and Navigation",[12,4896,4897],{},"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 log. Use the pagination controls to move between pages.",[21,4899,4901],{"id":4900},"live-updates","Live Updates",[12,4903,4904],{},"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. If the space has a password, live updates start only after you enter it.",[21,4906,4908],{"id":4907},"whats-recorded","What's Recorded",[12,4910,4911],{},"Each estimation history entry shows:",[26,4913,4914,4920,4925,4930,4936,4942],{},[29,4915,4916,4919],{},[16,4917,4918],{},"Moderator",": the moderator who finalized the estimate, shown as the entry's avatar",[29,4921,4922,4924],{},[16,4923,465],{},": how many of the required voters had voted",[29,4926,4927,4929],{},[16,4928,3251],{},": which estimation perspective was used",[29,4931,4932,4935],{},[16,4933,4934],{},"Duration",": how long the session took, shown as \"for {duration}\"",[29,4937,4938,4941],{},[16,4939,4940],{},"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",[29,4943,4944,4947],{},[16,4945,4946],{},"Timestamp",": when the estimate was accepted, shown in your Jira timezone",[12,4949,4950,4951,569],{},"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 ",[16,4952,4953],{},"Overridden by the moderator",[21,4955,4957],{"id":4956},"retention-and-deletion","Retention and Deletion",[12,4959,4960,4961,4963,4964,4966],{},"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 ",[16,4962,3403],{}," on the space settings ",[16,4965,355],{}," 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.",[21,4968,4970],{"id":4969},"how-results-flow-to-jira","How Results Flow to Jira",[12,4972,4973],{},"When a moderator accepts an estimate:",[66,4975,4976,4979,4994],{},[29,4977,4978],{},"The final estimate is computed from all votes using the perspective's averaging method",[29,4980,4981,4982],{},"The result is written to Jira based on the perspective's estimation target:\n",[26,4983,4984,4989],{},[29,4985,4986,4988],{},[16,4987,1566],{},": 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",[29,4990,4991,4993],{},[16,4992,1312],{},": Updates the configured custom fields for points, time, or T-shirt sizes. A T-shirt field receives the size label",[29,4995,4996],{},"The full voting session is saved for reference",[21,4998,5000],{"id":4999},"dashboard-analytics","Dashboard Analytics",[12,5002,5003],{},"The space Dashboard aggregates estimation history across all work items and perspectives to provide:",[26,5005,5006,5009,5012,5015,5018,5021],{},[29,5007,5008],{},"Daily accepted estimate counts",[29,5010,5011],{},"Average estimates by perspective",[29,5013,5014],{},"Average voting duration by perspective",[29,5016,5017],{},"Average certainty scores",[29,5019,5020],{},"Average variation scores",[29,5022,5023],{},"Average number of voters per session",[12,5025,5026],{},"Use the date range selector to focus on recent sprints or compare long-term trends.",{"title":153,"searchDepth":154,"depth":154,"links":5028},[5029,5030,5031,5032,5033,5034,5035],{"id":4864,"depth":154,"text":4865},{"id":4893,"depth":154,"text":4894},{"id":4900,"depth":154,"text":4901},{"id":4907,"depth":154,"text":4908},{"id":4956,"depth":154,"text":4957},{"id":4969,"depth":154,"text":4970},{"id":4999,"depth":154,"text":5000},"The estimation log records every accepted estimate for 90 days, with live updates and the results that flow back to Jira.","\u002Fog\u002Fguide-estimation-history.jpg",[5039,5040,5041],"estimation history","jira estimation log","story point history",{},9,"\u002Fgetting-started\u002Festimation-history",{"title":4856,"description":5036},{"loc":5044,"lastmod":159},"estimation-history","guide\u002Fen\u002Festimation-history","guide\u002Festimation-history","capd-XdWeVu5W3ZygjaVPG99wKqQUH7l7x_7RWhTJ9A",{"id":5052,"title":5053,"body":5054,"dateModified":802,"datePublished":5160,"description":5161,"extension":162,"heading":5080,"image":5162,"imageAlt":5080,"keywords":5163,"locale":168,"meta":5166,"navigation":170,"order":5167,"path":5168,"section":173,"seo":5169,"sitemap":5170,"slug":5171,"stem":5172,"translationKey":5173,"__hash__":5174},"guide\u002Fguide\u002Fen\u002Ffeedback-and-support.md","Feedback and Support | Scrumpy Planning Poker",{"type":9,"value":5055,"toc":5155},[5056,5064,5068,5078,5082,5086,5101,5107,5113,5117],[12,5057,930,5058,5060,5061,5063],{},[16,5059,359],{}," tab is the rightmost tab on the Space Estimations page, aligned to the right of the tab bar after ",[16,5062,355],{},". 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.",[21,5065,5067],{"id":5066},"rating-the-app","Rating the App",[12,5069,5070,5071,4066,5074,5077],{},"Choose one of five ratings, from ",[16,5072,5073],{},"Not satisfied",[16,5075,5076],{},"Excellent",". Rating is optional when you also leave a suggestion.",[61,5079],{"alt":5080,"caption":5080,"stem":5081},"Feedback and Support","guide-feedback",[21,5083,5085],{"id":5084},"suggesting-an-improvement","Suggesting an Improvement",[12,5087,5088,5089,5092,5093,5096,5097,5100],{},"Describe an idea, a problem, or a request in the ",[16,5090,5091],{},"How can we improve the app?"," box, up to ",[16,5094,5095],{},"1000 characters",". A counter under the box shows how many characters you have used, for example ",[16,5098,5099],{},"128 \u002F 1000",", and the box stops accepting text at the limit. You can send a suggestion on its own, a rating on its own, or both together.",[12,5102,3504,5103,5106],{},[16,5104,5105],{},"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.",[12,5108,5109,5110,5112],{},"You can send one message per minute, so a second message within a minute is not sent. The tab then shows how many seconds are left before you can try again, and ",[16,5111,5105],{}," stays disabled until the wait is over. A few messages per day are allowed in each space, which keeps the feedback channel readable for everyone and protects it from automated floods. If a message is longer than 1000 characters, it is refused and the tab explains the limit; the counter and the box already prevent this when you type in the form.",[21,5114,5116],{"id":5115},"support-and-contact","Support and Contact",[26,5118,5119,5125,5131,5137,5143,5149],{},[29,5120,5121,5124],{},[16,5122,5123],{},"Support forum",": opens the Scrumpy support portal in a new tab, where you can report an issue or ask for help",[29,5126,5127,5130],{},[16,5128,5129],{},"Check for new updates",": opens the Connected apps page for this site in a new tab, where a site admin can install an available app update",[29,5132,5133,5136],{},[16,5134,5135],{},"Follow us",": links to Facebook, LinkedIn, and YouTube",[29,5138,5139,5142],{},[16,5140,5141],{},"Copyright",": the AELBOX copyright notice links to aelbox.com",[29,5144,5145,5148],{},[16,5146,5147],{},"Contact",": the support email address for direct questions",[29,5150,5151,5154],{},[16,5152,5153],{},"Atlassian Marketplace",": opens the app's Atlassian Marketplace listing in a new tab",{"title":153,"searchDepth":154,"depth":154,"links":5156},[5157,5158,5159],{"id":5066,"depth":154,"text":5067},{"id":5084,"depth":154,"text":5085},{"id":5115,"depth":154,"text":5116},"2026-10-09","Send feedback from the Scrumpy Feedback tab, rate the app on the Marketplace or reach the AELBOX support team.","\u002Fog\u002Fguide-feedback-and-support.jpg",[5164,5165],"scrumpy support","atlassian marketplace feedback",{},10,"\u002Fgetting-started\u002Ffeedback-and-support",{"title":5053,"description":5161},{"loc":5168,"lastmod":802},"feedback-and-support","guide\u002Fen\u002Ffeedback-and-support","guide\u002Ffeedback-and-support","byRygKNmyICubz_O1iVx3VzSnk6PDVHULcbzvPaiWg8",{"id":5176,"title":5177,"body":5178,"dateModified":159,"datePublished":5160,"description":5203,"extension":162,"heading":5204,"image":5205,"imageAlt":5205,"keywords":5206,"locale":168,"meta":5209,"navigation":170,"order":5210,"path":5211,"section":173,"seo":5212,"sitemap":5213,"slug":5214,"stem":5215,"translationKey":5216,"__hash__":5217},"guide\u002Fguide\u002Fen\u002Fapp-language.md","App Language | Scrumpy Planning Poker",{"type":9,"value":5179,"toc":5201},[5180,5183,5186,5189,5192,5195,5198],[12,5181,5182],{},"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, the audit logs, the Getting started guide, and the tutorials.",[12,5184,5185],{},"Screenshots in the guide and tutorials stay in English. They follow the Jira theme instead, so you see the light or dark version that matches the theme you use.",[12,5187,5188],{},"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).",[12,5190,5191],{},"Durations, countdowns, work-hour totals, and the day labels on the dashboard charts in the app also follow your language. For example, a German user reads \"5 Minuten\" instead of \"5 minutes\", and the dashboard uses the German month names and date order.",[12,5193,5194],{},"Error messages follow your language too. When a planning session already exists, a work item cannot be written to Jira, or a ranking is locked, the message you see is translated rather than the English text returned by the server.",[12,5196,5197],{},"Parameter names in a parametric perspective are translated: until you rename a parameter, it reads \"Parameter 1\", \"Parameter 2\", and so on in your language. Renaming it replaces the default with your own text for everyone who opens the perspective.",[12,5199,5200],{},"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.",{"title":153,"searchDepth":154,"depth":154,"links":5202},[],"Scrumpy follows your Jira language across all 26 supported languages; there is nothing to configure.","App Language",null,[5207,5208],"scrumpy languages","jira localization",{},11,"\u002Fgetting-started\u002Fapp-language",{"title":5177,"description":5203},{"loc":5211,"lastmod":159},"app-language","guide\u002Fen\u002Fapp-language","guide\u002Fapp-language","8WgSfWizCwpcrvtCEsELXoJhtD78olsDp-Gqawag7H4",{"id":5219,"title":5220,"body":5221,"dateModified":802,"datePublished":5553,"description":5554,"extension":162,"heading":5266,"image":5555,"imageAlt":5266,"keywords":5556,"locale":168,"meta":5560,"navigation":170,"order":5561,"path":5562,"section":173,"seo":5563,"sitemap":5564,"slug":5565,"stem":5566,"translationKey":5567,"__hash__":5568},"guide\u002Fguide\u002Fen\u002Farchiving-to-confluence.md","Archiving to Confluence | Scrumpy Planning Poker",{"type":9,"value":5222,"toc":5543},[5223,5226,5230,5241,5247,5251,5264,5268,5285,5294,5300,5304,5314,5318,5326,5339,5342,5369,5376,5379,5383,5397,5400,5402,5422,5435,5439,5451,5457,5470,5474,5477,5504,5507,5511,5517,5537],[12,5224,5225],{},"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.",[21,5227,5229],{"id":5228},"configuring-the-confluence-space","Configuring the Confluence Space",[12,5231,5232,5233,5236,5237,5240],{},"In space settings, open the ",[16,5234,5235],{},"Permissions"," tab and find ",[16,5238,5239],{},"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. The search shows only Confluence spaces your account can access.",[12,5242,5243,5244,5246],{},"If Scrumpy is not installed on Confluence for your site, the ",[16,5245,5239],{}," field is disabled and a note explains that Confluence export is available only after the app is installed on Confluence.",[21,5248,5250],{"id":5249},"archiving-a-planning-session","Archiving a Planning Session",[12,5252,5253,5254,5256,5257,5260,5261,5263],{},"On the ",[16,5255,340],{}," tab, the ",[16,5258,5259],{},"Archive"," button sits at the end of the action bar below the planning table and appears only when a Confluence space is configured. Clicking ",[16,5262,5259],{}," opens a dialog that previews exactly what will be written:",[61,5265],{"alt":5266,"caption":5266,"stem":5267},"Archiving to Confluence","guide-archive",[26,5269,5270,5273,5276,5279,5282],{},[29,5271,5272],{},"When the planning session has a timer, the window is shown as a start badge and an end badge",[29,5274,5275],{},"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",[29,5277,5278],{},"A planning session without a timer has no window, so its preview lists every work item with an accepted estimate",[29,5280,5281],{},"Work items you cannot open in Jira are omitted, including work items hidden by Jira issue-level security",[29,5283,5284],{},"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",[12,5286,5287,5288,5290,5291,5293],{},"Confirm with ",[16,5289,5259],{},". On success the dialog shows a link to the created page. The ",[16,5292,5259],{}," 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.",[12,5295,5296,5297,5299],{},"When Scrumpy is not installed on Confluence, the ",[16,5298,5259],{}," button is disabled and explains why. The Delete dialogs then do not offer the archive option.",[21,5301,5303],{"id":5302},"archiving-while-deleting","Archiving While Deleting",[12,5305,5306,5307,5310,5311,5313],{},"When a Confluence space is configured, both Delete dialogs offer a ",[16,5308,5309],{},"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 Refinement\u002Fgrooming tab. The banner offers a ",[16,5312,581],{}," action that hides it.",[21,5315,5317],{"id":5316},"archiving-a-capacity-plan","Archiving a Capacity Plan",[12,5319,5253,5320,5322,5323,5325],{},[16,5321,343],{}," tab, select an active or future sprint in the combined table, then select ",[16,5324,5259],{}," in the capacity toolbar. The button is disabled when a closed sprint is selected, because a closed sprint is history only. Only a moderator can archive, and the action is available only after a Confluence space has been configured for the space.",[12,5327,5328,5329,5331,5332,5334,5335,5338],{},"The dialog previews the sprint, the goal and its votes, the decision, and the velocity summary before anything is written. The team and work item tables are written to the page only. While the preview loads, ",[16,5330,5259],{}," stays disabled. If the preview cannot load, the dialog says so, and you can close it and try again. Confirm with ",[16,5333,5259],{}," to create the page, or select ",[16,5336,5337],{},"Close"," to leave the capacity plan unchanged. When the page is ready, the dialog shows a link to it. If Confluence refuses the page, the dialog shows the reason and the capacity plan is not changed.",[12,5340,5341],{},"The page records:",[26,5343,5344,5347,5350,5353,5360,5363,5366],{},[29,5345,5346],{},"The planning session title, description, start and end time, and timezone, in the same header as the planning archive page, followed by the planning duration",[29,5348,5349],{},"The selected sprint name, state, start and end dates, and sprint goal",[29,5351,5352],{},"The up and down votes for the sprint goal",[29,5354,5355,5356,5359],{},"A ",[16,5357,5358],{},"Decision"," section that says whether the remaining estimate is below, within, or above the target capacity range",[29,5361,5362],{},"A velocity summary with the velocity per member, team velocity, team size, effective team size, team capacity, target capacity, healthy range, planned estimate, remaining estimate, and deviation from target",[29,5364,5365],{},"A team table with every member of the selected sprint, their utilization, and their hours of work out of the sprint working hours",[29,5367,5368],{},"The planned work items in their saved order, with their status and estimate. An estimate is shown in green while the running total stays below the healthy range, in yellow inside the range, and in red above it, matching the capacity table.",[12,5370,5371,5372,5375],{},"The header is the same one the planning archive page uses: the planning title and 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, and the timezone the dates are valid in. The planning duration follows the header as a plain line. The sprint goal and its up and down votes appear centered directly below the sprint name, and the sprint goal is shown without a label. The sprint start and end dates share one line and are separated by a dash, for example ",[16,5373,5374],{},"Oct 7, 2026 - Oct 15, 2026",". The team and work item tables use a wider layout, and the Work item column leaves room for a longer summary.",[12,5377,5378],{},"The page reflects the capacity plan as it currently appears, including changes that are still saved as a draft and have not been applied to Jira. Story point boards show story points, and time boards show work-day durations.",[21,5380,5382],{"id":5381},"archiving-a-retrospective","Archiving a Retrospective",[12,5384,5253,5385,5256,5387,5389,5390,5392,5393,5396],{},[16,5386,349],{},[16,5388,5259],{}," button sits before ",[16,5391,3592],{},". It is available to moderators in the ",[16,5394,5395],{},"Actions"," stage. In Feedback and Vote it stays disabled with an explanation, because the notes of other participants are still hidden until the team reveals them. Archiving creates or updates the Confluence page and does not close the planning session.",[12,5398,5399],{},"The dialog previews the archive for the selected sprint before anything is written. It shows the planning window, the board and sprint name, the sprint goal, the sprint state, how many notes each column contributes, and the action items with their work item type icon, their linked Jira work item or summary, and their hearts. The confirmation button stays disabled while the preview loads, when the preview cannot load, and when the sprint has neither notes nor action items. Only a moderator can archive.",[12,5401,5341],{},[26,5403,5404,5407,5410,5413,5416],{},[29,5405,5406],{},"The planning title, description, start and end time, and timezone",[29,5408,5409],{},"The board name, sprint name, sprint goal, sprint dates, and sprint state",[29,5411,5412],{},"A notes table with one column per retrospective column, such as Good, Bad, and Ugly. Each note sits in its own cell, and notes that the team grouped together share one cell. Authors, hearts, and votes are not written to the page.",[29,5414,5415],{},"A participants table with every note author, everyone who gave a heart, and every action item author, showing the number of notes and hearts for each person. The hearts column is headed with a heart icon.",[29,5417,5418,5419,5421],{},"An action items table with a ",[16,5420,4798],{}," first column that is twice as wide as before. A linked action item shows its Jira work item link; an action item without a link shows its summary as text. The rows keep the order the moderator set in the retrospective. The narrow last column is headed with a heart icon and shows the number of hearts in a colored badge. The number is the total hearts of the notes the action item came from, the same number the retrospective shows.",[12,5423,5424,5425,5428,5429,5431,5432,5434],{},"Retrospective archives use their own hierarchy: a root ",[16,5426,5427],{},"Retrospectives"," parent page, then a child page named after the space with a ",[16,5430,5427],{}," suffix, then the archive page. The page title carries the planning name, the sprint name, and the word ",[16,5433,349],{},", so it never collides with planning or capacity archives. Re-archiving the same sprint updates the existing page.",[21,5436,5438],{"id":5437},"archiving-a-standup","Archiving a Standup",[12,5440,5253,5441,5256,5443,5389,5445,5447,5448,5450],{},[16,5442,346],{},[16,5444,5259],{},[16,5446,3592],{}," and is available to moderators when a Confluence space is configured. Archiving never applies, discards, or completes the standup and never changes Jira. The dialog previews the planning window, the scope and space name, the participants with their presentation time, and the work items with their changes. Confirm with ",[16,5449,5259],{}," to create or update the page.",[12,5452,5453,5454,569],{},"The page records the planning header, the sprint, board, or filter name, the space name, the sprint goal and state, every assignee with presence, item count, and presentation time, and every work item with its status, presentation time, and changes. Presentation time is the countdown time the work item spent on screen, credited to its assignee. A staged change is marked ",[16,5455,5456],{},"Pending",[12,5458,5459,5460,5463,5464,5466,5467,5469],{},"Standup archives use the ",[16,5461,5462],{},"Plannings"," root. The child page is named after the space with a ",[16,5465,346],{}," suffix, and the page title carries the planning name, the scope name, the word ",[16,5468,346],{},", and the planning start time.",[21,5471,5473],{"id":5472},"the-archive-page","The Archive Page",[12,5475,5476],{},"Planning, capacity, retrospective, and standup archives all start with the same planning session header. The generated planning page contains:",[26,5478,5479,5485,5488,5491,5497],{},[29,5480,5481,5482,652],{},"The planning title, followed by the start date, time, and timezone (for example ",[16,5483,5484],{},"Sprint 42 - 2025-06-01 09:00 (Europe\u002FBerlin)",[29,5486,5487],{},"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",[29,5489,5490],{},"The timezone the dates are valid in",[29,5492,5355,5493,5496],{},[16,5494,5495],{},"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)",[29,5498,5499,5500,5503],{},"An ",[16,5501,5502],{},"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)",[12,5505,5506],{},"The page includes only the accepted estimates that fall between the planning session's start and end. A planning session without a timer has no window, so its page includes every accepted estimate, has no start, end, or timezone line, and its title carries only the planning name. All dates and times are rendered in the archiver's preferred timezone.",[21,5508,5510],{"id":5509},"page-hierarchy-and-re-archiving","Page Hierarchy and Re-Archiving",[12,5512,5513,5514,5516],{},"Planning-session archives are written under a fixed hierarchy: a root ",[16,5515,250],{}," parent page, then a child page named after the Jira space, then the archive page.",[12,5518,5519,5520,5522,5523,5526,5527,5529,5530,5533,5534,5536],{},"Capacity-plan archives use a separate hierarchy at the same level: a root ",[16,5521,5462],{}," parent page, then a child page named ",[604,5524,5525],{},"\u003Cspace name> - Capacity planning",", then the archive page. Standup archives share the ",[16,5528,5462],{}," root but use a child page named ",[604,5531,5532],{},"\u003Cspace name> - Standup",", and their page titles carry the word ",[16,5535,346],{},". The distinct page titles keep the four archive kinds apart and stop one from overwriting another.",[12,5538,5539,5540,5542],{},"Re-archiving the same sprint updates the existing capacity or standup page (matched by exact title inside the ",[16,5541,5462],{}," area) 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.",{"title":153,"searchDepth":154,"depth":154,"links":5544},[5545,5546,5547,5548,5549,5550,5551,5552],{"id":5228,"depth":154,"text":5229},{"id":5249,"depth":154,"text":5250},{"id":5302,"depth":154,"text":5303},{"id":5316,"depth":154,"text":5317},{"id":5381,"depth":154,"text":5382},{"id":5437,"depth":154,"text":5438},{"id":5472,"depth":154,"text":5473},{"id":5509,"depth":154,"text":5510},"2026-10-11","Archive planning sessions, capacity plans, stand-ups and retrospectives to Confluence pages that stay with your team.","\u002Fog\u002Fguide-archiving-to-confluence.jpg",[5557,5558,5559],"confluence archiving","sprint retrospective archive","jira confluence",{},12,"\u002Fgetting-started\u002Farchiving-to-confluence",{"title":5220,"description":5554},{"loc":5562,"lastmod":802},"archiving-to-confluence","guide\u002Fen\u002Farchiving-to-confluence","guide\u002Farchiving-to-confluence","frifiz6pWms7zEA57HRYz7R6D-Pf8PEpSyY6kbkapIc",{"id":5570,"title":5571,"body":5572,"dateModified":802,"datePublished":6480,"description":6481,"extension":162,"heading":343,"image":6482,"imageAlt":343,"keywords":6483,"locale":168,"meta":6487,"navigation":170,"order":6488,"path":6489,"section":173,"seo":6490,"sitemap":6491,"slug":393,"stem":6492,"translationKey":6493,"__hash__":6494},"guide\u002Fguide\u002Fen\u002Fcapacity-planning.md","Capacity planning | Scrumpy Planning Poker",{"type":9,"value":5573,"toc":6465},[5574,5577,5583,5586,5603,5627,5632,5636,5648,5651,5665,5672,5678,5684,5688,5691,5694,5746,5755,5758,5761,5764,5772,5786,5789,5795,5801,5826,5835,5838,5843,5854,5863,5868,5874,5894,5898,5904,5924,5927,5942,5946,5952,5955,5958,5982,5985,5994,5997,6002,6005,6009,6044,6050,6053,6056,6090,6093,6106,6113,6116,6120,6125,6157,6160,6164,6167,6183,6189,6193,6218,6273,6279,6283,6292,6298,6302,6310,6314,6322,6342,6345,6349,6352,6376,6382,6394,6397,6423,6426,6429,6433,6462],[12,5575,5576],{},"Capacity planning helps a Scrum team decide how much work fits into the next sprints. Scrumpy looks at the estimates your team completed in recent sprints. That average per team member is your velocity. A board that estimates in story points uses story points, and a board that estimates in time uses the original time estimates and shows them as durations such as 2 days, 4 hours. Capacity uses the estimation field configured on the selected board. If the space also has another story point field, the board's field is the one that counts.",[12,5578,5579,5580,5582],{},"Scrumpy then compares the work already planned for the next sprints with the capacity your team really has. The target capacity for a current or future sprint is that per-member velocity multiplied by the sprint's team size and adjusted by the team's utilization and time off. The ",[16,5581,1175],{}," dropdown sets how far the plan may differ from the target before a badge turns green or red. The working week settings decide which days count as working days and how many hours a full working day counts for.",[12,5584,5585],{},"In the Capacity planning tab you can:",[26,5587,5588,5591,5594,5597,5600],{},[29,5589,5590],{},"Add the closed sprints that set your velocity and the active or future sprints you want to plan.",[29,5592,5593],{},"See every sprint and its work items in one table, with the estimated total and the target range.",[29,5595,5596],{},"Adjust each team member's utilization and working hours for the sprint.",[29,5598,5599],{},"Rank the work items, or open a perspective tab and vote on them.",[29,5601,5602],{},"Apply the plan to Jira, or archive a sprint to Confluence.",[12,5604,5605,5606,5608,5609,5611,5612,2537,5614,5616,5617,430,5619,5621,5622,5624,5625,569],{},"Capacity belongs to a planning session. Open the ",[16,5607,343],{}," tab on the space page and choose a planning session tab. When the session you last opened is no longer available, the first planning session opens instead. The ",[16,5610,568],{}," button creates a planning session without leaving the tab. The planning session description, when one is set, appears at the top of the left side above the board selector and spans only the left side, so the right side starts higher and the tables line up. A moderator can click the description to change it in place, and it saves when the field loses focus with no ",[16,5613,3633],{},[16,5615,503],{}," buttons. The same planning sessions also appear on the ",[16,5618,346],{},[16,5620,349],{}," tabs, where you can run a sprint standup or retrospective. See the Sprint standups and Sprint retrospectives guides. When no description is set, a moderator sees a placeholder they can click to add one. Each board in the planning session keeps its own planned sprints, selected sprint, selected work item, selected team member, and open right-side tab. Switching boards does not clear another board's choices, and switching back restores them. The switch happens at once: the board's saved sprint, work item, and team member selection and its estimation unit change immediately, and the previous board's sprints are hidden while the new board loads. A board you already opened in this tab shows its sprints immediately and refreshes in the background. When the space page opens on the ",[16,5623,343],{}," tab, the tab loads its boards and sprints together with the planning session tabs, so the table appears in one step. If you open the tab later, it loads its boards and sprints when you select it. If the space has no Scrum board, the tab tells you that a Scrum board is needed. A new planning session starts with no sprints, so add the sprints you want to plan with ",[16,5626,399],{},[12,5628,5629],{},[16,5630,5631],{},"Everything you change on this screen is virtual: the sprints, the order, the team capacity, and the work item moves stay in Scrumpy. Jira changes only when you select Apply.",[21,5633,5635],{"id":5634},"plan-the-sprints","Plan the sprints",[12,5637,5638,5639,5641,5642,5644,5645,569],{},"Only the sprints you add to the selected board's view appear in the table. Select ",[16,5640,399],{},", next to ",[16,5643,3695],{}," in the toolbar, to open the sprint picker. The picker shows only sprints whose origin board is the board selected in the action bar. Sprints that originated on another board are not listed and cannot be added. Each sprint's estimate appears in a regular lozenge, for example ",[16,5646,5647],{},"3 sp",[12,5649,5650],{},"The picker has two tabs:",[26,5652,5653,5659],{},[29,5654,5655,5658],{},[16,5656,5657],{},"Past sprints"," lists closed sprints. Past sprints with a saved team are needed to calculate the velocity. Select at least 3 past sprints for a proper velocity calculation. If you select fewer, the velocity is calculated from the ones you selected. A past sprint with no team yet shows 0% in the Team column and does not count; select it and populate its team first.",[29,5660,5661,5664],{},[16,5662,5663],{},"Sprints"," lists active and future sprints. Select at least one of them before you can add the selection.",[12,5666,5667,5668,5671],{},"Both tabs list their sprints by start date, oldest first. Each row has a checkbox, the sprint name with its goal below it, its status, its start and end dates, and its estimate. The sprint column is headed ",[16,5669,5670],{},"Sprint",", because each row is one sprint. The estimate is the completed estimate for a past sprint and the currently allocated estimate for an active or future sprint. On a time board the estimate appears as a badge. The start and end dates are read only.",[12,5673,5674,5675,5677],{},"Use the checkbox in the header to select every sprint that is currently listed in the tab. Above the table on the right, the search box filters the sprints by name. The ",[16,5676,5657],{}," tab also has a dropdown that chooses how many of the most recent closed sprints to show: 3, 6, or 9. The default is 3. The choice is remembered in this browser tab.",[12,5679,5680,5681,5683],{},"Sprints that are already in the planning session appear checked and cannot be selected again. ",[16,5682,3765],{}," is enabled only when at least one active sprint is selected. Past sprints are optional.",[21,5685,5687],{"id":5686},"read-the-sprints","Read the sprints",[12,5689,5690],{},"The left side shows the combined sprint table. Sprint rows and work item rows share the same columns, so every value lines up vertically:",[61,5692],{"alt":343,"caption":343,"stem":5693},"guide-capacity",[26,5695,5696,5701,5707,5715,5723,5729,5734],{},[29,5697,5698,5700],{},[16,5699,429],{}," shows the sprint icon on a sprint row and the work item type icon on a work item row. The column header uses the work-item icon.",[29,5702,5703,5706],{},[16,5704,5705],{},"Priority"," shows the work item's Jira priority icon in its Jira color. Sprint rows leave it empty. The column header uses the priority-medium icon.",[29,5708,5709,5712,5713,2620],{},[16,5710,5711],{},"Sprint \u002F Work item"," shows the sprint name in bold, which opens the sprint in Jira in a new tab, or the work item key. A sprint goal appears in small text below the sprint name and stays on one line: a goal that is too long is shortened with an ellipsis. Moderators edit the goal in the ",[16,5714,5670],{},[29,5716,5717,5719,5720,5722],{},[16,5718,4310],{}," shows the saved ordinal rank of each work item in its sprint. Current and future sprint rows show a moderator-only customize button instead, and a work item without a rank shows 0. The column appears only when you select ",[16,5721,4310],{}," in the columns dropdown. Everyone sees the saved numbers read only.",[29,5724,5725,5728],{},[16,5726,5727],{},"Status"," shows the sprint state on a sprint row. On a work item row it shows the work item's Jira status until the work item starts. An In Progress work item shows its completion percentage instead. On a story point board moderators edit it. On a time board it is read only and derived from the time spent divided by the original time estimate. A Done work item shows a read-only 100%. To Do work items keep their Jira status.",[29,5730,5731,5733],{},[16,5732,1175],{}," shows values only on sprint rows that have a deviation. Work item rows and sprints without a deviation leave it empty.",[29,5735,5736,5739,5740,5742,5743,5745],{},[16,5737,5738],{},"SP"," on a story point board and ",[16,5741,884],{}," on a time board shows the allocated estimate on a sprint row and the estimate on a work item row. Story point values end with ",[16,5744,1286],{},". Time values are original time estimates shown as work-day durations such as 2 days, 4 hours. A work item with no estimate leaves the cell empty.",[12,5747,930,5748,334,5750,917,5752,5754],{},[16,5749,4310],{},[16,5751,5727],{},[16,5753,1175],{}," columns are centered, and the estimate column is right aligned. These columns take only the width their content needs. Scrumpy reads the estimate through Jira's board estimation, so the value and the timeline appear even when the estimation field is hidden from the work item screen. A work item saved in a sprint plan but hidden from you by Jira issue-level security stays out of the table, the rank list, and the removed list, so the plan never reveals it. Only the sprint row whose radio button is selected is highlighted, and this includes a selected closed sprint. Work item rows are highlighted the same way: only the work item whose radio button is selected is highlighted, and no work item row is highlighted while none is selected. Selecting a work item also selects its parent sprint row, so the team table and the right side follow that sprint.",[12,5756,5757],{},"Moderators see the capacity timeline in the first column and the bulk selection checkboxes in the second column. Non-moderators see the moderator selection column first, with the capacity timeline second. Each active or future sprint row starts the timeline with a hollow circle, each work item row has a circle, and the last work item row in the sprint ends it with a hollow circle. Closed sprints have no timeline, and the table header has no line. The line and circles use the cumulative estimate from the first work item through the current row, with the estimate total and both range bounds rounded to whole story points, or to the nearest hour on a time board: green below the rounded target capacity minus the deviation, yellow inside the rounded range including both ends, and red above the rounded target capacity plus the deviation. The target capacity is the per-member velocity multiplied by the selected team's size and adjusted by its capacity for that sprint.",[12,5759,5760],{},"Active and future sprint rows show their allocated estimate as a colored badge using the same rounded bands. Closed sprint rows show their completed estimate with the completion bands described below.",[12,5762,5763],{},"A current or future sprint row is followed directly by that sprint's work items, so every work item stays grouped under its sprint. A closed sprint row has no work items below it.",[12,5765,5766,5767,2537,5769,5771],{},"When a moderator accepts an estimate in a perspective tab, the ",[16,5768,5738],{},[16,5770,884],{}," value changes right away on the work item row and on its sprint row. Everyone with the tab open sees the new value without reloading. If the accepted work item belongs to a closed sprint, that sprint's totals and the velocity used for the targets are recalculated.",[12,5773,5774,5775,334,5778,5781,5782,5785],{},"Each sprint row shows its state: ",[16,5776,5777],{},"Closed",[16,5779,5780],{},"Current"," for the sprint that is running now, or ",[16,5783,5784],{},"Future",". Select a sprint name to open that sprint in Jira in a new tab. A past sprint opens its sprint report, and the current or a future sprint opens the board backlog.",[12,5787,5788],{},"Use the radio button beside any sprint, including a closed one, to select it. The selected sprint drives the team table. Selecting a work item selects its parent sprint too.",[12,5790,5791,5792,5794],{},"Use the checkbox on a sprint row to select the whole sprint. When at least one sprint is checked, ",[16,5793,4017],{}," asks you to confirm before it removes the sprints, together with their work items, from this capacity plan. Jira is not changed. Their draft plans and team settings stay with the planning session and come back if you add the sprint again. The header checkbox still selects work items only. Bulk selection checkboxes are available to moderators only, and checking a row is never shared with other participants or saved with the planning session.",[12,5796,5797,5798,5800],{},"Non-moderators see a yellow ",[16,5799,1515],{}," badge in that first column instead. It marks the sprint and the work item that the moderator has selected. The badge stays visible whether you follow the moderator or view another sprint or work item locally, so the moderator's place is always clear.",[12,5802,5803,5804,5806,5807,5809,5810,5812,5813,5816,5817,334,5819,917,5821,1603,5823,5825],{},"Above the combined table, the Scrum board selector sits at the top left, while the columns and ",[16,5805,1175],{}," dropdowns sit at the top right. The columns dropdown is available to everyone. It starts with ",[16,5808,1175],{}," selected. Select ",[16,5811,4310],{}," to add the Rank column before Status, select ",[16,5814,5815],{},"Utilization"," to show the Utilization column in the team capacity table, and clear an option to hide its column. A moderator shares the visible columns with everyone who is locked to the moderator. If you pick another selection while you are locked, you detach and keep your own choice in this browser tab. Moderators can change the board and deviation, and non-moderators see the same values read only. The board choice is remembered with the planning session. Selecting another board applies that board and its saved view at once, and the table shows the new board's sprints or its loading state instead of the previous board's rows. Each board keeps its own sprint selection. The board list groups boards under ",[16,5818,1597],{},[16,5820,884],{},[16,5822,1602],{},[16,5824,1602],{}," and are disabled. The sprint table lists the selected sprints by their start date, oldest first.",[12,5827,3822,5828,3825,5830,3828,5832,569],{},[16,5829,1175],{},[16,5831,340],{},[16,5833,5834],{},"Switch to refinement\u002Fgrooming",[12,5836,5837],{},"The velocity is the average completed estimate per team member across the selected closed sprints that have a saved team. On a time board the completed estimate is the original time estimate of the Done work items. Each closed sprint contributes its completed estimate divided by its effective team size: two people at 50% count as one person, and a 2-person team that completed 10 points contributes 5 points per member. The per-member values are then averaged, so a sprint with a bigger team does not outweigh a sprint with a smaller team. A closed sprint with no saved team shows 0% in the Team column and does not count towards the velocity until you populate its team. Adjusting a closed sprint's team size or team capacity changes its contribution and the velocity. The table updates the closed sprint's Team value, the velocity, and every future target as soon as you change a team member's capacity or membership, before the save finishes. If the save fails, the previous values return. The target for an active or future sprint is the per-member velocity multiplied by that sprint's effective team size, which is its headcount adjusted by utilization and time off. For example, 10 points with 2 people and 15 points with 4 people average 4.375 points per member, so a sprint with 3 people at full capacity targets 13.125 points. The timeline and the allocated estimate badges compare the planned estimate with that target, not with the velocity.",[12,5839,930,5840,5842],{},[16,5841,1175],{}," column shows only a signed estimate badge, rounded to whole story points, or to the nearest hour on a time board. For a closed sprint, the value is the difference between completed and allocated estimate: negative when less was completed and positive when more was completed. For an active or future sprint, it compares the target capacity with the remaining estimate after completion instead: positive when the remaining estimate is below the target and negative when it is above it. The percentage is not displayed.",[12,5844,5845,5846,5739,5848,5850,5851,5853],{},"The estimate column is ",[16,5847,5738],{},[16,5849,884],{}," on a time board. It shows the completed estimate on a closed sprint row, the allocated estimate on an active or future sprint row, and the estimate of the work item on a work item row. Story point values end with ",[16,5852,1286],{},". Time values are original time estimates shown as work-day durations such as 2 days, 4 hours. Work item estimates use the same green, yellow, and red bands as the timeline, calculated from the rounded cumulative remaining estimate through that row. Active and future sprint badges use the same rounded target bands from the remaining estimate: green below the range, yellow inside it, and red above it. Closed sprint badges compare the rounded completed estimate with the rounded allocation range: red below it, yellow inside it up to but not including the upper bound, and green at or above the upper bound. All three uses derive their lower and upper bounds from the same rounded healthy-range calculation. Active and future sprint rows show only that one estimate badge in the column.",[12,5855,5856,5857,5859,5860,5862],{},"For an active or future sprint, an In Progress work item shows its completion percentage in the ",[16,5858,5727],{}," column. On a story point board moderators can change it and everyone else sees it read only. On a time board it is always read only and derived from the time spent divided by the original time estimate. The derived value is rounded to a whole percent and stays between 0 and 100, so time spent above the original estimate counts as 100% and a missing original estimate counts as 0%. A Done work item shows a read-only 100%. To Do work items have no completion field. On a story point board the percentage is saved with the planning session and is never written to Jira. The remaining estimate is the item estimate reduced by its completion, so 2 sp at 50% counts as 1 sp, and on a time board 2 days at 50% counts as 1 day. A Done item counts as 0 remaining. The estimate column still shows the original allocated estimate on sprint and work item rows, while the ",[16,5861,1175],{}," and timeline use the remaining estimate. Manual completion does not change the velocity.",[12,5864,930,5865,5867],{},[16,5866,2942],{}," column after the estimate column shows the team capacity percentage used for the sprint. Active and future sprints, and closed sprints with team members, show the capacity calculated from those members' working time and utilization. The value is read only. A closed sprint with no saved team shows 0% and does not count towards the velocity, and a saved team with no effective capacity also shows 0%. Work item rows leave the Team cell empty.",[12,5869,5870,5871,5873],{},"Use the ",[16,5872,1175],{}," dropdown to allow 0%, 5%, 10%, 15%, 20%, or 25% deviation from the target. The deviation badge uses the regular style when the absolute deviation percentage is within that tolerance. Above the tolerance, a positive deviation is green and a negative deviation is red. The chosen deviation is saved with the planning session's capacity data.",[12,5875,5876,5877,5881,5882,5885,5886,5889,5890,5893],{},"Below the table, a right-aligned summary reads \"Team is at ",[5878,5879,5880],"span",{},"capacity"," capacity and velocity of ",[5878,5883,5884],{},"velocity",", aiming to complete ",[5878,5887,5888],{},"target"," at healthy range of ",[5878,5891,5892],{},"range","\", with the capacity and velocity shown as information badges. The capacity is the selected team's capacity percentage rounded to a whole number, and the velocity is the per-member velocity multiplied by the selected sprint's team size, so it is the full-capacity velocity of that team. The target appears as an information badge with the target capacity rounded to whole story points, or to the nearest hour on a time board. The healthy range uses two information badges, one for the lower bound and one for the upper bound, separated by a dash. Both bounds are the same rounded values used by the timeline and the estimate badges. For example, a 10% deviation around 20.4 sp shows 18 sp - 22 sp, and around 2 days, 4 hours shows 2 days, 2 hours - 2 days, 6 hours. When both ends round to the same value, a single badge shows that value.",[21,5895,5897],{"id":5896},"work-items-and-drag-and-drop","Work items and drag and drop",[12,5899,5900,5901,5903],{},"The work item rows below a sprint use the same columns as the sprint rows. The ",[16,5902,5727],{}," column shows the work item's own Jira status.",[26,5905,5906,5909,5915,5918,5921],{},[29,5907,5908],{},"Use the radio button on a work item to select it. The selection is remembered with the planning session. Its parent sprint row is selected with it.",[29,5910,5911,5912,5914],{},"Use the checkboxes to select work items for ",[16,5913,4017],{},". The header checkbox selects every work item in the table, across every sprint.",[29,5916,5917],{},"Use the checkbox on a sprint row to remove that sprint from the planning session, as described above. Sprint checkboxes are separate from the work item header checkbox.",[29,5919,5920],{},"Drag a work item to reorder it inside its sprint, or drag it onto another sprint row to move it into that sprint.",[29,5922,5923],{},"Closed sprints are history only, so they have no work items to drag.",[12,5925,5926],{},"The selection controls store their choice with the selected board's view. Only moderators can change the shared selections. The selected sprint, work item, team member, and right-side tab are remembered with the board view.",[12,5928,5929,5930,5932,5933,334,5935,334,5937,917,5939,5941],{},"Non-moderators see a ",[16,5931,2366],{}," checkbox below the table. It is checked by default, so your view follows the moderator's sprint, work item, team member, visible columns, and right-side tab. It follows the moderator between ",[16,5934,340],{},[16,5936,343],{},[16,5938,346],{},[16,5940,349],{}," for the same planning session. It applies to the planning tab you are on: switching to another planning tab yourself clears it, so you start detached on the new tab. Clear the checkbox to stay on the current view, then choose a sprint, work item, team member, column selection, or tab to look at without changing what anyone else sees. Choosing one clears the lock automatically. Select the checkbox again to return to the moderator's view. The lock is remembered in this browser tab while you stay on the tab. Your local choices stay with the tab where you made them, and they never change what the moderator or other participants see.",[21,5943,5945],{"id":5944},"rank-the-work-items","Rank the work items",[12,5947,5948,5949,5951],{},"Select ",[16,5950,4310],{}," in the columns dropdown to show the Rank column. The column sits before Status and uses only the width its numbers need. A work item without a rank shows 0. Each planning session you open loads its capacity data. Switching to another planning session loads it once, and returning to one you already opened shows its data right away.",[12,5953,5954],{},"On every current or future sprint row, moderators see a customize button in the Rank cell. Select it to open the ranking dialog for that sprint. Closed sprint rows and the view that non-moderators see have no button.",[12,5956,5957],{},"The dialog explains that it sets the order of the sprint's work items from the selected ranking. Choose a ranking:",[26,5959,5960,5966,5972,5977],{},[29,5961,5962,5965],{},[16,5963,5964],{},"Board rank"," uses the work item's position in the Jira sprint order.",[29,5967,5968,5971],{},[16,5969,5970],{},"Votes"," uses the number of Jira votes on the work item.",[29,5973,5974,5976],{},[16,5975,2694],{}," uses the selected perspective's affinity ranking from the planning session.",[29,5978,5979,5981],{},[16,5980,2700],{}," uses the selected perspective's dot ranking from the planning session.",[12,5983,5984],{},"A ranking that has no values for the sprint is shown in the dropdown but cannot be selected. This happens when Jira returns no board rank or vote counts, or when the selected perspective has no affinity or dot ranking yet. Nothing in the dialog warns you about it: choose another ranking, or add the missing data in the planning session. When you change the perspective, the ranking falls back to the first option that has values if the current one does not.",[12,5986,1342,5987,2537,5990,5993],{},[16,5988,5989],{},"Ascending",[16,5991,5992],{},"Descending"," for the sort order. For Affinity rank and Dot rank, a Perspective dropdown appears beside the other two so you can choose which perspective's ranking to use. The Default perspective is selected first.",[12,5995,5996],{},"Below the dropdowns, a preview table lists the work items in their new order. It shows the work item type icon, the work item key, and the Rank number in a neutral badge. The Type column header uses the work-item icon. The Rank column uses 10 percent of the preview width, and the Rank header and its cells are right aligned. Rank numbers are bound to the work items, not to their row position. Each source has a natural order: lower Board rank and lower Affinity position are better, while higher Votes and higher Dot counts are better. Ordinal numbers are assigned once in that order, so changing between Ascending and Descending reverses both the rows and the displayed numbers. For Dot rank, Ascending shows the most-dotted work item first, and Descending reverses the whole list, including the work items with 0 dots. With Votes, the Rank cell shows the work item's vote count, including 0, instead of an ordinal position. With Dot rank, a work item with no dots shows 0. A work item with no value for the selected ranking shows 0 and follows the ranked work items. Apply saves a number for every work item in the sprint.",[12,5998,5948,5999,6001],{},[16,6000,3592],{}," to save the new order and the rank numbers for the sprint. The dialog closes and the Rank column shows the numbers. If the save fails, the dialog stays open with an error message, and the previous order stays in place.",[12,6003,6004],{},"Non-moderators see the saved rank numbers read only. Dragging a work item, adding work items, or removing work items keeps the saved numbers attached to the work items. A work item moved to another sprint or removed from the plan loses its number, and a moved or newly added work item shows 0 until you apply a ranking again. Applying the capacity plan to Jira keeps the rank numbers.",[21,6006,6008],{"id":6007},"plan-the-team","Plan the team",[12,6010,6011,6012,334,6015,6017,6018,6020,6021,6023,6024,6026,6027,6029,6030,6032,6033,6035,6036,430,6038,6040,6041,6043],{},"The right side has ",[16,6013,6014],{},"Team capacity",[16,6016,5670],{},", a tab for each perspective that estimates with the same board you selected, and ",[16,6019,1877],{},". The perspective tabs appear only when a work item is selected in the combined table. Their titles stay on one line and are not shortened with an ellipsis. The selected tab is shared with the planning session, so participants who are locked to the moderator follow the moderator's tab. Choosing another tab while locked keeps that tab for you only and clears the lock. A yellow ",[16,6022,1515],{}," badge marks the tab the moderator is viewing. Every non-moderator sees it, whether or not ",[16,6025,2366],{}," is checked, and it stays on the moderator's tab while you look at another tab locally. ",[16,6028,6014],{}," shows the team for the selected sprint. ",[16,6031,5670],{}," shows the selected active or future sprint's Jira fields. Each perspective tab shows the voting panel for the selected work item. The ",[16,6034,1877],{}," tab at the right end of the tab bar always shows the full session conversation: every message sent from the planning session, plus messages sent from outside the session for the work items in the capacity plan, ordered by publish time. Selecting a work item, selecting no work item, or selecting a closed sprint does not change the conversation. A selected work item only chooses where a new message is sent: the work item chat. With no selection or a closed sprint, a new message goes to the planning session chat. Every work item message keeps its work item key link, in every chat panel. Your own messages sit on the right side of the conversation, and messages from other participants sit on the left. When you select a closed sprint, only ",[16,6037,6014],{},[16,6039,1877],{}," stay visible, and the ",[16,6042,5670],{}," and perspective tabs are hidden. Your role badge and the sound bell always sit at the right end of the tab bar. The badge opens the Permissions settings, and the bell turns sound notifications on or off. When an active or future sprint has no stored team, Scrumpy fills its team from the people assigned to that sprint's work items while those items were In Progress, then stores it for that sprint. A moderator who selects a past sprint with no team is asked first because reading its history can take a while; a non-moderator sees the empty team read only. Cancel selects the sprint without populating its team. If you accept, the dialog stays open with a spinner and a message to wait until population finishes. If nobody was assigned while an item was In Progress, the team stays empty, and selecting the sprint again offers to populate it again. After that, moderators manage the list from the bulk action bar below the table. New assignees are not added automatically once a team is stored. Each sprint keeps its own team list.",[12,6045,6046,6047,6049],{},"The team table follows the sprint selected in the combined table. The checkboxes select team members for the bulk actions. The checkbox in the table header selects everyone at once. The member checkboxes are available to moderators only, are used only for the bulk actions, and are never shared with other participants. Non-moderators see a narrow first column with no header that shows a yellow ",[16,6048,1515],{}," badge on the team member whose calendar the moderator has open. The badge stays on that member while you open another member's calendar yourself.",[12,6051,6052],{},"A moderator can change every team member's utilization and working hours. A team member can change their own utilization and working hours for a sprint where they are on the team. This also works for a closed sprint that has a recorded team, so you can correct the team size and team capacity used for the velocity. If the closed sprint has no team yet, you can add members and set their capacity; the sprint starts counting towards the velocity as soon as it has a saved team. Adding or removing a team member updates the team table and every calculated value right away, before the save finishes. If the save fails, the previous team and values return. You can open any team member's calendar. A calendar you cannot change opens read only, and its hours of work and utilization are shown as disabled fields, so the values line up with the editable view.",[12,6054,6055],{},"For each team member:",[26,6057,6058,6061,6064,6073,6081,6084,6087],{},[29,6059,6060],{},"Change the overall utilization percentage to show part-time availability. The default is 100%.",[29,6062,6063],{},"Select the radio button next to the team member to open their calendar, then select the days they cannot work a full day. Select a highlighted day again to remove it. The calendar only shows dates inside the selected sprint, and it opens on the month of the sprint start date instead of the current month. The weekend days chosen in the space's Working week settings are disabled and do not count as working days.",[29,6065,930,6066,6069,6070,6072],{},[16,6067,6068],{},"Hours of work"," column shows the hours the team member can work out of the sprint's total working hours, for example 72h out of 80h. Both values appear as badges. When the calendar is open, each marked day shows a small cross-circle button, its date in a read-only date picker, and an hours field next to it. The hours field accepts 0 to the ",[16,6071,860],{}," set in the space's Working week settings (13h by default). A newly marked day starts at 0 hours. Select the cross-circle button to remove that day from the team member's calendar.",[29,6074,930,6075,6077,6078,6080],{},[16,6076,5815],{}," column shows the overall utilization. When the calendar is open, a utilization field for every marked day sits next to it. A day with no hours of work keeps its utilization field disabled, because that day adds no capacity. The reverse also holds: a day at 0% utilization keeps its hours of work field disabled, because those hours would be multiplied by zero. When both values are 0, the hours field stays editable so the day can be corrected. The column is hidden until you select ",[16,6079,5815],{}," in the columns dropdown, and hiding it also hides the per-day utilization fields of an open calendar.",[29,6082,6083],{},"A marked day starts at 0h. Raise the hours for a partial day, for example 6h. Days you do not mark count as a full working day at 100%, using the work hours from the space's working week settings (8h by default).",[29,6085,6086],{},"A marked day can also be longer than the regular work hours, for example 10h when the work hours are 8h. The extra hours raise that team member's total available hours above the sprint's regular total, for example 44h out of 40h, and increase their share of the team capacity and every target that uses it.",[29,6088,6089],{},"The overall utilization applies on top of each day. With 90% overall utilization, a day with 6h at 60% counts as 3.24h of a normal working day.",[12,6091,6092],{},"Below the team table, moderators see a small note on the right. It explains that to record time off or another deviation from the regular working hours per day, you open the team member's calendar and then select a date during the sprint. It also explains that the team member's sprint utilization is applied on top of each exception day's utilization.",[12,6094,6095,6096,6099,6100,6102,6103,6105],{},"Below the table, moderators see the team bulk action bar. Select ",[16,6097,6098],{},"Add team members"," to open a dialog, choose one or more people, and select ",[16,6101,3765],{},". The selected people join the team for the selected planned sprint and start with 100% utilization and full working hours. To remove team members, check them in the table and select ",[16,6104,4017],{},". If any selected team member has time off records in that sprint, a confirmation dialog explains that their time off records will be lost. Confirm the removal to continue; if there are no time off records, the members are removed immediately. Removing a team member deletes their saved utilization and time off for that sprint only. Other planned sprints keep their own team lists. Only moderators can add or remove team members.",[12,6107,6108,6109,6112],{},"To clear time off in that sprint, check the members and select ",[16,6110,6111],{},"Clear time off",". A confirmation dialog explains that their time off (Hours of work) entries will be deleted and their utilization reset to 100%. Confirm to continue. Each selected member returns to the regular working hours and full utilization. The clear control stays disabled when no selected member has something to clear.",[12,6114,6115],{},"The selected team member is remembered with the board view. The target updates as you change these values. The leftover value is negative when less was completed than was allocated and positive when more was completed. The leftover badges use the regular style when the absolute leftover percentage is at or below the deviation. Above the deviation, positive is green and negative is red.",[21,6117,6119],{"id":6118},"the-selected-sprint","The selected sprint",[12,6121,930,6122,6124],{},[16,6123,5670],{}," tab edits the sprint selected in the combined table. It is available for active and future sprints only. When a closed sprint is selected, the tab is hidden.",[26,6126,6127,6144,6150],{},[29,6128,6129,334,6132,334,6135,917,6138,6141,6142,569],{},[16,6130,6131],{},"Sprint name",[16,6133,6134],{},"Sprint goal",[16,6136,6137],{},"Start date",[16,6139,6140],{},"End date"," are kept in the plan as you edit them. The table shows the new name right away and recalculates the sprint target and team day range from the new dates. Jira is not changed until you select ",[16,6143,3592],{},[29,6145,6146,6147,6149],{},"Below the ",[16,6148,6134],{}," field, a square thumbs up button and a square thumbs down button let voters agree or disagree with the text. The number of votes appears beside each button. A voter can vote, select a button again to remove the vote, and the counts update for everyone. Guests see the counts but cannot vote. Votes reset when the goal text changes.",[29,6151,6152,6153,6156],{},"Sprint state changes happen in Jira, not in this tab. To start or complete a sprint, use the Jira backlog or the active sprints page, then select ",[16,6154,6155],{},"Refresh"," in the capacity toolbar to reload the plan. A started sprint shows as the current sprint, and a completed sprint leaves the plan.",[12,6158,6159],{},"Moderators can edit these fields. Non-moderators see the same values read only.",[21,6161,6163],{"id":6162},"vote-on-work-items-from-capacity-planning","Vote on work items from capacity planning",[12,6165,6166],{},"A perspective appears as a tab in the team section when its estimation target is the board and its estimation board is the same board you selected above the combined table. A perspective that writes estimates to Jira fields instead, or estimates with another board, does not appear.",[12,6168,6169,6170,6172,6173,334,6175,917,6177,6179,6180,6182],{},"Select a work item in the combined table, then open its perspective tab to vote. The perspective tabs appear only after a work item is selected. The tab shows the same voting panel as the Refinement\u002Fgrooming tab: the perspective header, the voting cards, the participant list, the session controls, and the final result with ",[16,6171,509],{},". While a session runs, the ",[16,6174,2303],{},[16,6176,1462],{},[16,6178,2040],{}," sub-tabs stay inside the perspective tab. The ",[16,6181,2040],{}," sub-tab shows the summary and description of the selected work item, and moderators can edit both there. An edit saves when you click away, switch to another sub-tab, or close the panel, even if the short description pause has not finished. If no work item is selected, the perspective tabs are hidden. When you select a closed sprint, the perspective tabs are hidden.",[12,6184,6185,6186,6188],{},"The summary you edit in the voting panel's ",[16,6187,2040],{}," sub-tab also updates the work item tooltip in the combined table.",[21,6190,6192],{"id":6191},"the-capacity-toolbar","The capacity toolbar",[12,6194,6195,6196,6198,6199,6201,6202,430,6204,6206,6207,6209,6210,430,6212,6214,6215,6217],{},"Below the table, moderators see the same style of toolbar as the Refinement\u002Fgrooming tab. The board selector sits above the top left corner of the combined table, while the ",[16,6197,1175],{}," dropdown and the columns control sit above the top right corner. ",[16,6200,3592],{}," uses the warning colour. ",[16,6203,3559],{},[16,6205,3562],{}," sit in the row above the session tabs, beside ",[16,6208,568],{},", and they appear only while a session is open. ",[16,6211,5259],{},[16,6213,3592],{}," follow ",[16,6216,6155],{}," in the toolbar with a gap; they do not sit at the right edge:",[26,6219,6220,6228,6241,6246,6251,6256,6261,6266],{},[29,6221,6222,6224,6225,6227],{},[16,6223,3559],{},", beside ",[16,6226,568],{},", changes the planning session title, description, and dates. The new title and description appear on the tab, in the planning header, and in the progress bar right away, and they return to the saved values if the save fails. A message then tells you that the planning session could not be saved.",[29,6229,6230,6232,6233,6235,6236,3702,6238,6240],{},[16,6231,3695],{}," adds work items from a saved Jira filter, a sprint, a Refinement\u002Fgrooming planning session, or a retrospective to the selected sprint plan. The picker starts with a ",[16,6234,340],{}," group that lists the planning sessions with work items; selecting one previews that session's work items. A ",[16,6237,349],{},[16,6239,349],{}," group is hidden when no action item is linked to a work item. It only offers work items from the current space that are not already in the selected sprint plan. To start over, clear the picker: the chosen source is dropped, the search box empties, and the first 100 shared filters return.",[29,6242,6243,6245],{},[16,6244,399],{}," opens the sprint picker described above.",[29,6247,6248,6250],{},[16,6249,4017],{}," removes the checked work items from the selected sprint plan, or the checked sprints from the planning session after you confirm. It does not change Jira immediately.",[29,6252,6253,6255],{},[16,6254,6155],{}," reads the sprints and work items from Jira again, including their priorities, summaries, and descriptions. It does not change the plan or Jira.",[29,6257,6258,6260],{},[16,6259,5259],{}," creates a Confluence page for the sprint currently selected in the combined table. It is available only when a Confluence space is configured, and it is disabled when a past sprint is selected. The page records the planning session window and duration, the selected sprint and goal, the goal votes, the capacity decision, the velocity summary, the team's hours of work, and the ordered work items with their estimates.",[29,6262,6263,6265],{},[16,6264,3592],{}," updates Jira with the plan and the sprint name, goal, and dates you changed.",[29,6267,6268,6224,6270,6272],{},[16,6269,3562],{},[16,6271,3559],{}," above the tabs, closes the planning session. It asks for confirmation, then permanently removes the planning session with its capacity data, votes, notes, action items, standup, and chat.",[12,6274,6275,6276,6278],{},"The planning session progress bar appears below the toolbar. Non-moderators see the ",[16,6277,2366],{}," checkbox in the space where the toolbar appears.",[21,6280,6282],{"id":6281},"sprint-goals","Sprint goals",[12,6284,6285,6286,6288,6289,6291],{},"Every sprint goal appears in small text below the sprint name in the table and stays on one line, and a goal that does not fit is shortened with an ellipsis. A sprint without a goal keeps an empty goal line in the table, so the sprint rows and the timeline stay aligned. Moderators edit an active or future sprint goal in the ",[16,6287,5670],{}," tab. The goal under the sprint name follows your typing before the draft is saved, and the goal votes reset to 0 as soon as the text changes. The vote buttons stay read only until the goal draft is saved, because the votes always describe the saved goal. A goal change appears for everyone without a reload and reaches Jira when you select ",[16,6290,3592],{},". A closed sprint goal is read only. If a goal in Jira contains line breaks, the table shows them as spaces.",[12,6293,6294,6295,6297],{},"The sprint name and dates you change in the ",[16,6296,5670],{}," tab also appear in the combined table, the team calendar, and the target as you change them, before the draft is saved. The date fields stay editable while a change is saved, so you can set the start and end dates without waiting, and an older save never rewinds a newer date you picked. A failed save restores the saved name, goal, and dates.",[21,6299,6301],{"id":6300},"move-work-into-the-selected-sprint","Move work into the selected sprint",[12,6303,6304,6305,6307,6308,569],{},"Work items are planned per sprint. Use ",[16,6306,3695],{}," to add a work item from a filter, a sprint, a Refinement\u002Fgrooming session, or a retrospective to the selected sprint, drag a work item onto another sprint row to move it into that sprint, or drag within a sprint to reorder its items. The order and sprint membership are saved as a draft. They do not change Jira until you select ",[16,6309,3592],{},[21,6311,6313],{"id":6312},"apply-the-plan","Apply the plan",[12,6315,5948,6316,6318,6319,6321],{},[16,6317,3592],{}," after ",[16,6320,6155],{}," in the toolbar and confirm the change in the dialog. Scrumpy then:",[26,6323,6324,6327,6330,6333,6336,6339],{},[29,6325,6326],{},"Saves the sprint names, goals, and start and end dates you changed.",[29,6328,6329],{},"Moves the planned work items into the selected sprints.",[29,6331,6332],{},"Updates their order inside each sprint using the board's rank field.",[29,6334,6335],{},"Moves work items you removed from a sprint plan to the backlog, but only when they are currently in that sprint. Work items that are in another sprint or already in the backlog stay where they are.",[29,6337,6338],{},"Leaves closed sprints and their estimates unchanged.",[29,6340,6341],{},"Saves a team capacity snapshot for every selected sprint that has a team. The snapshot holds the team members, their working hours, and their utilization, is kept for 12 months, and is not tied to this planning session.",[12,6343,6344],{},"When the update finishes, the page reloads the current Jira data. If Jira refuses part of the change, the page tells you that some sprints could not be updated and keeps the draft so you can try again. A sprint name, goal, or date you have not applied yet is part of the plan, so it also appears in the combined table and in an archive page.",[21,6346,6348],{"id":6347},"archive-the-capacity-plan","Archive the capacity plan",[12,6350,6351],{},"You can save a sprint's capacity plan as a Confluence page, so the team keeps a record of what was planned and why. Only a moderator can archive, and the action is available only after a Confluence space has been configured for the space.",[66,6353,6354,6360,6365,6368],{},[29,6355,6356,6357,6359],{},"Select an active or future sprint in the combined table. ",[16,6358,5259],{}," is disabled for a closed sprint, because a closed sprint is history only.",[29,6361,5948,6362,6364],{},[16,6363,5259],{}," in the capacity toolbar.",[29,6366,6367],{},"Review the preview. It shows the sprint and its dates, the sprint goal, the up and down votes, the capacity decision, and the velocity summary. The team and work item tables are written to the Confluence page but are not shown in the dialog.",[29,6369,5948,6370,6372,6373,6375],{},[16,6371,5259],{}," to create the page, or ",[16,6374,5337],{}," to leave the capacity plan unchanged.",[12,6377,6378,6379,6381],{},"While the preview loads, ",[16,6380,5259],{}," stays disabled. If the preview cannot load, the dialog explains why, and you can close it and try again. When the page is ready, the dialog shows a link to it. If Confluence refuses the page, the dialog shows the reason and your capacity plan is not changed.",[12,6383,6384,6385,6387,6388,6390,6391,6393],{},"The page is written under the ",[16,6386,5462],{}," parent page in the configured Confluence space, in a child page named ",[604,6389,5525],{},". Planning-session archives stay under the separate ",[16,6392,250],{}," parent, so the two kinds of page never overwrite each other. The page title starts with the planning session title, then the sprint name, and the planning start time with the timezone.",[12,6395,6396],{},"The page contains:",[26,6398,6399,6402,6405,6408,6411,6414,6417,6420],{},[29,6400,6401],{},"The planning session title, description, start and end time, and timezone, in the same header as the planning archive page",[29,6403,6404],{},"The planning session duration, as a plain line below that header",[29,6406,6407],{},"The selected sprint name, state, dates, and goal",[29,6409,6410],{},"The up and down votes for the goal",[29,6412,6413],{},"A decision line for the target capacity range",[29,6415,6416],{},"The velocity summary: velocity per member, team velocity, team size, effective team size, team capacity, target capacity, healthy range, planned estimate, remaining estimate, and deviation from target",[29,6418,6419],{},"Every team member in the selected sprint, with their utilization and their hours of work out of the sprint working hours",[29,6421,6422],{},"The work items in their saved order, with their status and estimate",[12,6424,6425],{},"The header is the same one the planning archive page uses: the planning title and 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, and the timezone the dates are valid in. The planning duration follows the header as a plain line. The sprint goal and its up and down votes appear centered directly below the sprint name. The team and work item tables use a wider layout, and the Work item column leaves room for a longer summary.",[12,6427,6428],{},"The page shows the capacity plan as it currently appears, including draft changes that you have not applied to Jira yet. On a story point board the values use story points, and on a time board they use work-day durations. Re-archiving the same sprint updates the existing page instead of creating a duplicate.",[21,6430,6432],{"id":6431},"notes","Notes",[26,6434,6435,6438,6444,6447,6453,6456,6459],{},[29,6436,6437],{},"Velocity uses the current completion state of the work items in the closed sprints. A work item that was reopened after its sprint closed counts as not completed. Manual completion percentages on active or future work items do not change the velocity.",[29,6439,6440,6441,6443],{},"The manual completion percentage is saved with the planning session and never written to Jira. ",[16,6442,3592],{}," keeps it. On a time board the percentage is not manual: it is recalculated from the current time spent and original time estimate each time the plan loads or refreshes.",[29,6445,6446],{},"Working days exclude Saturdays and Sundays unless you change the weekend days in the space's Working week settings. Mark public holidays as 0h days for each team member.",[29,6448,6449,6450,6452],{},"Velocity uses the saved team size and team capacity of the selected closed sprints. If you select no closed sprints, or none of them has a saved team, the velocity is zero. Before asking you to populate a past sprint that has no saved team, Scrumpy loads the most recent team capacity snapshot from an earlier Apply when one is still available. A past sprint with no saved team and no snapshot shows 0% and does not count. Select it to open its ",[16,6451,6014],{}," tab, populate its team, and then correct its size and capacity. A team member who never had a work item In Progress in a sprint does not appear in that sprint's team list.",[29,6454,6455],{},"Removing a sprint from the capacity plan does not delete its saved draft work item order or team settings. Those come back if you add the sprint to the planning session again.",[29,6457,6458],{},"Each planning session has its own capacity data. Switching planning tabs does not change another planning session.",[29,6460,6461],{},"A non-moderator can edit only their own utilization and time off, and only for a sprint where they are on the team. The change is saved for everyone who views that sprint.",[12,6463,6464],{},"Capacity planning data is kept for 90 days after the last change, matching the planning session. Older capacity data is removed automatically. Team capacity snapshots are separate records kept for 12 months after the last Apply that refreshed them.",{"title":153,"searchDepth":154,"depth":154,"links":6466},[6467,6468,6469,6470,6471,6472,6473,6474,6475,6476,6477,6478,6479],{"id":5634,"depth":154,"text":5635},{"id":5686,"depth":154,"text":5687},{"id":5896,"depth":154,"text":5897},{"id":5944,"depth":154,"text":5945},{"id":6007,"depth":154,"text":6008},{"id":6118,"depth":154,"text":6119},{"id":6162,"depth":154,"text":6163},{"id":6191,"depth":154,"text":6192},{"id":6281,"depth":154,"text":6282},{"id":6300,"depth":154,"text":6301},{"id":6312,"depth":154,"text":6313},{"id":6347,"depth":154,"text":6348},{"id":6431,"depth":154,"text":6432},"2026-11-08","Plan sprint capacity from recent velocity, drag work into sprints and let the team vote on what fits.","\u002Fog\u002Fguide-capacity-planning.jpg",[6484,6485,5884,6486],"capacity planning","sprint capacity","agile planning",{},13,"\u002Fgetting-started\u002Fcapacity-planning",{"title":5571,"description":6481},{"loc":6489,"lastmod":802},"guide\u002Fen\u002Fcapacity-planning","guide\u002Fcapacity-planning","o18flU9NCXI_8Fri7sepAw5oIlAYzvcI-Fp5yw9pXO0",{"id":6496,"title":6497,"body":6498,"dateModified":802,"datePublished":7092,"description":7093,"extension":162,"heading":7094,"image":7095,"imageAlt":7094,"keywords":7096,"locale":168,"meta":7100,"navigation":170,"order":7101,"path":7102,"section":173,"seo":7103,"sitemap":7104,"slug":7105,"stem":7106,"translationKey":7107,"__hash__":7108},"guide\u002Fguide\u002Fen\u002Fsprint-retrospectives.md","Sprint retrospectives | Scrumpy Planning Poker",{"type":9,"value":6499,"toc":7076},[6500,6505,6510,6514,6537,6541,6567,6571,6574,6627,6630,6636,6640,6651,6654,6658,6672,6677,6681,6684,6694,6697,6728,6731,6734,6747,6751,6760,6772,6775,6784,6787,6793,6797,6807,6831,6840,6849,6852,6865,6868,6872,6875,6904,6907,6911,6920,6937,6940,6943,6946,6949,6953,6962,6971,6975,6978,6987,6999,7016,7019,7023,7035,7060,7064,7067,7070,7073],[12,6501,930,6502,6504],{},[16,6503,349],{}," tab runs a retrospective for a sprint, for a board without sprints, or for the space when it has no board, inside a planning session. You and the other participants add notes to three columns, like the notes you agree with, group related notes, and turn notes into action items. The notes stay face down during Feedback, which is the first stage, and are revealed in the Vote stage, except your own notes, which only you can see.",[12,6506,6507],{},[16,6508,6509],{},"The retrospective is virtual: notes, groups, stages, and the timer stay in Scrumpy. Jira changes only when you select Apply, which creates or updates the Jira work items for your action items.",[21,6511,6513],{"id":6512},"before-you-start","Before you start",[26,6515,6516,6519,6531,6534],{},[29,6517,6518],{},"The space does not need a board. A Scrum board with sprints, a Kanban board, or a Scrum board without sprints works too. With no board at all, the retrospective saves its notes, timer, action items, and type for the planning session itself.",[29,6520,6521,6522,5256,6524,5256,6526,6528,6529,2620],{},"A planning session must exist. Create one from the ",[16,6523,340],{},[16,6525,343],{},[16,6527,346],{}," tab, or the ",[16,6530,349],{},[29,6532,6533],{},"Each sprint of a board, each board without sprints, and a planning session without a board has its own retrospective: its own notes, timer, action items, stage, and type. A change in one never reaches another.",[29,6535,6536],{},"Moderators choose the shared board, retrospective type, and sprint when the board has one. Locked participants follow that selection.",[21,6538,6540],{"id":6539},"choose-the-board-and-sprint","Choose the board and sprint",[66,6542,6543,6548,6551,6558,6564],{},[29,6544,6545,6546,2620],{},"Open the ",[16,6547,349],{},[29,6549,6550],{},"Pick a planning session from the tabs above the retrospective board. When the session you last opened is no longer available, the first planning session opens instead.",[29,6552,6553,6554,6557],{},"Pick a ",[16,6555,6556],{},"board"," in the top left corner.",[29,6559,6553,6560,6563],{},[16,6561,6562],{},"sprint"," next to the board. The list shows the six most recently started sprints of that board. A sprint that has not started yet is not listed. If the board has no started sprint, the sprint selector is hidden and the retrospective works for the board. A voter or guest can pick another sprint locally; that detaches the viewer from the moderator. Every sprint opens its own retrospective.",[29,6565,6566],{},"The sprint name appears in the center, with its goal underneath. Use the link icon next to the goal to open the sprint in the Jira backlog in a new browser tab. A board without sprints hides the sprint name, the goal, and the link. A space without a board shows an empty disabled board selector and hides the sprint selector, and the retrospective works for the planning session.",[21,6568,6570],{"id":6569},"choose-the-retrospective-type","Choose the retrospective type",[12,6572,6573],{},"Use the dropdown in the top right corner. The three columns change with the type:",[614,6575,6576,6585],{},[617,6577,6578],{},[620,6579,6580,6582],{},[623,6581,429],{},[623,6583,6584],{},"Columns",[633,6586,6587,6595,6603,6611,6619],{},[620,6588,6589,6592],{},[638,6590,6591],{},"The good \u002F The bad \u002F The ugly",[638,6593,6594],{},"The good, The bad, The ugly",[620,6596,6597,6600],{},[638,6598,6599],{},"Start \u002F Stop \u002F Continue",[638,6601,6602],{},"Start, Stop, Continue",[620,6604,6605,6608],{},[638,6606,6607],{},"Mad \u002F Glad \u002F Sad",[638,6609,6610],{},"Mad, Glad, Sad",[620,6612,6613,6616],{},[638,6614,6615],{},"Sunny skies \u002F Hot air \u002F Storm clouds",[638,6617,6618],{},"Sunny skies, Hot air, Storm clouds",[620,6620,6621,6624],{},[638,6622,6623],{},"What worked well? \u002F What didn't go well? \u002F What should we try next?",[638,6625,6626],{},"The three questions",[12,6628,6629],{},"Switching the type only changes the column names. The notes stay in their columns. The new column names appear right away, and you can keep adding notes and using the actions while the change saves. If the change cannot be saved, the previous type returns.",[12,6631,6632,6633,6635],{},"The type belongs to the retrospective you are looking at. Each sprint keeps its own type, and so does a board without sprints and a planning session without a board. Switching the sprint or the board shows that retrospective's own type, or the default ",[16,6634,6591],{}," when it never had one. Changing the type on one sprint never changes another sprint's columns.",[21,6637,6639],{"id":6638},"add-a-note","Add a note",[66,6641,6642,6645,6648],{},[29,6643,6644],{},"Find the column you want. Its name sits above the retrospective board, centered over the lane.",[29,6646,6647],{},"Select the add button with the plus icon under the column name.",[29,6649,6650],{},"An empty note appears in the column and its editor is ready. Type your note.",[12,6652,6653],{},"Your own notes are always visible to you, even during Feedback. Notes from other participants stay hidden during Feedback and are revealed in the Vote stage. The note sits in the retrospective board as a sticky card with the same layout as a chat message. Your own notes sit on the right of the column, and notes from other participants sit on the left. Each card shows the author and the author's role (Moderator or Voter), the time, the note text, and the actions you can use on that note. The role uses the same label as a chat message. A single note has no separate accent line inside the card; the card's rounded border is the only accent border, in blue for your notes and purple for notes from other participants. The cards use the same 8px vertical spacing as the standup work item cards. Notes in a group have a 20px gap before and after the group. Guests can read the notes but cannot add or edit them.",[21,6655,6657],{"id":6656},"read-edit-and-like-a-note","Read, edit, and like a note",[26,6659,6660,6663,6666,6669],{},[29,6661,6662],{},"If you wrote the note, the card itself contains an editor. Change the text directly on the card and it is saved shortly after you stop typing. Only the author or a moderator can edit a note.",[29,6664,6665],{},"Select the like button on a card to like a note. Select it again to remove your like. The button shows how many likes the note has. You can like notes in the Vote stage. In the Actions stage the like button and its count stay on the card but are read-only, so you can still see the totals. The like button, and the delete button on notes you wrote, sit at the right edge of the action row for every participant, close together.",[29,6667,6668],{},"A group shows one like button with the sum of its notes' likes. A new like is added to the first note in the group. If you already liked a note in the group, selecting the group like removes your like from the first note you liked.",[29,6670,6671],{},"The delete button on a card asks for confirmation, then removes that note, only if you wrote it. A group has one delete action that removes every note in the group, and only a participant who wrote every note in the group can use it. A note that belongs to an action item keeps its text and editor, but its like is disabled until the action item is removed. Grouping is still available; grouping linked notes adds the whole group to their action items.",[61,6673],{"alt":6674,"caption":6675,"stem":6676},"The retrospective board with notes in the three columns, the stage selector, and the shared countdown","The retrospective board","guide-retrospective",[21,6678,6680],{"id":6679},"select-several-notes","Select several notes",[12,6682,6683],{},"Each card has a checkbox at the start of its action row. A moderator sees one on every card. A voter sees one on every card during the Vote stage, so they can like several notes at once, including notes written by other people, and only on their own notes in the other stages. A group has one checkbox in its action bar, and it selects every note in the group; it appears to a moderator, to a voter during the Vote stage, and to a participant who wrote every note in the group. Checking a note ticks its checkbox. The moderator's checked notes are filled with the light accent colour that matches their border, and every participant sees the same fill, even when they browse the retrospective locally. A voter's own checkbox only ticks, because the fill always shows the moderator's shared selection. A group is filled as one card when any of its notes is checked. The fill is stored with the retrospective, survives a reload, and is cleared when the sprint changes.",[12,6685,6686,6687,6689,6690,6693],{},"A moderator also has an ",[16,6688,3559],{}," button at the start of the action bar, before ",[16,6691,6692],{},"Group notes",". It opens the Edit planning session dialog, where you can change the title, description, and schedule of the planning session. The new values show on the planning tab and the progress bar right away. If the save fails, the previous values come back and a message tells you that the planning session could not be saved.",[12,6695,6696],{},"Select the checkboxes of the notes you want, then use the action bar below the notes and action items:",[26,6698,6699,6704,6710,6716,6722],{},[29,6700,6701,6703],{},[16,6702,6692],{}," is available to moderators. The selected notes in each column join one group. The button is enabled from the Vote stage on, when at least two selected notes are in the same column and at least one of them is not already in a group. If a selected note already belongs to an action item, that action item takes on the whole group's notes, authors, and likes.",[29,6705,6706,6709],{},[16,6707,6708],{},"Ungroup notes"," is available to moderators. The selected notes in each column leave their group. The button is enabled from the Vote stage on, when at least one selected note belongs to a group.",[29,6711,6712,6715],{},[16,6713,6714],{},"Like notes"," adds your like to every selected note. It is enabled in the Vote stage, including when the selection contains another participant's notes.",[29,6717,6718,6721],{},[16,6719,6720],{},"Create action items"," uses the tasks icon and is available to moderators. It creates one action item for each selected note and one for each selected group. Notes that already belong to an action item, and groups containing one, are skipped. The action is enabled when at least one selected note or group is not already linked.",[29,6723,6724,6727],{},[16,6725,6726],{},"Delete notes"," removes the selected notes you wrote. The action is disabled when the selection includes a note written by someone else, so a mixed selection is for liking only. The checked action items are removed with the separate action item delete action. A confirmation dialog appears before anything is deleted.",[12,6729,6730],{},"Grouped notes stay together and are separated from the rest of the column by a 20px gap. The whole group shares one comment card, one pair of left and right borders, one author header, and one action bar. The author header shows the first note's author and time. Each grouped note has its own editor inside the card; your own notes are editable and the other notes are read-only. Each note except the last is separated from the next by a 1px dashed bottom border in the group card's accent colour. The last note has no bottom border, so the group keeps one clean end, and a single note has no separator. The group action bar has one selection checkbox that selects every note in the group, one like button with the summed like count, and one delete action. The delete action appears only when you wrote every note in the group, and it removes every note in the group after confirmation. The group like and delete buttons sit at the right edge of the group action row, close together.",[12,6732,6733],{},"Deleting a note is disabled while the note belongs to an action item. Remove the action item first if you need to delete its source notes. Removing the action item leaves the source notes in the retrospective.",[12,6735,6736,6737,6740,6741,6743,6744,6746],{},"A moderator also has a ",[16,6738,6739],{},"Discard changes"," text button immediately after the delete actions, the same action the Standup offers. It asks for confirmation and deletes every note, action item, and the timer of the retrospective on screen, returning it to its initial state with its chosen type. Other sprints, other boards, and the planning session's other retrospectives keep their notes, action items, and timer. The ",[16,6742,5259],{}," action sits after Discard changes with spacing before it, and ",[16,6745,3592],{}," follows it and creates or updates Jira work items for every action item in the selected sprint that has a work item type other than None. Only a moderator sees Discard changes and Apply. Discard changes is disabled when the retrospective on screen has no notes, no action items, and an untouched timer, and it stays disabled while the discard is being saved. Apply is available when at least one action item has a work item type other than None and is new or has changed since the last Apply, even when no rows are checked. After a successful Apply it is disabled until an action item changes.",[21,6748,6750],{"id":6749},"see-your-notes-in-the-status-and-assignee-tables","See your notes in the Status and Assignee tables",[12,6752,6753,6754,430,6756,6759],{},"From the Vote stage on, the right side panel has two more tabs, ",[16,6755,5727],{},[16,6757,6758],{},"Assignee",". Both tables list the notes of the retrospective. A group is one row, with the first line of each note shown one under the other and separated by a dashed line. A row shows a checkbox, the author, and the first line of the note, cut with an ellipsis when it is longer.",[26,6761,6762,6767],{},[29,6763,6764,6766],{},[16,6765,5727],{}," groups the notes by the three columns of the retrospective type.",[29,6768,6769,6771],{},[16,6770,6758],{}," groups the notes by the person who wrote them. A group sits under the author of its first note.",[12,6773,6774],{},"A checkbox in a table is the same checkbox as on the note. Selecting a row selects the note on the board, and selecting a note on the board selects its row. A group row selects every note in the group. A voter can select their own notes outside the Vote stage and any note in the Vote stage.",[12,6776,6777,6778,6780,6781,6783],{},"Drag a row into another section to move it. In ",[16,6779,5727],{},", a section is a column, so the note moves to that column; inside its own section it changes only the order. In ",[16,6782,6758],{},", a section is one author, so this makes that person the note's author. Grouped notes move together. Only a moderator or the note's author can drag a row; another row returns to its place with a message. A column can hold at most 200 notes, so a move into a full column is refused.",[12,6785,6786],{},"The tables appear in the Vote and Actions stages. During Feedback they are hidden, because another participant's note is still face down.",[12,6788,6789,6790,6792],{},"Changing a note's author also changes the role shown on the note and the Authors column of every action item built from it. The move saves right away, so there is nothing to Apply. When you are ready, ",[16,6791,6720],{}," in the action bar is the blue primary action.",[21,6794,6796],{"id":6795},"turn-notes-into-action-items","Turn notes into action items",[12,6798,6799,6800,6802,6803,6806],{},"A moderator selects one or more notes or groups, then selects ",[16,6801,6720],{}," in the note action bar. The button is enabled when at least one selected note or group has no action item yet. Only those unlinked notes and groups create rows; the ones that already have an action item are skipped. The action items appear in a table above the action bar. A centered ",[16,6804,6805],{},"Action items"," heading sits above the table, with a short line below it that reads \"Follow-up action items based on the team retrospective notes.\" The heading is smaller than the sprint or board name and is hidden when the table has no rows. The table stretches across the left content, and the selected action item's details are in the Details tab of the right side panel when the action item has no voting tab. While no action item is selected, the side panel has no Details tab. A moderator can drag a row to change the order of the action items. Everyone sees the new order right away, and the Confluence archive writes the action items in that order.",[26,6808,6809,6812,6815,6821,6828],{},[29,6810,6811],{},"One selected single note creates one row.",[29,6813,6814],{},"One selected group creates one row. The row uses the group's first note as its summary and lists every author in the group.",[29,6816,6817,6818,6820],{},"The Type column header is the work-item icon, and the next column is headed ",[16,6819,433],{},". Its cells show the same issue key link as the planning session tables, with the action item summary on hover. For a moderator, the matching work item type icon comes before the compact dropdown, and the header icon and the type icon are left aligned. The dropdown starts with None, which is not the default. When None is selected, the icon becomes an empty space of the same width so the cell does not resize. For a voter or guest, the Type column shows only the work item type icon and uses the minimum width, and their first column is a new empty column that marks the action item the moderator selected. The remaining columns show the summary, the authors, the total likes of the source notes, and the estimate. The Summary column cells show the summary without a Summary label.",[29,6822,6823,6824,6827],{},"The last column is headed ",[16,6825,6826],{},"Estimate",". It shows the linked work item's current estimate in the selected board's unit: story points for a numeric board and a work-day duration for a time board. The cell stays empty for an action item without a Jira link or without an estimate. The column is hidden when the board has no estimation field.",[29,6829,6830],{},"For everyone else the type cell shows only the work item type icon, with an empty space of the same width when the type is None, and the header icon and the type icon are centered in their column. The Type column for a voter or guest uses the minimum width. A moderator changes the type in the dropdown; the icon updates immediately, and if the change cannot be saved, the previous type returns.",[12,6832,6833,6834,6836,6837,6839],{},"A moderator sees a checkbox column for selection and a radio column for choosing the shared row shown in the Details tab of the side panel. The radio column header uses the same presenter mode icon as the single selection column of the Refinement and grooming tab. Everyone else sees the same radio column, and their first column is an empty column of the minimum width that shows a warning ",[16,6835,1515],{}," badge on the action item the moderator selected, with a tooltip that names it, like the Refinement and grooming table. The badge follows the moderator's current selection even while you browse the retrospective locally. While you are locked to the moderator, your radio follows the moderator's row. Select another row's radio to browse that action item yourself: the choice detaches you from the moderator, appears only in this browser tab, and leaves the moderator's shared row unchanged. Selecting another action item by the moderator does not replace your local row while you stay detached. Selecting an action item with its checkbox also selects the notes that were used to create it. Choosing another radio button replaces the summary and description in the Details tab with the newly selected action item. The like count in the table is shown in a purple lozenge with no icon. The ",[16,6838,4798],{}," column in the table shows plain text. Edit the summary in the Details tab while no voting tab is shown; only a moderator can change it there.",[12,6841,6842,6843,6845,6846,6848],{},"The action item details show a ",[16,6844,4798],{}," label and a ",[16,6847,631],{}," label above the two fields. Only a moderator can edit the summary, the description, and the work item type. The summary uses the same inline text field as a work item summary in the Details tab. The description uses the same editor as a work item description. Voters and guests see the action item details read-only. The type dropdown starts with None, then lists the work item types of the board's project, without subtasks. The first Jira work item type remains the default.",[12,6850,6851],{},"The action bar below the action item table controls both kinds of selection:",[26,6853,6854,6860],{},[29,6855,6856,6859],{},[16,6857,6858],{},"Delete action items"," uses the table-row-delete icon and removes only the checked action items after a confirmation dialog. It is available to moderators. The source notes stay in the retrospective when you remove an action item. A Jira work item that was already created stays in Jira.",[29,6861,6862,6864],{},[16,6863,3592],{}," creates a work item for every action item in the selected sprint that has a work item type other than None and no Jira link, and updates the linked work item for every action item that has a type and a link. It is available to moderators. Action items with None are skipped entirely, so no Jira work item is created or updated for them. The checked rows do not limit it. It is a text button immediately after Archive, and it is available only when at least one action item has a work item type other than None and is new or has changed since the last Apply, so a second Apply without an edit stays disabled. New work items are added to the project backlog. If some rows fail, the retrospective shows a warning and the successful rows keep their links. A small hint below the action item table explains that Apply creates or updates Jira work items from the action items and that estimation becomes available once a Jira work item is created from an action item. The hint appears to moderators only, when at least one action item has a work item type other than None.",[12,6866,6867],{},"The action bar sits directly below the action item table, with the planning progress bar directly below it and a space.200 vertical gap between them. This is the same placement as the action toolbar in the capacity planning tab.",[21,6869,6871],{"id":6870},"the-timer","The timer",[12,6873,6874],{},"The countdown clock sits at the right of the action bar below the retrospective board. A moderator also sees the controls there, with the clock to the right of the fast-forward button. Everyone sees the clock.",[26,6876,6877,6880,6883,6886,6889,6892,6895,6898,6901],{},[29,6878,6879],{},"A moderator chooses 1, 3, 5, 10, or 15 minutes. Choosing a duration resets the countdown.",[29,6881,6882],{},"The first note you add in Feedback starts the countdown automatically with the selected duration. Anyone in the team can start it this way. The stage then locks until the countdown ends or a moderator fast-forwards it. If the countdown was already started or paused, adding a note does not restart or resume it.",[29,6884,6885],{},"The play button starts the timer, pauses it while it runs, and resumes it when paused. Only a moderator sees the duration selector, the play button, and the fast-forward button.",[29,6887,6888],{},"A moderator can use the fast-forward button to end the countdown and move to the next stage right away.",[29,6890,6891],{},"The remaining time is shown in a large rounded box. When the countdown ends, the same box shows that time is up.",[29,6893,6894],{},"The clock updates every second.",[29,6896,6897],{},"While the stage is Feedback, the cards written by other participants keep their layout but hide the note text and the like button. Your own note keeps its text and editor. Grouping and ungrouping are disabled in Feedback; creating action items is enabled only in the Actions stage. Delete stays available.",[29,6899,6900],{},"When the countdown reaches zero, the stage moves to Vote and the note text is revealed. The text appears for everyone at the same time, including the person who changes the stage. Your own notes stay visible all the time.",[29,6902,6903],{},"In the Vote and Actions stages the timer is just a timer. A moderator can start it again at any time to timebox the discussion without hiding the notes, except in the Actions stage where the timer controls are disabled.",[12,6905,6906],{},"The progress bar under the action bar shows how far the planning session is from its start and end dates. It ends to the left of the side panel.",[21,6908,6910],{"id":6909},"stages","Stages",[12,6912,930,6913,6916,6917,6919],{},[16,6914,6915],{},"Stage"," dropdown sits after the timer controls in the action bar. Its three stages are grouped under the ",[16,6918,6915],{}," label inside the menu:",[26,6921,6922,6927,6932],{},[29,6923,6924,6926],{},[16,6925,359],{}," is the default. You can add notes. Grouping, ungrouping, likes, and creating action items are disabled.",[29,6928,6929,6931],{},[16,6930,2303],{}," disables new notes. You can like notes. Creating action items is disabled.",[29,6933,6934,6936],{},[16,6935,5395],{}," disables new notes and likes. Like buttons and counts stay visible but cannot be selected. A moderator can create action items. The countdown controls are disabled.",[12,6938,6939],{},"A small line below the notes explains the current stage. Everyone sees it. In Feedback it invites the team to add sticky notes with their feedback. In Vote it explains that this is the time to collect which notes are worth creating action items from. In Actions it explains that notes can be grouped by common meaning and action items created from the most-voted notes.",[12,6941,6942],{},"A moderator switches the stage. Everyone else sees the current stage in the dropdown but cannot change it. The stage is remembered with the retrospective and survives a reload.",[12,6944,6945],{},"While a countdown has started and has not ended, the stage is locked. When the countdown ends or is fast-forwarded, the next stage is selected automatically. The notes are revealed when you leave Feedback, and they are hidden again if you go back to Feedback.",[12,6947,6948],{},"An action item shows the total likes of all its source notes. When the action item comes from a group, this includes every note in the group. Grouping notes later also adds the whole group's notes, authors, and likes to every action item already linked to a note in the group. Ungrouping keeps the action item linked to the notes and keeps the total.",[21,6950,6952],{"id":6951},"archive-and-complete","Archive and complete",[12,6954,6955,6956,6958,6959,6961],{},"A moderator can archive the retrospective to Confluence with the ",[16,6957,5259],{}," button before Apply in the action bar. It is available in the ",[16,6960,5395],{}," stage, because the notes stay hidden from everyone until the team reveals them. The archive writes the notes, the participants, and the action items of the selected sprint to the page, and it creates or updates the page. It does not close the planning session. See Archiving to Confluence for the page contents.",[12,6963,6964,6965,6967,6968,6970],{},"The danger-colored ",[16,6966,3562],{}," button, above the session tabs beside ",[16,6969,568],{},", closes the planning session. It asks for confirmation, then permanently removes the planning session and its notes, action items, standup, and chat.",[21,6972,6974],{"id":6973},"details-and-chat","Details and chat",[12,6976,6977],{},"The right side panel has a Chat tab on the right. When an action item is selected and it has no voting tab, a Details tab appears on the left. The Details tab shows the selected action item. While no action item is selected, the panel shows only the Chat tab. The Chat tab holds the full session conversation: every message sent from the planning session, plus messages sent from outside the session for the work items the retrospective shows, including the work items linked from action items, ordered by time. A work item message shows its work item key as a small link at the start of its action row; select it to open the work item in Jira. When you select an action item that is linked to a Jira work item, the messages you send go to that work item chat, and the message shows the work item key as a small link. With no action item selected, with an action item that has no Jira link, or when you cannot open the linked work item, the messages go to the planning-session chat. The planning conversation belongs to the planning session, so it is the same chat in every tab that opens that planning session.",[12,6979,6980,6981,6983,6984,6986],{},"When the selected action item is linked to a Jira work item, the side panel also shows a voting tab for every perspective whose estimation uses the board in the board selector. The voting tabs appear before ",[16,6982,1877],{},". Each tab opens the voting panel for the linked Jira work item. A voting tab already shows the linked work item details, so the Details tab is hidden while at least one voting tab is shown. An action item without a Jira link shows no voting tabs. Changing the board selector changes the voting tabs to that board's matching perspectives. When you accept an estimate in a voting tab, the linked action item's ",[16,6985,6826],{}," cell shows the new value right away, and every other participant sees it as soon as the accepted estimate reaches them.",[12,6988,6989,6990,6992,6993,6995,6996,6998],{},"The side panel is 400px wide and starts at the top of the planning session content, level with the board and sprint selectors. The Details tab is selected by default when it is shown. When a voting tab is shown, the panel opens on the first voting tab. The moderator's chosen tab is part of the shared retrospective data, so locked participants follow it. A yellow ",[16,6991,1515],{}," badge marks the tab the moderator has open: ",[16,6994,2040],{},", a voting tab, or ",[16,6997,1877],{},". Every non-moderator sees it, whether they follow the moderator or browse on their own. The retrospective type selector sits at the end of the board and sprint row, immediately left of the side panel.",[26,7000,7001,7004,7007,7010,7013],{},[29,7002,7003],{},"Moderators and voters can send public or private messages. Guests can send public messages and cannot see private messages.",[29,7005,7006],{},"Work item messages appear next to planning messages by their sent time. They stay available for 72 hours and are hidden when you cannot open that work item in Jira.",[29,7008,7009],{},"When you send a message right after your own previous message, the new text is added to that message after a single newline. The combined message keeps one author header, one time, and one action row. Editing it edits the combined text. A message from another participant, a private or public change, or a role change starts a new message.",[29,7011,7012],{},"Messages can be edited or deleted by their author, and can be reacted to with thumbs up or thumbs down.",[29,7014,7015],{},"The side panel stretches to the height of the retrospective content. The note columns, action item table, and progress bar stay to its left.",[12,7017,7018],{},"The bell at the right of the Details and Chat tabs, after your role badge, controls sound notifications for the timer and the chat. Select it once to turn sound on. The bell starts muted.",[21,7020,7022],{"id":7021},"follow-the-moderator","Follow the moderator",[12,7024,7025,7026,334,7028,334,7030,917,7032,7034],{},"Voters and guests start locked to the moderator. While locked, you follow the moderator's action item, sprint, retrospective type, and side panel tab. The checked-note highlight is always shared, even while you browse locally. The moderator's changes arrive right away. You also follow the moderator's space page tab, so the page moves between ",[16,7027,340],{},[16,7029,343],{},[16,7031,346],{},[16,7033,349],{}," for the same planning session.",[26,7036,7037,7042,7048,7051,7057],{},[29,7038,7039,7041],{},[16,7040,2366],{}," applies to the planning tab you are on. Switching to another planning tab yourself clears it, so you start detached on the new tab. A move caused by the moderator's tab change keeps it checked.",[29,7043,7044,7045,7047],{},"Clear ",[16,7046,2366],{}," to browse on your own. You can pick another tab, pick another sprint, or pick another action item. Your action item choice applies only to you and is not shared with the team. Your choices stay with this tab. The shared board and retrospective type stay moderator controlled.",[29,7049,7050],{},"Picking another tab, sprint, or action item while locked also detaches you.",[29,7052,7053,7054,7056],{},"Check ",[16,7055,2366],{}," again to discard your local choices and follow the moderator. The sprint and board return to the moderator's shared choice.",[29,7058,7059],{},"The lock is remembered in this browser tab while you stay on the tab.",[21,7061,7063],{"id":7062},"changes-appear-for-everyone","Changes appear for everyone",[12,7065,7066],{},"Every note, like, group, action item, and timer change is saved for the planning session and appears for the other participants right away. If the connection drops, the tab reloads the current state when the connection returns.",[12,7068,7069],{},"Most changes appear in your own view immediately, before the server answers. This includes the timer duration and controls, the Stage, adding and deleting notes, likes, groups, action items, and Discard changes. Confirmation dialogs close as soon as you confirm. If a change cannot be saved, the previous state is restored and a warning appears. The controls stay available while the change is being saved.",[12,7071,7072],{},"A like you give or take back stays as you left it. A slower copy of your earlier like never adds it back, and other people's likes still appear as they give them. If a like cannot be saved, only the likes from that click go back to how they were, and your other notes stay as you left them.",[12,7074,7075],{},"Retrospective data is kept for 72 hours after the last change. Older retrospective data is removed automatically.",{"title":153,"searchDepth":154,"depth":154,"links":7077},[7078,7079,7080,7081,7082,7083,7084,7085,7086,7087,7088,7089,7090,7091],{"id":6512,"depth":154,"text":6513},{"id":6539,"depth":154,"text":6540},{"id":6569,"depth":154,"text":6570},{"id":6638,"depth":154,"text":6639},{"id":6656,"depth":154,"text":6657},{"id":6679,"depth":154,"text":6680},{"id":6749,"depth":154,"text":6750},{"id":6795,"depth":154,"text":6796},{"id":6870,"depth":154,"text":6871},{"id":6909,"depth":154,"text":6910},{"id":6951,"depth":154,"text":6952},{"id":6973,"depth":154,"text":6974},{"id":7021,"depth":154,"text":7022},{"id":7062,"depth":154,"text":7063},"2026-11-13","Run a sprint retrospective in Jira: collect notes, group them, vote and turn the result into action items.","Sprint retrospectives","\u002Fog\u002Fguide-sprint-retrospectives.jpg",[7097,7098,7099],"sprint retrospective","agile retrospective","jira retrospective",{},14,"\u002Fgetting-started\u002Fsprint-retrospectives",{"title":6497,"description":7093},{"loc":7102,"lastmod":802},"sprint-retrospectives","guide\u002Fen\u002Fsprint-retrospectives","guide\u002Fsprint-retrospectives","ybCpunharAAtUbt5ZQmwP9arm2Kx-gjKWlDo-VcdhwU",{"id":7110,"title":7111,"body":7112,"dateModified":802,"datePublished":7092,"description":7906,"extension":162,"heading":7907,"image":7908,"imageAlt":7907,"keywords":7909,"locale":168,"meta":7913,"navigation":170,"order":7914,"path":7915,"section":173,"seo":7916,"sitemap":7917,"slug":7918,"stem":7919,"translationKey":7920,"__hash__":7921},"guide\u002Fguide\u002Fen\u002Fsprint-standups.md","Sprint standups | Scrumpy Planning Poker",{"type":9,"value":7113,"toc":7889},[7114,7119,7128,7133,7135,7152,7156,7204,7207,7211,7220,7234,7237,7247,7267,7271,7278,7283,7287,7308,7323,7353,7357,7373,7377,7389,7393,7398,7404,7409,7458,7462,7474,7482,7485,7490,7561,7563,7577,7597,7601,7613,7669,7684,7766,7769,7773,7781,7787,7800,7804,7823,7832,7840,7844,7847,7876,7880,7886],[12,7115,930,7116,7118],{},[16,7117,346],{}," tab reviews one sprint, one board, or one saved filter inside a planning session. Work items are shown in the lanes of the selected scope, in a shared standup order that starts as the order Jira returns. Every planning session keeps its own data for each board and sprint, and for each filter. Switching planning sessions shows that session's data, and when the session you last opened is no longer available, the first planning session opens instead. The assignee avatar is on each card, but assignee grouping does not control the position. Status moves stay stored in the standup session until you apply them to Jira.",[12,7120,7121,7122,7124,7125,7127],{},"The side panel gives you two compact views of the same standup. The ",[16,7123,5727],{}," table groups the work by board column, and the ",[16,7126,6758],{}," table groups it by person. Both show the same flags, passed checks, staged changes, and estimates as the board.",[12,7129,7130],{},[16,7131,7132],{},"Everything you change on this screen is virtual: status moves, flags, the order, and the work items you add from a filter stay in Scrumpy. Jira changes only when you select Apply.",[21,7134,6513],{"id":6512},[26,7136,7137,7143,7146,7149],{},[29,7138,7139,7140,7142],{},"Moderators can create a new planning session with the ",[16,7141,568],{}," button at the top of the tab.",[29,7144,7145],{},"The space does not need a board. When the space has a board, the standup uses the board and, on a Scrum board with a running sprint, that sprint. When the space has no board, the standup reads a saved Jira filter.",[29,7147,7148],{},"A planning session must exist. Moderators choose the shared board, sprint, or filter. Locked participants follow that selection.",[29,7150,7151],{},"The standup is locked by the space password when one is set.",[21,7153,7155],{"id":7154},"choose-what-the-standup-shows","Choose what the standup shows",[66,7157,7158,7163,7175,7189,7198,7201],{},[29,7159,6545,7160,7162],{},[16,7161,346],{}," tab and pick a planning session from the tabs above the board.",[29,7164,7165,7168,7169,7171,7172,7174],{},[16,7166,7167],{},"The space has a board:"," pick a ",[16,7170,6556],{},". If the board is a Scrum board with a running sprint, pick a ",[16,7173,6562],{}," too. The sprint list shows only the sprints that are currently running; sprints that already ended and sprints that have not started yet are not listed. When the board has no running sprint, the sprint selector is hidden and the standup shows the work items currently on the board. Only a moderator changes the shared board. A voter or guest can pick another sprint locally, which detaches the viewer from the moderator.",[29,7176,7177,7180,7181,7184,7185,7188],{},[16,7178,7179],{},"The space has no board:"," the board selector and the sprint selector are hidden. Pick a saved ",[16,7182,7183],{},"filter",", and the standup shows only the work items that filter returns from this space. The filter selector sits in the toolbar next to the ",[16,7186,7187],{},"estimate perspective"," selector. The perspective selector chooses whose estimate the cards show; the default perspective is selected at first. While no filter is selected, the toolbar asks you to choose one and the standup shows no work items. A voter or guest can pick another filter or perspective locally, which detaches the viewer from the moderator.",[29,7190,5870,7191,7194,7195,7197],{},[16,7192,7193],{},"Max per column"," dropdown before the columns selector to cap how many work items each column shows. The options are 5, 10, 15, 25, 50, 100, 150, and 200, and the default is 15. The standup reads up to 200 work items for the selected scope in one read, and the dropdown only filters the loaded work items. Changing the cap does not read Jira again. A column with more work items than the cap shows a left-aligned hint at its bottom. A capped column ends with a hint that shows the number shown and the number loaded, for example showing 15 of 23. The numbers sit in badges on one vertically centered line. Work items beyond the cap are already loaded when the scope read includes them and stay hidden until you raise the cap. A work item the standup loaded before it was hidden keeps its place in the shared order and its staged changes. A moderator shares the cap with everyone who is locked to the moderator. If you pick another cap while you are locked, you detach and keep your own choice in this browser tab. The same cap applies to the ",[16,7196,5727],{}," tab: each column lists only the first work items up to the cap, and a capped column ends with the same hint row. The hint row is not a work item and cannot be dragged.",[29,7199,7200],{},"Next to the limit dropdown, use the columns multi-select to choose which columns are shown. It starts empty and shows every column. Select one or more columns to show only those, or clear the selection to show all again. A moderator shares the visible columns with everyone who is locked to the moderator. If you pick another selection while you are locked, you detach and keep your own choice in this browser tab.",[29,7202,7203],{},"The sprint name and goal sit above the lanes. The link icon opens the sprint in the Jira backlog in a new browser tab. A board without a running sprint hides that line completely, so the lanes start right under the toolbar. A filter standup shows the filter name instead.",[12,7205,7206],{},"Work items that belong to another space are never shown, even when the selected sprint, board, or filter includes them. The per-column cap counts only the work items of this space.",[21,7208,7210],{"id":7209},"add-work-items-from-a-filter","Add work items from a filter",[12,7212,7213,7214,7216,7217,7219],{},"A moderator can stage more work items for the sprint from the standup. The ",[16,7215,3695],{}," button sits next to the primary ",[16,7218,3559],{}," button at the start of the bottom action bar, and it appears only while the standup shows a running sprint.",[66,7221,7222,7226,7229],{},[29,7223,5948,7224,569],{},[16,7225,3695],{},[29,7227,7228],{},"Pick a saved Jira filter, an active sprint, or the backlog. The dialog previews the work items of the choice.",[29,7230,7231,7232,569],{},"Select the work items you want, then select ",[16,7233,3765],{},[12,7235,7236],{},"To start over, clear the picker. The chosen source is dropped, the search box empties, and the first 100 shared filters return.",[12,7238,7239,7240,7243,7244,7246],{},"The work items appear in their status columns with a ",[16,7241,7242],{},"New"," badge. Every participant sees them right away, like a staged status move. You can still move, flag, or reassign a staged work item. Jira is not changed until a moderator selects ",[16,7245,3592],{},", which moves the staged work items into the sprint together with the other standup changes. After Apply the badge disappears and the work items are part of the sprint.",[26,7248,7249,7252,7255,7258,7264],{},[29,7250,7251],{},"Work items that already belong to the sprint, or that belong to another space, cannot be selected.",[29,7253,7254],{},"A work item that sits in another sprint moves to this sprint on Apply.",[29,7256,7257],{},"A staged work item in a status that is not mapped to a board column stays hidden, like any other work item.",[29,7259,7260,7261,7263],{},"To remove one staged work item before Apply, select its undo button. ",[16,7262,6739],{}," removes every staged work item with the other staged changes.",[29,7265,7266],{},"If Jira refuses to add a work item, it stays staged and the error names it.",[21,7268,7270],{"id":7269},"read-the-board","Read the board",[12,7272,7273,7274,7277],{},"Each column of the selected board is a lane, in the board's configured order. In a filter standup, each status of the space is a lane, ordered by status category. Every visible column shares the width of the board equally, so all columns stay side by side and get narrower as you show more of them. Work items whose status is not mapped to a column are not shown on a board. Inside a lane, work items follow the shared standup order. The lanes start in the order the sprint shows on the board the first time you open the standup. That is the only time the Jira order is used. From then on the standup keeps its own order and every participant sees it. A work item that joins a sprint later, or whose status changes in Jira, appears at the bottom of its column and keeps that place. A reorder someone makes in the Jira backlog never changes the standup order. The order is not grouped by assignee. Each card keeps the note look of a retrospective note: the accent border, the regular assignee avatar, the priority icon, the work item key as a link, and the estimate badge at the top right, the summary in a two-line subtle inline text area, and the action row. The priority icon appears when the work item has a priority; hover it to see the priority name. The key link opens the work item in the Jira view issue dialog. A work item the team has passed shows a small green check right of its key. At the top right, a badge shows the estimate of the work item: story points when the selected board estimates in story points, a duration when it estimates in time. A work item without an estimate shows no badge. The card does not show the last updated time. The rounded card border uses a light accent color from the Atlassian palette. Every card assigned to the same person uses the same border color, different assignees get different colors, and an unassigned card keeps the usual own or other assignee border. An unselected card background stays neutral. A selected card uses a light tint of its own border color. When an assignee is marked absent, that person's cards replace the assignee color with a gray border, and the avatar and text on those cards are dimmed. Own work items align to the right of the lane and other assignees' work items to the left. A card without an assignee shows the same empty avatar image as a retrospective note without an avatar. The status is shown by the column, not repeated on the card. A moderator can edit the summary in place: select the summary, change it in the two-line text area, then click away. The summary saves when the field loses focus. Voters and guests see the summary read only. The inline text area is left aligned, shows the ",[16,7275,7276],{},"Work item summary"," placeholder, and grows vertically when the summary is long.",[61,7279],{"alt":7280,"caption":7281,"stem":7282},"The standup board with cards in every column, the max per column selector, and the shared countdown","The standup board","guide-standup",[21,7284,7286],{"id":7285},"details-chat-and-sound","Details, chat, and sound",[12,7288,7289,7290,7292,7293,7295,7296,7298,7299,7301,7302,334,7304,917,7306,569],{},"A side panel sits to the right of the standup. It has a ",[16,7291,5727],{}," tab and an ",[16,7294,6758],{}," tab on the left, then ",[16,7297,2040],{}," or the perspective tabs when a work item is selected, and the ",[16,7300,1877],{}," tab on the right, followed by the red video link icon when the planning session has one, your role badge, and the sound bell. The side panel is 400px wide. When nothing is selected, it shows ",[16,7303,5727],{},[16,7305,6758],{},[16,7307,1877],{},[12,7309,7310,7311,6992,7313,334,7315,334,7317,7319,7320,7322],{},"The moderator chooses which tab everyone sees. Locked participants follow the tab as the moderator changes it. When you detach from the moderator, you can choose your own tab. A yellow ",[16,7312,1515],{},[16,7314,5727],{},[16,7316,6758],{},[16,7318,2040],{},", a perspective tab, or ",[16,7321,1877],{},". Every non-moderator sees it, whether they follow the moderator or browse on their own, so the moderator's current tab is always clear.",[26,7324,7325,7330,7335,7347,7350],{},[29,7326,7327,7329],{},[16,7328,1877],{}," always shows the full session conversation: every message sent from the planning session, plus messages sent from outside the session for every work item the standup shows, ordered by publish time, and every work item message keeps its work item key link. The focused work item only chooses where a new message is sent: that work item's chat. With no work item selected, a new message goes to the planning-session chat. The conversation and the selected Chat tab stay the same when you change the focused work item, and the conversation is shared with the other tabs that open the same planning session.",[29,7331,7332,7334],{},[16,7333,2040],{}," appears on the left when a work item is selected and no perspective tab is shown. It shows the summary and description of the selected work item. A moderator can edit both; voters and guests see them read only.",[29,7336,7337,7340,7341,7343,7344,7346],{},[16,7338,7339],{},"Perspective tabs"," appear before ",[16,7342,1877],{}," when a work item is selected. Each tab is a perspective whose estimation target is the board and whose estimation board matches the board selected in the Standup. A perspective for another board does not appear. A perspective tab already shows the work item details, so ",[16,7345,2040],{}," is hidden while at least one perspective tab is shown. The tabs disappear when no work item is selected.",[29,7348,7349],{},"The bell at the right of the tabs controls sound notifications for the active chat. Select it once to turn sound on. The bell starts muted.",[29,7351,7352],{},"The role badge before the bell links to the Permissions settings.",[21,7354,7356],{"id":7355},"flag-a-work-item","Flag a work item",[12,7358,7359,7360,7363,7364,7366,7367,7369,7370,7372],{},"A flag marks a work item that needs attention. The flag button sits at the right of the card action row, before the ",[16,7361,7362],{},"Move to"," dropdown. It shows the Jira flag: a work item that is already flagged in Jira opens with a red flag. Select the flag button on an unflagged work item to stage a flag, then press ",[16,7365,3592],{}," to write the Jira Flagged field. Select a red flag to stage clearing it, then press ",[16,7368,3592],{}," to clear the flag in Jira. Selecting the same button again before Apply returns the work item to the Jira state. The flag is shared with every participant as soon as you select it, but Jira is not changed until Apply. If Jira refuses the change, the flag stays staged and the error names the affected work items. A moderator can flag any work item, and a voter can flag only the work items assigned to them. Guests see the flag and its tooltip but cannot change it. ",[16,7371,6739],{}," also removes the flag changes you can discard once you confirm. The flag belongs to the standup session and is not a separate Jira comment or label. Selecting the flag changes the button at once, and the participant who selected it ignores the echo of their own change, so a delayed echo cannot undo a newer toggle.",[21,7374,7376],{"id":7375},"mark-the-work-item-under-discussion","Mark the work item under discussion",[12,7378,7379,7380,7382,7383,7385,7386,7388],{},"A moderator clicks the card of the work item the team is discussing. The card itself is the click target: the avatar, the key, the priority, the estimate badge, the summary, and the empty space around them all select the work item. The flag button, the bulk checkbox, and the ",[16,7381,7362],{}," dropdown in the card action row keep their own behavior and do not change the selection. The whole card is highlighted for everyone who is locked to the moderator until the moderator clicks it again. A voter or guest can click a card to highlight it locally, which detaches the viewer without changing the shared selection. The shared selection changes immediately without reloading the board. The selecting participant ignores the echo of their own selection, so a delayed echo cannot move the highlight back. Every non-moderator also sees an ",[16,7384,1515],{}," badge on the work item the moderator has selected. The badge stays visible whether you follow the moderator or view the standup locally, so the moderator's current work item is always clear. When you can also check that card, the badge sits to the right of the checkbox. A small left-aligned hint below the columns and above the action bar also explains that a moderator selects a work item by clicking the card, that the shared selection is between the participants, and that ",[16,7387,3592],{}," must be pressed to synchronize the changes with Jira.",[21,7390,7392],{"id":7391},"check-the-work-in-the-status-table","Check the work in the Status table",[12,7394,930,7395,7397],{},[16,7396,5727],{}," tab is the first tab of the side panel. It lists every work item of the sprint, of the board when no sprint is running, or of the selected filter, in one table. Each board column is a wide row with its name in the center, and the work items of that column sit under it. Only the columns you show on the board appear here.",[12,7399,7400,7401,7403],{},"Use this table when you want to walk the sprint in order without scanning the full board. The ",[16,7402,7193],{}," cap applies here too, so a crowded column ends with the same hint row as the board.",[61,7405],{"alt":7406,"caption":7407,"stem":7408},"The Status table with work items grouped under each board column","The Status table","guide-standup-status",[26,7410,7411,7414,7426,7432,7435,7444,7447,7450,7453],{},[29,7412,7413],{},"Each row shows the work type icon, the priority icon, the flag button, the work item key, a green check when the work item is passed, the undo button, and the estimate. The key opens the work item in Jira.",[29,7415,7416,7417,7419,7420,7422,7423,7425],{},"The narrow column after the work item key shows a green check once the team has passed the work item. A work item is passed when the moderator forwards its countdown, or when the moderator selects another work item or clears the selection after its countdown has run out. A countdown that only runs out does not mark it. The check appears in the same place in the ",[16,7418,6758],{}," tab and next to the key on the card, and it stays for the rest of the planning session and scope. A passed check counts as a change, so ",[16,7421,6739],{}," removes every check for everyone in the standup, and ",[16,7424,3592],{}," clears them too when it writes the staged changes.",[29,7427,7428,7429,7431],{},"A moderator has a radio button in the first column to select the work item under discussion. Everyone else sees a yellow ",[16,7430,1515],{}," badge in the first column, on the work item the moderator selected, and a radio button for their own selection. The table and the board keep the same selection: pick a work item in one place and the other follows.",[29,7433,7434],{},"Drag a work item to change its place in its column. The row and the board move at once, before the change is saved. The person who dragged ignores the echo of their own change, so a delayed echo cannot move the row back or undo a newer drop.",[29,7436,7437,7438,7440,7441,7443],{},"Drop a work item into another column to move it there. This works only when the ",[16,7439,7362],{}," menu of that work item offers a status of that column and the work item has no staged move. If the choices for that work item have not been read yet, the board reads them first and then drops the work item. A work item with a staged move keeps its place, just like its disabled ",[16,7442,7362],{}," menu, until you undo or apply that move. Otherwise the row returns to its place. A dismissible warning explains why.",[29,7445,7446],{},"A moderator can drag every work item. A voter can drag only the work items assigned to them. Guests can read the table but cannot change it.",[29,7448,7449],{},"Select the flag button to stage a flag or clear it, exactly like the flag on a card.",[29,7451,7452],{},"The undo button appears on a work item with a staged change: a moved place, a staged status move, or a staged flag. The card on the board shows the same undo button at the same time. Select either one to remove the staged change without changing Jira. You see the button only when you may discard that change, so a guest or another person's work item shows no undo button. Undoing a staged flag returns the work item to its original Jira flag state.",[29,7454,1353,7455,7457],{},[16,7456,3592],{}," to write the new order to the sprint rank. On a board without a sprint, the board rank is written instead. In a filter standup there is no board to rank, so the order stays in the standup and only the status and flag changes reach Jira.",[21,7459,7461],{"id":7460},"check-who-works-on-what-in-the-assignee-table","Check who works on what in the Assignee table",[12,7463,930,7464,7466,7467,7469,7470,7473],{},[16,7465,6758],{}," tab follows ",[16,7468,5727],{}," in the side panel. It groups the same work items by the person doing them. Each assignee is a wide row with the person's name in the center, and that person's work items sit under it. ",[16,7471,7472],{},"Unassigned"," sits last and holds the work items that have no assignee.",[12,7475,930,7476,7478,7479,7481],{},[16,7477,7193],{}," cap applies here too, so the table lists only the work items the board shows. A person whose work items all sit beyond the cap is not listed, in the table or in the ",[16,7480,5495],{}," picker, until you raise the cap.",[12,7483,7484],{},"Use this table when you want to see how the sprint is spread across the team, or when you need to hand a work item to someone else. The presence checkbox at the left of each row shows who is taking part in the standup.",[61,7486],{"alt":7487,"caption":7488,"stem":7489},"The Assignee table with one person marked absent","The Assignee table","guide-standup-assignee",[26,7491,7492,7498,7507,7510,7513,7519,7528,7533,7539,7548,7553,7556],{},[29,7493,7494,7495,7497],{},"The rows show the same facts as the ",[16,7496,5727],{}," tab: the work type icon, the priority icon, the flag button, the work item key, the same green passed check, the undo button, and the estimate. The check appears in the same column here, so both tables show how far the team has got.",[29,7499,7500,7501,7503,7504,7506],{},"Drag a work item into another assignee's row to give it to that person. The change appears for everyone right away, but Jira is not changed until you press ",[16,7502,3592],{},". The board avatar, the card color, and the ",[16,7505,5727],{}," row show the new person too. The row moves as soon as you drop it, and the person who dragged ignores the echo of their own change, so a delayed echo cannot put the row back or undo a newer drop.",[29,7508,7509],{},"The work items inside a row keep the board order. Dragging a work item inside its own row does not change anything, because the board order decides the order here.",[29,7511,7512],{},"A moderator can give any work item to another person. A voter can give only their own work items. Guests can read the table but cannot change it.",[29,7514,7515,7516,7518],{},"Below the table and the hint, a moderator can use the ",[16,7517,5495],{}," picker. It lists every participant whose presence checkbox is checked. Add a person who has no work items in this scope and they get their own row right away, taking part like every other assignee; drag a work item into that row to give it to them. Clear a person in the picker to remove them from the standup. A person who still has work items keeps their row, with the checkbox unchecked and disabled, while a person with no work items loses their row. Adding or removing a participant is shared right away and is saved immediately. Work items already staged to a removed person keep their row until you discard or apply the change.",[29,7520,7521,7522,7524,7525,7527],{},"An assignee change puts the undo button on the ",[16,7523,6758],{}," row, the ",[16,7526,5727],{}," row, and the card. Select it to return the work item to its Jira assignee without changing Jira.",[29,7529,1353,7530,7532],{},[16,7531,3592],{}," to write the new assignee to Jira. A rejected change stays staged and the error names the affected work items.",[29,7534,7535,7536,7538],{},"A moderator can clear the checkbox at the left of an assignee row to remove that person from the ",[16,7537,5495],{}," picker and mark them absent. The checkbox is checked by default for every assignee, and only a moderator can change it. Once cleared, the checkbox stays disabled because the person's work items still belong to them; add them back in the picker to check it again. Voters and guests see the checkbox but cannot change it.",[29,7540,7541,7542,7544,7545,7547],{},"When an assignee is absent, their work items cannot be selected from the ",[16,7543,6758],{}," table, from the ",[16,7546,5727],{}," table, or by clicking the card on the board. Their cards use a gray border and dimmed text and avatar, so you can tell them apart at a glance. They also lose the countdown pause, resume, and forward controls.",[29,7549,1640,7550,7552],{},[16,7551,6758],{}," tab open, the countdown forward button moves to the next work item in this table. It skips every absent assignee and stops at the first work item of the next present assignee. On any other tab, the forward button keeps following the board order.",[29,7554,7555],{},"The presence choice is shared right away, stays after a reload, and resets when the selected board, sprint, or filter changes. If you change several checkboxes quickly, every checkbox keeps your latest choice.",[29,7557,7558,7560],{},[16,7559,7472],{}," is always shown and is always treated as present. It has no presence checkbox.",[21,7562,7022],{"id":7021},[12,7564,7565,7566,7568,7569,334,7571,334,7573,917,7575,7034],{},"Voters and guests start locked to the moderator. While locked, you follow the moderator's work item, sprint, board, ",[16,7567,7193],{}," cap, visible columns, and side panel tab. The moderator's changes arrive right away. You also follow the moderator's space page tab, so the page moves between ",[16,7570,340],{},[16,7572,343],{},[16,7574,346],{},[16,7576,349],{},[26,7578,7579,7583,7588,7591,7595],{},[29,7580,7581,7041],{},[16,7582,2366],{},[29,7584,7044,7585,7587],{},[16,7586,2366],{}," to browse on your own. You can click another card, pick another tab, pick another sprint, change the cap, or change the visible columns. Your choices stay with this tab and are not shared with the team.",[29,7589,7590],{},"Picking a card, tab, sprint, cap, or column selection while locked also detaches you.",[29,7592,7053,7593,7056],{},[16,7594,2366],{},[29,7596,7059],{},[21,7598,7600],{"id":7599},"stage-and-apply-status-moves","Stage and apply status moves",[12,7602,7603,7604,7606,7607,7609,7610,7612],{},"Status moves, flags, and assignee changes are stored in the standup session and are not written to Jira until you apply them. Selecting, undoing a move, moving by status, flagging, changing an assignee, and discarding changes update the board immediately. A staged status move, a staged flag, a staged assignee, or a moved place puts the undo button on the card, and the same button appears on its row in the ",[16,7605,5727],{}," tab and the ",[16,7608,6758],{}," tab. The button removes the staged change right away, without changing Jira, and the card returns to its lane. You see it only when you may discard that change. Their controls stay available while the request runs. If a request fails, the change rolls back and an error explains it. The board, sprint, filter, and estimate perspective selectors and ",[16,7611,3592],{}," still wait for the server.",[26,7614,7615,7625,7631,7655],{},[29,7616,7617,7618,7620,7621,7624],{},"Select the checkbox on one or more cards, then choose an entry from the bottom ",[16,7619,7362],{}," dropdown. The menu lists only the Jira statuses every selected work item can reach under ",[16,7622,7623],{},"By status",". A moderator can check every card. A voter can check only the cards assigned to them, so a bulk move never targets another person's work item.",[29,7626,7627,7628,7630],{},"Each card has the same subtle ",[16,7629,7362],{}," dropdown. The placeholder is only a hint and resets after each action.",[29,7632,7633,7634,7637,7638,430,7641,7644,7645,7647,7648,2537,7651,7654],{},"The menu has two groups. ",[16,7635,7636],{},"By rank"," holds ",[16,7639,7640],{},"Up",[16,7642,7643],{},"Down",", which move the work item one place up or down inside its own column. ",[16,7646,7623],{}," holds the Jira statuses the card can reach with a direct workflow transition, for example ",[16,7649,7650],{},"To Do",[16,7652,7653],{},"Done",". Statuses that are not mapped to another board column are not listed.",[29,7656,7657,7658,7660,7661,7663,7664,430,7666,7668],{},"A work item that is first in its column has ",[16,7659,7640],{}," disabled, and a work item that is last in its column has ",[16,7662,7643],{}," disabled. For a bulk selection, ",[16,7665,7640],{},[16,7667,7643],{}," are disabled when no checked work item can move that way.",[12,7670,7671,7672,7674,7675,7677,7678,7680,7681,7683],{},"After a card has a staged status move, its ",[16,7673,7362],{}," menu disables every ",[16,7676,7623],{}," choice until the move is undone or applied, and the ",[16,7679,7636],{}," choices stay available. The bulk ",[16,7682,7362],{}," menu does the same while any selected card has a staged move. Apply recalculates the choices for each moved work item from its new Jira status.",[26,7685,7686,7705,7711,7714,7723,7726,7743,7748],{},[29,7687,7688,7689,7691,7692,7695,7696,7698,7699,7701,7702,7704],{},"The app reads the status choices of a work item when you open its ",[16,7690,7362],{}," menu, so the first open can take a moment and the menu shows ",[16,7693,7694],{},"Loading statuses"," under ",[16,7697,7623],{}," until the choices arrive. It keeps the choices for as long as the board is shown, so the next open of the same menu is instant. Voting, starting or forwarding the countdown, selecting a card, moving cards around the board, and discarding changes do not read Jira again. ",[16,7700,6155],{}," forgets the choices together with the rest of the board, and the next time you open a menu it reads them again. The bulk ",[16,7703,7362],{}," menu reads the choices for every checked work item that it has not read yet.",[29,7706,7707,7708,7710],{},"A staged item moves to the target column and shows an error colored undo button right of its checkbox and moderator badge. The undo button removes the staged status move right away without changing Jira. Use ",[16,7709,6739],{}," to clear every staged move, and that action asks you to confirm.",[29,7712,7713],{},"A moderator can stage moves for any work item. A voter can check and move only the work items assigned to them.",[29,7715,7716,7717,7719,7720,7722],{},"The bottom bar shows the pending count. ",[16,7718,3592],{}," writes the staged status moves to Jira. The standup also keeps the order of each lane, so a card that changed lane is placed after the cards already in its new lane. Apply writes the new order of every lane whose order changed into the selected sprint, so the sprint and the board show the standup order. On a board without a sprint, the order is written to the board order instead. In a filter standup, no Jira rank is written because there is no board; the order stays in the standup. Apply writes only the cards whose place in a lane changed, so the other cards stay where they are. A lane that holds only one card is ranked next to the neighbouring lane, so a card moved into an otherwise empty lane still leaves the order of the lane it came from. Only the lanes whose order changed are written, so a status-only ",[16,7721,3592],{}," leaves the sprint order alone.",[29,7724,7725],{},"A moderator applies every staged move in the selected sprint, board, or filter; a voter applies only the moves for their own work items.",[29,7727,7728,7730,7731,7733,7734,7736,7737,7739,7740,7742],{},[16,7729,3592],{}," is enabled only while the standup has a staged move or an order change to write. A passed check counts as a change only for ",[16,7732,6739],{},", because the check is not written to Jira, so passed checks alone never enable ",[16,7735,3592],{},". When ",[16,7738,3592],{}," runs, it writes the staged changes and clears every passed check. A work item that someone adds to the sprint or moves to another status in Jira appears in its lane after the board reloads, but it does not enable ",[16,7741,3592],{}," by itself.",[29,7744,7745,7747],{},[16,7746,6739],{}," asks you to confirm, then removes every staged move you can discard, every staged work item a moderator added from a filter, clears every passed check, and returns the lanes to the order the sprint has in Jira now, including a reorder someone made in the Jira backlog. Cancel the confirmation to keep every staged change.",[29,7749,7750,7751,7753,7754,7756,7757,7759,7760,7762,7763,7765],{},"A moderator can delete the planning session with the danger-colored ",[16,7752,3562],{}," button above the session tabs, beside ",[16,7755,568],{},". A moderator can also archive the standup with the ",[16,7758,5259],{}," button before ",[16,7761,3592],{},", and pressing ",[16,7764,3592],{}," does not archive anything by itself. Deleting asks for confirmation and permanently removes the planning session and its standup, retrospective, and chat data.",[12,7767,7768],{},"A status move fails and stays staged when the work item changed status in Jira after it was staged. The board reloads after Apply. An order write failure leaves that lane pending and reports the affected work items so you can retry. The failed order is never written to another place, so the sprint order and the board order cannot disagree because of it.",[21,7770,7772],{"id":7771},"archive-the-standup","Archive the standup",[12,7774,7775,7776,5389,7778,7780],{},"A moderator can archive the standup to Confluence. The ",[16,7777,5259],{},[16,7779,3592],{}," and appears when a Confluence space is configured. Archiving never changes Jira, the standup, or the staged changes.",[12,7782,7783,7784,7786],{},"The dialog shows the planning window, the sprint, board, or filter name, the space name, every assignee with presence and total presentation time, and every work item with its status, presentation time, and changes. A person the moderator added with the participant picker is listed too, with zero work items until something is assigned to them. A staged change is marked ",[16,7785,5456],{},". Presentation time is the countdown time the work item spent on screen and counts toward its assignee.",[12,7788,5287,7789,7791,7792,7794,7795,7797,7798,569],{},[16,7790,5259],{}," to create or update the page. The page is written under ",[16,7793,5462],{}," in a child page named after the space with a ",[16,7796,346],{}," suffix, and its title carries the word ",[16,7799,346],{},[21,7801,7803],{"id":7802},"reload-and-live-updates","Reload and live updates",[12,7805,7806,7809,7810,7812,7813,7815,7816,334,7818,917,7820,7822],{},[16,7807,7808],{},"Reload sprints and work items"," in the bottom action bar, after the ",[16,7811,7362],{}," dropdown, reloads the selected sprint or board, its Jira statuses, the estimates shown on the cards, and the Jira flags, and it forgets the ",[16,7814,7362],{}," choices so the next open reads them again. It does not change the standup order, and it does not move a work item to the place its Jira rank gives it. The rest of the bar follows it on the left: a gap, then ",[16,7817,6739],{},[16,7819,5259],{},[16,7821,3592],{}," for a moderator. The countdown sits at the right of the bar. Stages, undos, flags, and applies from other participants arrive right away. Staged moves, flags, and lane order changes are kept per planning session and per board and sprint, or per filter, and are removed when the planning session is deleted.",[12,7824,7825,7826,7828,7829,7831],{},"A moderator selects ",[16,7827,3559],{}," above the session tabs, beside ",[16,7830,568],{},", to open the Edit planning session dialog. You can change the title, description, and schedule of the planning session there. The new values show on the planning tab and the progress bar right away. If the save fails, the previous values come back and a message tells you that the planning session could not be saved.",[12,7833,7834,7835,430,7837,7839],{},"Accepting an estimate in a perspective tab updates it right away for everyone: the estimate badge on the card and the estimate in the ",[16,7836,5727],{},[16,7838,6758],{}," tabs change without a reload. The other work items on the board stay as they are.",[21,7841,7843],{"id":7842},"the-standup-countdown","The standup countdown",[12,7845,7846],{},"A countdown at the right of the action bar follows the work item the moderator is discussing. A moderator sees the duration choice, the play or pause button, and the forward button. A voter who is assigned to the selected work item also sees the play or pause button and the forward button for that item. Guests see only the clock, even when the selected work item is assigned to them, so everyone can follow the same countdown.",[26,7848,7849,7852,7855,7858,7861,7864,7867,7870,7873],{},[29,7850,7851],{},"A voter assigned to the selected work item can pause, resume, and forward the countdown. Starting a stopped countdown and changing the duration stay with the moderator.",[29,7853,7854],{},"The clock keeps following the moderator even while you browse locally, so a detached voter or guest still sees the moderator's countdown.",[29,7856,7857],{},"The duration choice offers 15 seconds, 30 seconds, 1 minute, 2 minutes, and 3 minutes. It starts at 1 minute.",[29,7859,7860],{},"The countdown stops and resets when the moderator selects another work item, and it starts again right away for the new card. Clearing the selection stops the countdown.",[29,7862,7863],{},"Changing the duration stops the countdown and shows the new duration. The moderator starts it again with the play button.",[29,7865,7866],{},"The forward button ends the current countdown and moves the shared selection to the next work item in the column. When the current card is the last one in its column, it selects the first work item in the previous column. On the last card of the first column the selection stays and the countdown ends. A new selection starts a fresh countdown automatically.",[29,7868,7869],{},"In the last 10 seconds the selected card alternates between its normal background and the same highlight background used for the selected work item once per second. It never switches to a gray warning background. In the last 5 seconds it alternates twice per second. The card returns to its selected highlight when the countdown ends.",[29,7871,7872],{},"When the countdown reaches zero, everyone hears the same end sound as the retrospective countdown, subject to their sound setting. Pressing the forward button while the countdown still has time left plays the same end sound for everyone right away, whether the countdown is running or paused. Reaching zero alone does not pass the work item. The moderator passes it by pressing the forward button, or by selecting another work item or clearing the selection after the countdown ran out. The passed work item then shows the green check on its card and in both tables.",[29,7874,7875],{},"The passed checks are shared, so every participant sees the same green checks without a reload. They belong to the planning session and the selected board, sprint, or filter.",[21,7877,7879],{"id":7878},"planning-session-progress","Planning session progress",[12,7881,7882,7883,7885],{},"The planning session progress bar sits at the bottom of the standup, below the action bar and to the left of the side panel. It shows how much of the planning session has elapsed, the time until it starts or the time remaining, and a ",[16,7884,2162],{}," state once the end date has passed.",[12,7887,7888],{},"Standup data is kept for 12 hours after the last change. Each planning session keeps one record for its shared selection and one set of records for each board and sprint, or for each filter. Older standup data is removed automatically.",{"title":153,"searchDepth":154,"depth":154,"links":7890},[7891,7892,7893,7894,7895,7896,7897,7898,7899,7900,7901,7902,7903,7904,7905],{"id":6512,"depth":154,"text":6513},{"id":7154,"depth":154,"text":7155},{"id":7209,"depth":154,"text":7210},{"id":7269,"depth":154,"text":7270},{"id":7285,"depth":154,"text":7286},{"id":7355,"depth":154,"text":7356},{"id":7375,"depth":154,"text":7376},{"id":7391,"depth":154,"text":7392},{"id":7460,"depth":154,"text":7461},{"id":7021,"depth":154,"text":7022},{"id":7599,"depth":154,"text":7600},{"id":7771,"depth":154,"text":7772},{"id":7802,"depth":154,"text":7803},{"id":7842,"depth":154,"text":7843},{"id":7878,"depth":154,"text":7879},"Run a daily standup in Jira: review the sprint board, flag blockers, move statuses and keep a shared speaking order.","Sprint standups","\u002Fog\u002Fguide-sprint-standups.jpg",[7910,7911,7912],"daily standup","sprint standup","jira standup",{},15,"\u002Fgetting-started\u002Fsprint-standups",{"title":7111,"description":7906},{"loc":7915,"lastmod":802},"sprint-standups","guide\u002Fen\u002Fsprint-standups","guide\u002Fsprint-standups","KhlYqMMmhDBToVDozBl0yOiJXza38DOzQDytXMAhSJs",[7923,7996,8068,8194,8284,8462,8577,8696,8845,8957,9060,9160,9459,9704,9850,9939,10227],{"id":7924,"title":7925,"body":7926,"dateModified":7980,"datePublished":7980,"description":7981,"extension":162,"heading":7982,"image":7983,"imageAlt":7982,"keywords":7984,"locale":168,"meta":7987,"navigation":170,"order":171,"path":7988,"section":7989,"seo":7990,"sitemap":7991,"slug":7992,"stem":7993,"translationKey":7994,"__hash__":7995},"tutorials\u002Ftutorials\u002Fen\u002Fcard-voting.md","Voting with cards | Tutorials | Scrumpy Planning Poker",{"type":9,"value":7927,"toc":7975},[7928,7931,7935,7938,7942,7946,7958,7963,7967,7970],[12,7929,7930],{},"Voting with cards takes just a few clicks: set up your team once, start a session, and let everyone pick their estimate.",[21,7932,7934],{"id":7933},"set-up-your-team-once","Set up your team once",[12,7936,7937],{},"Before any voting starts, a space administrator sets up the moderators and voters for the space. This is a one-time step: Scrumpy remembers the team for every session after that. Everyone else can watch the session and see the results, but only voters cast cards and only moderators run the session.",[61,7939],{"alt":7940,"caption":5235,"stem":7941},"The Permissions tab in space settings with the Voters and Moderators fields filled in","tutorial-permissions",[21,7943,7945],{"id":7944},"start-a-session-and-vote","Start a session and vote",[12,7947,7948,7949,7951,7952,7954,7955,7957],{},"Once you are a moderator, press ",[16,7950,313],{}," in the work item panel and the session begins. Participants pick the card that matches their estimate and cast it. When the discussion is over, the moderator finalizes the session: ",[16,7953,509],{}," the calculated estimate, or ",[16,7956,1308],{}," the result with the number the team agreed on.",[61,7959],{"alt":7960,"caption":7961,"stem":7962},"The estimation panel with the card deck and the Start button","Start and vote","tutorial-cards-ad-hoc",[21,7964,7966],{"id":7965},"make-the-cards-yours","Make the cards yours",[12,7968,7969],{},"The deck fits the way your team estimates. Turn individual cards on or off, give them your own titles, and even upload custom images. Voters then see only the options you chose, so every vote stays quick and focused.",[61,7971],{"alt":7972,"caption":7973,"stem":7974},"Card settings with the card sequence, the available cards, and their custom titles","Card settings","tutorial-cards-configure",{"title":153,"searchDepth":154,"depth":154,"links":7976},[7977,7978,7979],{"id":7933,"depth":154,"text":7934},{"id":7944,"depth":154,"text":7945},{"id":7965,"depth":154,"text":7966},"2026-10-26","Vote with cards in Scrumpy: set up the team once, start a session and accept or override the estimate.","Voting with cards","\u002Fog\u002Ftutorial-card-voting.jpg",[7985,7986,2109],"planning poker cards","card voting",{},"\u002Ftutorials\u002Fcard-voting","tutorial",{"title":7925,"description":7981},{"loc":7988,"lastmod":7980},"card-voting","tutorials\u002Fen\u002Fcard-voting","tutorial\u002Fcard-voting","OxrCEEfNkztwuicNXVgmtWWUifGbtX2fWDWxra_eBZU",{"id":7997,"title":7998,"body":7999,"dateModified":7980,"datePublished":7980,"description":8054,"extension":162,"heading":8055,"image":8056,"imageAlt":8055,"keywords":8057,"locale":168,"meta":8060,"navigation":170,"order":154,"path":8061,"section":7989,"seo":8062,"sitemap":8063,"slug":8064,"stem":8065,"translationKey":8066,"__hash__":8067},"tutorials\u002Ftutorials\u002Fen\u002Ffree-scale-voting.md","Voting on a free scale | Tutorials | Scrumpy Planning Poker",{"type":9,"value":8000,"toc":8050},[8001,8004,8008,8025,8030,8034,8046],[12,8002,8003],{},"A free scale keeps the cards out of the way and lets the team pick an estimate with a slider. It takes a minute to set up and one click to vote.",[21,8005,8007],{"id":8006},"set-up-the-free-scale","Set up the free scale",[12,8009,8010,8011,8014,8015,8017,8018,430,8021,8024],{},"In the perspective settings, choose ",[16,8012,8013],{},"Free scale"," in the ",[16,8016,1220],{}," dropdown. Then set the ",[16,8019,8020],{},"Free scale minimum",[16,8022,8023],{},"Free scale maximum",": every value between them becomes available to voters, so the range fits the kind of work your team estimates. The preview below the fields shows the slider your voters will see.",[61,8026],{"alt":8027,"caption":8028,"stem":8029},"Perspective settings with the Free scale sequence selected and the minimum and maximum fields filled in","Free scale settings","tutorial-free-scale-configure",[21,8031,8033],{"id":8032},"vote-with-the-slider","Vote with the slider",[12,8035,8036,8037,8039,8040,8042,8043,8045],{},"During a session, each voter moves the slider to the estimate that feels right and presses ",[16,8038,2303],{},". The number appears above the slider with an ",[16,8041,1286],{}," suffix. Change your mind? Move the slider again and vote again, or press ",[16,8044,2310],{}," to take the vote back.",[61,8047],{"alt":8048,"caption":8033,"stem":8049},"The estimation panel with the free scale slider, the selected value, and the Vote and Withdraw buttons","tutorial-free-scale",{"title":153,"searchDepth":154,"depth":154,"links":8051},[8052,8053],{"id":8006,"depth":154,"text":8007},{"id":8032,"depth":154,"text":8033},"Estimate on a free scale in Scrumpy, from a slider to precise values, and write the result to Jira.","Voting on a free scale","\u002Fog\u002Ftutorial-free-scale-voting.jpg",[8058,8059,166],"free scale voting","estimation scale",{},"\u002Ftutorials\u002Ffree-scale-voting",{"title":7998,"description":8054},{"loc":8061,"lastmod":7980},"free-scale-voting","tutorials\u002Fen\u002Ffree-scale-voting","tutorial\u002Ffree-scale-voting","Uy_fQVxLPK6bl8fSLzAqFmpWnBDKUY8yqeQCYu-nsd8",{"id":8069,"title":8070,"body":8071,"dateModified":8179,"datePublished":7980,"description":8180,"extension":162,"heading":8181,"image":8182,"imageAlt":8181,"keywords":8183,"locale":168,"meta":8186,"navigation":170,"order":784,"path":8187,"section":7989,"seo":8188,"sitemap":8189,"slug":8190,"stem":8191,"translationKey":8192,"__hash__":8193},"tutorials\u002Ftutorials\u002Fen\u002Fparametric-voting.md","Voting with 2 parameters | Tutorials | Scrumpy Planning Poker",{"type":9,"value":8072,"toc":8174},[8073,8076,8080,8118,8123,8127,8144,8148,8152,8169],[12,8074,8075],{},"Some work is easier to describe with more than one number. A parametric perspective combines several parameters with a formula and turns them into one story point result.",[21,8077,8079],{"id":8078},"set-up-the-parameters","Set up the parameters",[12,8081,8010,8082,8014,8084,8086,8087,430,8089,8092,8093,8096,8097,8100,8101,8104,8105,8108,8109,8111,8112,8114,8115,8117],{},[16,8083,1339],{},[16,8085,1220],{}," dropdown. Name the two parameters ",[16,8088,896],{},[16,8090,8091],{},"Value",", give each one a ",[16,8094,8095],{},"Minimum",", a ",[16,8098,8099],{},"Maximum",", and a ",[16,8102,8103],{},"Step",", then write the ",[16,8106,8107],{},"Formula"," from the variable names shown beside the fields, for example ",[604,8110,1374],{}," where ",[604,8113,1367],{}," is Risk and ",[604,8116,1370],{}," is Value. The preview at the bottom shows the sliders and the result your team will see. Add more parameters when two are not enough.",[61,8119],{"alt":8120,"caption":8121,"stem":8122},"Perspective settings with the Parametric sequence, two parameters, and the formula","Parameter settings","tutorial-parametric-configure",[21,8124,8126],{"id":8125},"vote-with-the-sliders","Vote with the sliders",[12,8128,8129,8130,430,8132,8134,8135,8137,8138,8140,8141,8143],{},"During a session, each voter moves the ",[16,8131,896],{},[16,8133,8091],{}," sliders to the values that fit the work. The formula turns those positions into the result shown in large text with an ",[16,8136,1286],{}," suffix, and a small badge on the right shows how far the rounded result is from the exact formula value. Press ",[16,8139,2303],{}," to cast it, or ",[16,8142,2310],{}," to take it back.",[61,8145],{"alt":8146,"caption":8126,"stem":8147},"The voting panel with two parameter sliders, the result, the deviation badge, and the Vote and Withdraw buttons","tutorial-parametric",[21,8149,8151],{"id":8150},"read-the-results","Read the results",[12,8153,930,8154,8156,8157,8159,8160,8162,8163,8165,8166,8168],{},[16,8155,1466],{}," tab draws one dot per participant, so you can see how the votes spread across ",[16,8158,896],{}," on the horizontal axis and ",[16,8161,8091],{}," on the vertical axis, plus a dashed crosshair for the averaged positions. ",[16,8164,1597],{}," averages the results each participant voted, while ",[16,8167,612],{}," averages every parameter position first and then applies the formula. The moderator can also override the default averaging method and the final result before accepting.",[61,8170],{"alt":8171,"caption":8172,"stem":8173},"The Quadrant tab with participant dots and the averaged crosshair, above the Override, Averaging, and Override averaging method controls","Quadrant results","tutorial-parametric-results",{"title":153,"searchDepth":154,"depth":154,"links":8175},[8176,8177,8178],{"id":8078,"depth":154,"text":8079},{"id":8125,"depth":154,"text":8126},{"id":8150,"depth":154,"text":8151},"2026-11-02","Vote on two parameters at once, such as value and effort, and combine them into one estimate.","Voting with 2 parameters","\u002Fog\u002Ftutorial-parametric-voting.jpg",[8184,8185,166],"parametric estimation","two parameter voting",{},"\u002Ftutorials\u002Fparametric-voting",{"title":8070,"description":8180},{"loc":8187,"lastmod":8179},"parametric-voting","tutorials\u002Fen\u002Fparametric-voting","tutorial\u002Fparametric-voting","EhSG0Z-zoBeseXjyGKCs9c0MgMPBbErtVRUVNSYw8XU",{"id":8195,"title":8196,"body":8197,"dateModified":8179,"datePublished":7980,"description":8271,"extension":162,"heading":8272,"image":8273,"imageAlt":8272,"keywords":8274,"locale":168,"meta":8276,"navigation":170,"order":2112,"path":8277,"section":7989,"seo":8278,"sitemap":8279,"slug":8280,"stem":8281,"translationKey":8282,"__hash__":8283},"tutorials\u002Ftutorials\u002Fen\u002Fparametric-3-voting.md","Voting with 3+ parameters | Tutorials | Scrumpy Planning Poker",{"type":9,"value":8198,"toc":8266},[8199,8202,8204,8227,8231,8233,8242,8246,8248,8261],[12,8200,8201],{},"When one number is not enough, a parametric perspective can combine three, four, or more parameters with a formula and turn them into one story point result.",[21,8203,8079],{"id":8078},[12,8205,8010,8206,8014,8208,8210,8211,8213,8214,8096,8216,8100,8218,8104,8220,8222,8223,8226],{},[16,8207,1339],{},[16,8209,1220],{}," dropdown and add as many parameters as the work needs with ",[16,8212,1356],{},". Give each one a name, a ",[16,8215,8095],{},[16,8217,8099],{},[16,8219,8103],{},[16,8221,8107],{}," from the parameter names shown beside the fields, for example ",[604,8224,8225],{},"(p1 + sqrt(p2) + 2 + p3 + p4 + p5) \u002F 5",". The preview at the bottom shows every slider and the result your team will see.",[61,8228],{"alt":8229,"caption":8121,"stem":8230},"Perspective settings with the Parametric sequence, three parameters, and the formula","tutorial-parametric-3-configure",[21,8232,8126],{"id":8125},[12,8234,8235,8236,8137,8238,8140,8240,8143],{},"During a session, each voter moves every parameter to the value that fits the work. The formula turns those positions into the result shown in large text with an ",[16,8237,1286],{},[16,8239,2303],{},[16,8241,2310],{},[61,8243],{"alt":8244,"caption":8126,"stem":8245},"The voting panel with one slider per parameter, the result, the deviation badge, and the Vote and Withdraw buttons","tutorial-parametric-3",[21,8247,8151],{"id":8150},[12,8249,8250,8251,8253,8254,8256,8257,8165,8259,8168],{},"A perspective with three or more parameters adds a ",[16,8252,1470],{}," tab instead of the two-parameter ",[16,8255,1466],{},": each parameter becomes a ray, and every participant gets one polygon, with a dotted polygon for the averaged positions. ",[16,8258,1597],{},[16,8260,612],{},[61,8262],{"alt":8263,"caption":8264,"stem":8265},"The Radar tab with one polygon per participant and the dotted averaged polygon, above the Override, Averaging, and Override averaging method controls","Radar results","tutorial-parametric-3-results",{"title":153,"searchDepth":154,"depth":154,"links":8267},[8268,8269,8270],{"id":8078,"depth":154,"text":8079},{"id":8125,"depth":154,"text":8126},{"id":8150,"depth":154,"text":8151},"Estimate three or more parameters in one round and review how Scrumpy combines them.","Voting with 3+ parameters","\u002Fog\u002Ftutorial-parametric-3-voting.jpg",[8184,8275],"multi parameter voting",{},"\u002Ftutorials\u002Fparametric-3-voting",{"title":8196,"description":8271},{"loc":8277,"lastmod":8179},"parametric-3-voting","tutorials\u002Fen\u002Fparametric-3-voting","tutorial\u002Fparametric-3-voting","fTV72fdLB_C_c16A38yT1SKNnxYpSpu8ChC1rCI9608",{"id":8285,"title":8286,"body":8287,"dateModified":8179,"datePublished":7980,"description":8448,"extension":162,"heading":8449,"image":8450,"imageAlt":8449,"keywords":8451,"locale":168,"meta":8454,"navigation":170,"order":3014,"path":8455,"section":7989,"seo":8456,"sitemap":8457,"slug":8458,"stem":8459,"translationKey":8460,"__hash__":8461},"tutorials\u002Ftutorials\u002Fen\u002Fvoting-with-time.md","Voting with time | Tutorials | Scrumpy Planning Poker",{"type":9,"value":8288,"toc":8438},[8289,8292,8296,8302,8306,8310,8313,8315,8318,8323,8326,8332,8337,8339,8342,8347,8351,8357,8362,8366,8369,8396,8401,8419,8424,8433],[12,8290,8291],{},"Some teams find it easier to think in hours than in abstract story points. Scrumpy keeps the card, free-scale, or parameter estimate and can show the equivalent time beside it, so the team can estimate the way it works while the result still lands in days and hours. The time appears only when the perspective writes to a time-based board or a Time field, and the last section shows how to set that up.",[21,8293,8295],{"id":8294},"set-the-conversion-from-your-project-history","Set the conversion from your project history",[12,8297,8298,8299,8301],{},"Open the perspective settings and find ",[16,8300,1294],{},". To choose the factor, look at a few recent completed work items: add up the time they actually took and divide it by the story points they were estimated at. Use that average (for example, 1 point = 8 hours) so the time estimate reflects how your team really works rather than a generic guess.",[61,8303],{"alt":8304,"caption":1294,"stem":8305},"Perspective settings with the Story points to hours field set to the project's conversion factor","tutorial-time-estimate-configure",[21,8307,8309],{"id":8308},"vote-with-cards-a-free-scale-or-parameters","Vote with cards, a free scale, or parameters",[12,8311,8312],{},"The conversion works with every voting style.",[233,8314,913],{"id":1201},[12,8316,8317],{},"With cards, the result labels show each vote in the units the perspective writes: story points on a numeric board or a story points field, the duration on a time board or a Time field, and both when the target writes a time value next to the story points.",[61,8319],{"alt":8320,"caption":8321,"stem":8322},"A card voting result with story points and time labels and the Override field showing both","Card result","tutorial-time-estimate-cards",[233,8324,8013],{"id":8325},"free-scale",[12,8327,8328,8329,8331],{},"With the free scale, the slider preview above ",[16,8330,2303],{}," shows story points on a numeric board or a story points field. A time board or a Time field shows the duration, and a Field target with both a story points field and a Time field shows both.",[61,8333],{"alt":8334,"caption":8335,"stem":8336},"The free scale slider with the selected story points and time above the Vote button","Free scale vote","tutorial-time-estimate-free-scale",[233,8338,612],{"id":611},[12,8340,8341],{},"With parameters, the calculated result below the sliders shows story points on a numeric board or a story points field. A time board or a Time field shows the duration, and a Field target with both a story points field and a Time field shows both.",[61,8343],{"alt":8344,"caption":8345,"stem":8346},"The parametric sliders with the calculated story points and time below them","Parametric vote","tutorial-time-estimate-parameters",[21,8348,8350],{"id":8349},"read-the-result","Read the result",[12,8352,8353,8354,8356],{},"When the session completes, the result chart, the vote list, and the moderator's ",[16,8355,1308],{}," field show the result in the units the perspective writes. On a time board or a Time field that is the duration; when the target writes both story points and time, they appear together, and choosing a different override updates the time beside it.",[61,8358],{"alt":8359,"caption":8360,"stem":8361},"A free scale result chart with time labels and an Override field showing the story points and time","Completed result","tutorial-time-estimate-free-scale-result",[21,8363,8365],{"id":8364},"make-the-time-estimate-reach-jira","Make the time estimate reach Jira",[12,8367,8368],{},"Scrumpy shows the time value only when the perspective writes it to a Jira time field. Set up one of these before you vote.",[12,8370,8371,8374,8375,4066,8378,8380,8381,8383,8384,8387,8388,8391,8392,8395],{},[16,8372,8373],{},"Use a time field as the target."," Set ",[16,8376,8377],{},"Estimation target",[16,8379,1312],{},", then choose a Jira time field under ",[16,8382,1316],{},", for example ",[16,8385,8386],{},"Original estimate",". The ",[16,8389,8390],{},"Story points field"," can stay ",[16,8393,8394],{},"None"," when the team only wants the time written.",[61,8397],{"alt":8398,"caption":8399,"stem":8400},"The Estimation target set to Field with the Time field set to Original estimate","Time field target","tutorial-time-estimate-configure-field",[12,8402,8403,8374,8406,4066,8408,8410,8411,8414,8415,8418],{},[16,8404,8405],{},"Use the board's time estimate.",[16,8407,8377],{},[16,8409,1566],{},", pick the board the team plans with, and then open ",[16,8412,8413],{},"Configure this board's estimation settings"," in Jira and set the board's estimation method to a time statistic such as ",[16,8416,8417],{},"Original time estimate",". With the default target, Scrumpy sends the result to the board and the board decides which field stores it.",[61,8420],{"alt":8421,"caption":8422,"stem":8423},"The Estimation target set to Default with the board estimation statistic set to Time Estimate","Default board target","tutorial-time-estimate-configure-board",[12,8425,8426,8427,8430,8431,569],{},"In the Jira board settings, set the ",[16,8428,8429],{},"Estimation method"," to a time statistic such as ",[16,8432,8417],{},[61,8434],{"alt":8435,"caption":8436,"stem":8437},"The Jira board estimation method set to Original time estimate","Jira board estimation","tutorial-configure-time-estimate-board-jira",{"title":153,"searchDepth":154,"depth":154,"links":8439},[8440,8441,8446,8447],{"id":8294,"depth":154,"text":8295},{"id":8308,"depth":154,"text":8309,"children":8442},[8443,8444,8445],{"id":1201,"depth":784,"text":913},{"id":8325,"depth":784,"text":8013},{"id":611,"depth":784,"text":612},{"id":8349,"depth":154,"text":8350},{"id":8364,"depth":154,"text":8365},"Estimate effort in hours and days instead of story points, with time cards, a time field and duration results.","Voting with time","\u002Fog\u002Ftutorial-voting-with-time.jpg",[8452,8453,2109],"time estimation","hour estimates",{},"\u002Ftutorials\u002Fvoting-with-time",{"title":8286,"description":8448},{"loc":8455,"lastmod":8179},"voting-with-time","tutorials\u002Fen\u002Fvoting-with-time","tutorial\u002Fvoting-with-time","CNFPsWyj97bFnrQs4SftgRf5YI5g1rKBuq3Li3rBQ-8",{"id":8463,"title":8464,"body":8465,"dateModified":8560,"datePublished":8561,"description":8562,"extension":162,"heading":8563,"image":8564,"imageAlt":8563,"keywords":8565,"locale":168,"meta":8569,"navigation":170,"order":3175,"path":8570,"section":7989,"seo":8571,"sitemap":8572,"slug":8573,"stem":8574,"translationKey":8575,"__hash__":8576},"tutorials\u002Ftutorials\u002Fen\u002Fvoting-with-tshirts.md","Voting with T-shirts | Tutorials | Scrumpy Planning Poker",{"type":9,"value":8466,"toc":8555},[8467,8470,8474,8485,8488,8497,8502,8506,8509,8522,8533,8538,8543,8547,8550],[12,8468,8469],{},"T-shirt sizes keep a session short: voters pick a size instead of arguing over a number. Scrumpy turns the size into a story point value you control, so the estimate still fits the team's scale and can be written to Jira.",[21,8471,8473],{"id":8472},"set-the-sizes-and-their-story-points","Set the sizes and their story points",[12,8475,8476,8477,1535,8479,8481,8482,8484],{},"Open the perspective settings and choose ",[16,8478,1534],{},[16,8480,1220],{},". Tick the sizes the team uses under ",[16,8483,1230],{},". Only the ticked cards appear during voting, so a short list keeps the session focused.",[12,8486,8487],{},"Each card has a story point value beside it. Change a number to match the team's scale. The values must grow from the first card to the last, so edit the list from the bottom upward when you need wider gaps. These values are the story points Scrumpy uses for the result and for Jira.",[12,8489,8490,8491,8493,8494,569],{},"When ",[16,8492,1294],{}," is set in the same tab and the perspective writes a time value, the result also shows the converted duration beside the size, for example ",[16,8495,8496],{},"1 sp · 1 day 2 hours · M",[61,8498],{"alt":8499,"caption":8500,"stem":8501},"The Available cards list for a T-shirt perspective with the story points beside each size","T-shirt cards and story points","tutorial-tshirt-configure",[21,8503,8505],{"id":8504},"write-the-result-to-one-or-two-jira-fields","Write the result to one or two Jira fields",[12,8507,8508],{},"A T-shirt vote can update two Jira fields:",[26,8510,8511,8517],{},[29,8512,930,8513,8516],{},[16,8514,8515],{},"story points field",", using the story point value configured for the chosen size (for example, S = 10).",[29,8518,930,8519,8521],{},[16,8520,1646],{},", with the size label (for example, S).",[12,8523,8524,8525,4066,8527,8529,8530,8532],{},"Set ",[16,8526,8377],{},[16,8528,1312],{},", then choose the fields you want. Choose both to update both. Leave a field as ",[16,8531,8394],{}," when the team does not use it.",[61,8534],{"alt":8535,"caption":8536,"stem":8537},"The Estimation target set to Field with the Story points field and the T-shirt field","Story points and T-shirt fields","tutorial-tshirt-configure-field",[12,8539,2451,8540,8542],{},[16,8541,1566],{}," as the target, the accepted estimate goes to the board's estimation field as the mapped story point value, and the T-shirt field can still receive the size label when it is set.",[21,8544,8546],{"id":8545},"vote-with-the-size-cards","Vote with the size cards",[12,8548,8549],{},"When the moderator starts a session, voters see only the sizes you ticked. Each voter taps a card, and the panel shows who has voted. The moderator pauses, resumes, or completes the session as usual. When the estimate is accepted, Scrumpy writes the size label, the mapped story points, or both, depending on the fields you set.",[61,8551],{"alt":8552,"caption":8553,"stem":8554},"The voting panel with the T-shirt size cards","Voting with T-shirt cards","tutorial-tshirt",{"title":153,"searchDepth":154,"depth":154,"links":8556},[8557,8558,8559],{"id":8472,"depth":154,"text":8473},{"id":8504,"depth":154,"text":8505},{"id":8545,"depth":154,"text":8546},"2026-10-31","2026-10-29","Size work with T-shirt cards, optionally mapped to story points and time, directly in your Jira board.","Voting with T-shirts","\u002Fog\u002Ftutorial-voting-with-tshirts.jpg",[8566,8567,8568],"t-shirt sizing","t shirt estimation","agile sizing",{},"\u002Ftutorials\u002Fvoting-with-tshirts",{"title":8464,"description":8562},{"loc":8570,"lastmod":8560},"voting-with-tshirts","tutorials\u002Fen\u002Fvoting-with-tshirts","tutorial\u002Fvoting-with-tshirts","-PvkZpXyh5ZpLS6tSG4ept2o2G7zNhCI0u_pSGBE3AE",{"id":8578,"title":8579,"body":8580,"dateModified":8561,"datePublished":8561,"description":8682,"extension":162,"heading":8673,"image":8683,"imageAlt":8673,"keywords":8684,"locale":168,"meta":8688,"navigation":170,"order":3463,"path":8689,"section":7989,"seo":8690,"sitemap":8691,"slug":8692,"stem":8693,"translationKey":8694,"__hash__":8695},"tutorials\u002Ftutorials\u002Fen\u002Fvoting-with-custom-cards.md","Voting with custom cards | Tutorials | Scrumpy Planning Poker",{"type":9,"value":8581,"toc":8675},[8582,8585,8589,8605,8610,8613,8617,8625,8629,8633,8636,8642,8646,8655,8660,8663,8667,8670],[12,8583,8584],{},"You can re-brand the whole voting board to match the team's standards: the card values, the titles, the story points on a T-shirt deck, and the artwork. Voters then see a deck that speaks the team's language instead of the built-in one.",[21,8586,8588],{"id":8587},"every-card-set-is-customizable","Every card set is customizable",[12,8590,8591,8592,334,8594,334,8596,334,8598,334,8600,917,8602,8604],{},"Titles and custom images work on every card-based sequence: ",[16,8593,2216],{},[16,8595,2226],{},[16,8597,2236],{},[16,8599,2246],{},[16,8601,2256],{},[16,8603,1534],{},". Pick the sequence first, then change its titles, choose the active cards, and upload artwork. The same steps apply to each set.",[12,8606,8607,8609],{},[16,8608,1534],{}," adds one more setting. Its cards are size labels instead of numbers, so each size also has an editable story point value. The other card sets already carry a fixed number on every card, so they do not show a story point field.",[12,8611,8612],{},"This tutorial uses a T-shirt perspective because it shows both customizations, but you can follow the title and image steps on any card set.",[21,8614,8616],{"id":8615},"start-with-a-t-shirt-perspective","Start with a T-shirt perspective",[12,8618,8476,8619,1535,8621,8481,8623,8484],{},[16,8620,1534],{},[16,8622,1220],{},[16,8624,1230],{},[61,8626],{"alt":8627,"caption":8500,"stem":8628},"The Available cards list for a T-shirt perspective with the selected sizes and their story points","tutorial-custom-cards-configure",[21,8630,8632],{"id":8631},"change-the-titles-and-the-story-points-on-t-shirt","Change the titles, and the story points on T-Shirt",[12,8634,8635],{},"Each card has a title field beside its preview. Replace the built-in title with the team's own name for that card. A custom title must contain at least one letter and must be unique within the sequence; the small reset control restores the built-in title. This works the same on every card set.",[12,8637,8638,8639,8641],{},"On ",[16,8640,1534],{},", each size also has a story point value. Set the numbers so they grow from the first card to the last, and edit from the bottom upward when you need wider gaps. These values are what Scrumpy uses for the result and for the Jira story points field. The other card sets keep their fixed numeric value and show no story point field.",[21,8643,8645],{"id":8644},"upload-custom-card-images","Upload custom card images",[12,8647,8648,8649,2537,8651,8654],{},"Click any card preview in ",[16,8650,1230],{},[16,8652,8653],{},"Available extra cards"," to open the upload dialog. This works on every card set. Choose a PNG or JPG image up to 293 kB with a width to height ratio of 1:1.5, for example 400 by 600 pixels. The same dialog removes a custom image and restores the built-in artwork.",[61,8656],{"alt":8657,"caption":8658,"stem":8659},"The Upload card image dialog with the file browser and the PNG or JPG limits","Upload card image","tutorial-custom-cards-configure-images",[12,8661,8662],{},"Custom images are kept per card and per sequence, so the same value in two sequences can carry different artwork. Only people who can manage the space can upload or remove an image, and the image belongs to this space.",[21,8664,8666],{"id":8665},"vote-with-the-custom-board","Vote with the custom board",[12,8668,8669],{},"When a session runs, voters see the custom titles and artwork on the cards they can pick. A custom title also appears in the card tooltip and replaces the value on the minimalistic card visuals. The moderator starts, pauses, resumes, or completes the session as usual, and the accepted estimate uses the story point value behind the chosen card.",[61,8671],{"alt":8672,"caption":8673,"stem":8674},"The voting panel with custom titles and custom card artwork","Voting with custom cards","tutorial-custom-cards",{"title":153,"searchDepth":154,"depth":154,"links":8676},[8677,8678,8679,8680,8681],{"id":8587,"depth":154,"text":8588},{"id":8615,"depth":154,"text":8616},{"id":8631,"depth":154,"text":8632},{"id":8644,"depth":154,"text":8645},{"id":8665,"depth":154,"text":8666},"Build your own planning poker deck: custom card titles, images and story point values for each card.","\u002Fog\u002Ftutorial-voting-with-custom-cards.jpg",[8685,8686,8687],"custom cards","planning poker deck","estimation cards",{},"\u002Ftutorials\u002Fvoting-with-custom-cards",{"title":8579,"description":8682},{"loc":8689,"lastmod":8561},"voting-with-custom-cards","tutorials\u002Fen\u002Fvoting-with-custom-cards","tutorial\u002Fvoting-with-custom-cards","ZmpaQYUlevOG4WnHeCljXE5_e-LcTChoQmaCOffDKgs",{"id":8697,"title":8698,"body":8699,"dateModified":8179,"datePublished":8179,"description":8831,"extension":162,"heading":8832,"image":8833,"imageAlt":8832,"keywords":8834,"locale":168,"meta":8837,"navigation":170,"order":4846,"path":8838,"section":7989,"seo":8839,"sitemap":8840,"slug":8841,"stem":8842,"translationKey":8843,"__hash__":8844},"tutorials\u002Ftutorials\u002Fen\u002Festimation-log.md","Reading the estimation log | Tutorials | Scrumpy Planning Poker",{"type":9,"value":8700,"toc":8823},[8701,8704,8708,8718,8721,8726,8732,8736,8739,8777,8782,8788,8792,8795,8799,8802,8806,8813,8817],[12,8702,8703],{},"Every time a moderator accepts an estimate, Scrumpy records it in the estimation log for that work item. The log keeps the sizing decisions of the last 90 days, so you can see how an estimate changed over time, which perspective produced each value, and who took part.",[21,8705,8707],{"id":8706},"find-the-log-on-a-work-item","Find the log on a work item",[12,8709,8710,8711,4872,8713,4876,8715,8717],{},"Open the work item in Jira, expand the ",[16,8712,4871],{},[16,8714,4875],{},[16,8716,4879],{},". The log lists the accepted estimates for the work item, newest first.",[12,8719,8720],{},"If the space has a password, enter it first: the log asks for the space password before it shows any entries. Scrumpy also checks that you can open the work item in Jira, so a work item hidden from you by Jira issue-level security shows no history.",[61,8722],{"alt":8723,"caption":8724,"stem":8725},"The estimation log on a work item","The estimation log","tutorial-estimation-log",[12,8727,8728,8729,8731],{},"A space administrator can hide the log by hiding both the Scrumpy panel on work items and the ",[16,8730,250],{}," page in space settings. While either one is shown, the log stays available.",[21,8733,8735],{"id":8734},"read-an-entry","Read an entry",[12,8737,8738],{},"Each entry is one accepted estimate:",[26,8740,8741,8746,8754,8759,8764,8772],{},[29,8742,8743,8745],{},[16,8744,4918],{},": the avatar of the person who accepted the estimate",[29,8747,8748,8750,8751],{},[16,8749,465],{},": how many of the required voters had voted, such as ",[16,8752,8753],{},"100% of required voters",[29,8755,8756,8758],{},[16,8757,3251],{},": which estimation perspective produced the value",[29,8760,8761,8763],{},[16,8762,884],{},": when the estimate was accepted, in your Jira timezone",[29,8765,8766,8768,8769],{},[16,8767,4934],{},": how long the vote took, for example ",[16,8770,8771],{},"for 4 minutes",[29,8773,8774,8776],{},[16,8775,4940],{},": the accepted value in a badge, then every vote in the deck's labels and the people who cast them",[12,8778,8779,8780,569],{},"The result badge is green when the accepted value matches the computed average. If the moderator chose a different value before accepting, the badge is yellow and hovering it shows ",[16,8781,4953],{},[12,8783,8784,8785,8787],{},"Values follow the perspective: story points carry the ",[16,8786,1286],{}," suffix, a T-shirt perspective shows the size labels, and a time perspective shows a work-day duration.",[21,8789,8791],{"id":8790},"move-through-the-history","Move through the history",[12,8793,8794],{},"The log shows 5 entries per page by default. Use the page numbers at the bottom to move through older estimates, and the selector beside them to show 5, 10, 15, or 20 entries per page. Changing the page size returns you to page one. The order never changes: the most recent accepted estimate is always at the top.",[21,8796,8798],{"id":8797},"watch-the-log-during-a-session","Watch the log during a session",[12,8800,8801],{},"When someone accepts an estimate for the work item while the log is open, the new entry appears at the top without a reload. If you are reading an older page, the log returns to page one so the new entry is visible. In a password-protected space, live updates start after you enter the space password.",[21,8803,8805],{"id":8804},"see-the-trend-across-the-space","See the trend across the space",[12,8807,8808,8809,8812],{},"The estimation log is per work item. To see the whole space, open ",[16,8810,8811],{},"Space settings > Dashboard",", where accepted estimates are grouped into charts by perspective and by day, with the average certainty, variation, voting time, and number of voters. Use the range selector to focus on the last weeks or on all time.",[21,8814,8816],{"id":8815},"know-how-long-the-history-stays","Know how long the history stays",[12,8818,8819,8820,8822],{},"Entries are kept for three months (90 days), then removed automatically. A space owner can clear every estimation log entry for the space at once from the space settings ",[16,8821,355],{}," tab; that action cannot be undone. Archiving a planning session to Confluence keeps its estimates on a Confluence page beyond the 90 days.",{"title":153,"searchDepth":154,"depth":154,"links":8824},[8825,8826,8827,8828,8829,8830],{"id":8706,"depth":154,"text":8707},{"id":8734,"depth":154,"text":8735},{"id":8790,"depth":154,"text":8791},{"id":8797,"depth":154,"text":8798},{"id":8804,"depth":154,"text":8805},{"id":8815,"depth":154,"text":8816},"Read the estimation log: what is recorded for each accepted estimate and how long the history is kept.","Reading the estimation log","\u002Fog\u002Ftutorial-estimation-log.jpg",[8835,5039,8836],"estimation log","jira reporting",{},"\u002Ftutorials\u002Festimation-log",{"title":8698,"description":8831},{"loc":8838,"lastmod":8179},"estimation-log","tutorials\u002Fen\u002Festimation-log","tutorial\u002Festimation-log","gvxokZmR6GM9dzZGhZslUowlV8TY17qXctdhUNS8IHA",{"id":8846,"title":8847,"body":8848,"dateModified":802,"datePublished":8179,"description":8946,"extension":162,"heading":3498,"image":8947,"imageAlt":3498,"keywords":8948,"locale":168,"meta":8950,"navigation":170,"order":5043,"path":8951,"section":7989,"seo":8952,"sitemap":8953,"slug":3487,"stem":8954,"translationKey":8955,"__hash__":8956},"tutorials\u002Ftutorials\u002Fen\u002Fcreating-a-planning-session.md","Creating a planning session | Tutorials | Scrumpy Planning Poker",{"type":9,"value":8849,"toc":8940},[8850,8853,8857,8872,8876,8884,8888,8892,8895,8914,8920,8924,8927,8930,8935],[12,8851,8852],{},"In Scrum, a planning session is the grooming or refinement session: the regular time the team sets aside to discuss upcoming work items and estimate them together. Scrumpy keeps the session, its work items, and the team's estimation perspectives in one place, so the discussion and the estimates stay together.",[21,8854,8856],{"id":8855},"open-the-planning-sessions-page","Open the planning sessions page",[12,8858,8859,8860,8862,8863,8865,8866,8868,8869,8871],{},"Go to the space page and open the ",[16,8861,340],{}," tab. A moderator presses ",[16,8864,568],{}," above the session tabs, then gives the session a name, a short description, and a schedule. Use ",[16,8867,2216],{}," for a start time plus a duration such as 30 minutes, or ",[16,8870,3522],{}," when the session has a specific end time. The planned time is the refinement window, and the header shows how much of it is left while the team estimates.",[21,8873,8875],{"id":8874},"add-the-work-items","Add the work items",[12,8877,1353,8878,8880,8881,8883],{},[16,8879,3695],{},", choose a saved Jira filter, tick the work items you want, and press ",[16,8882,3765],{},". A filter is the quickest way to bring in a backlog slice, for example the next sprint's stories or a saved query for defects. You can add more work items later, and the same filter can be reused for the next session.",[61,8885],{"alt":8886,"caption":7210,"stem":8887},"The Add work items from filter dialog with a saved filter and ten work items selected","tutorial-planning-add-from-filter",[21,8889,8891],{"id":8890},"give-each-estimation-style-a-perspective","Give each estimation style a perspective",[12,8893,8894],{},"Each perspective is a column in the planning table, and the same work item can be estimated in every one of them. This session shows three perspectives:",[26,8896,8897,8902,8908],{},[29,8898,8899,8901],{},[16,8900,884],{}," uses a free scale and writes the result to a board that estimates in time.",[29,8903,8904,8907],{},[16,8905,8906],{},"Scrum"," uses Fibonacci cards, limited here to 1, 2, 3 and 5, plus the infinity and coffee cards.",[29,8909,8910,8913],{},[16,8911,8912],{},"Bugs"," uses T-shirt sizes.",[12,8915,8916,8917,8919],{},"Use ",[16,8918,3835],{}," to hide the perspectives the team does not need for this session. The choice belongs to the session, so the table stays focused on the work at hand.",[21,8921,8923],{"id":8922},"estimate-one-work-item-or-many","Estimate one work item or many",[12,8925,8926],{},"Work through the table one work item at a time, or tick several work items and use the actions above the table to start, pause, resume, complete, accept, or cancel voting for all of them. The work item you select in presenter mode opens in the panel on the right, where the team votes with the controls of the active perspective.",[12,8928,8929],{},"The example below has all ten work items selected, the sessions for Time, Scrum, and Bugs started and then paused, and the first work item open in the Scrum panel. From here the team can estimate the next work item, resume the sessions, or complete them in bulk when the discussion is over.",[61,8931],{"alt":8932,"caption":8933,"stem":8934},"The planning session with ten work items, three perspectives, all rows selected, sessions paused, and the selected work item's card panel open","A planning session with three perspectives","tutorial-planning-session",[61,8936],{"alt":8937,"caption":8938,"stem":8939},"The selected work item's card voting panel with the session paused","The selected work item's voting panel","tutorial-planning-voting-panel",{"title":153,"searchDepth":154,"depth":154,"links":8941},[8942,8943,8944,8945],{"id":8855,"depth":154,"text":8856},{"id":8874,"depth":154,"text":8875},{"id":8890,"depth":154,"text":8891},{"id":8922,"depth":154,"text":8923},"Create a planning session in Jira, add work items and move from a backlog to accepted estimates.","\u002Fog\u002Ftutorial-creating-a-planning-session.jpg",[2386,4841,8949],"jira backlog",{},"\u002Ftutorials\u002Fcreating-a-planning-session",{"title":8847,"description":8946},{"loc":8951,"lastmod":802},"tutorials\u002Fen\u002Fcreating-a-planning-session","tutorial\u002Fcreating-a-planning-session","w-hJTeMuUDnb3c1VJk3ZNG-EQYYx6Du2uCmvpC0oI0o",{"id":8958,"title":8959,"body":8960,"dateModified":8179,"datePublished":8179,"description":9046,"extension":162,"heading":9047,"image":9048,"imageAlt":9047,"keywords":9049,"locale":168,"meta":9052,"navigation":170,"order":5167,"path":9053,"section":7989,"seo":9054,"sitemap":9055,"slug":9056,"stem":9057,"translationKey":9058,"__hash__":9059},"tutorials\u002Ftutorials\u002Fen\u002Fauditing-and-dashboards.md","Auditing and dashboards | Tutorials | Scrumpy Planning Poker",{"type":9,"value":8961,"toc":9040},[8962,8965,8969,8975,8978,8982,8988,8992,8998,9008,9012,9016,9024,9028,9033,9037],[12,8963,8964],{},"When you need to know what happened in a space, you do not have to ask around. Space settings keeps two audit logs and the full dashboard for the space. You need permission to manage the space in Jira to open them, and Scrumpy checks that permission again when the data loads.",[21,8966,8968],{"id":8967},"follow-a-voting-session-from-start-to-finish","Follow a voting session from start to finish",[12,8970,930,8971,8974],{},[16,8972,8973],{},"Voting audit"," tab lists every significant voting event in the space, newest first: a session started, a vote cast or withdrawn, a pause or resume, a completion, the team estimate, an accepted estimate, a change to the required voters, a reminder, and the async voting deadline.",[12,8976,8977],{},"Each row shows when the event happened, the work item type and key, the perspective, who did it, and what happened. Click a work item key to open the work item in a dialog without leaving the page.",[61,8979],{"alt":8980,"caption":8973,"stem":8981},"The Voting audit tab with recent voting events and the actor for each event","tutorial-voting-audit",[12,8983,8984,8985,8987],{},"Use the search field for a work item key, a perspective, or an event description, then click ",[16,8986,3269],{},". Choose 15, 30, 45, or 60 rows per page. You only see events for work items you can open in Jira; hidden work items are left out and are not counted.",[21,8989,8991],{"id":8990},"see-who-changed-the-settings","See who changed the settings",[12,8993,930,8994,8997],{},[16,8995,8996],{},"Configuration audit"," tab records every change to the space permissions and to the perspective settings. It covers the voter and moderator lists, the password, page visibility, the Confluence space, and every perspective setting. A perspective added, renamed, or removed also appears here.",[12,8999,9000,9001,2537,9004,9007],{},"Each row shows who made the change, which perspective it belongs to, what changed, and when. The description reads like ",[16,9002,9003],{},"Certainty enabled",[16,9005,9006],{},"Active cards changed for Fibonacci",", so you can see the exact difference without opening the setting.",[61,9009],{"alt":9010,"caption":8996,"stem":9011},"The Configuration audit tab with the actor, the perspective, and the change description","tutorial-config-audit",[21,9013,9015],{"id":9014},"visualize-the-voting-activity","Visualize the voting activity",[12,9017,930,9018,9020,9021,9023],{},[16,9019,355],{}," tab in Space settings turns accepted sessions into charts for the space. It shows the total votes and estimates per perspective, the average certainty and variation, the average active and paused time, and the same numbers per day. Use the range selector to switch between 1, 2, 4, or 8 weeks and ",[16,9022,3335],{},"; the choice is remembered in this browser tab.",[61,9025],{"alt":9026,"caption":355,"stem":9027},"The Dashboard tab with the range selector and the voting activity charts","tutorial-dashboard",[12,9029,930,9030,9032],{},[16,9031,355],{}," tab on the Estimations page is a lighter live view. It shows active sessions, unique voters, and sessions by state per perspective, plus the people voting right now. It has no time filter.",[21,9034,9036],{"id":9035},"keep-the-history","Keep the history",[12,9038,9039],{},"Voting audit entries, configuration audit entries, and accepted sessions are kept for 90 days, then removed automatically. Only the space owner can clear an audit log or the estimation log from these tabs. A confirmation appears first, and those deletions cannot be undone.",{"title":153,"searchDepth":154,"depth":154,"links":9041},[9042,9043,9044,9045],{"id":8967,"depth":154,"text":8968},{"id":8990,"depth":154,"text":8991},{"id":9014,"depth":154,"text":9015},{"id":9035,"depth":154,"text":9036},"Use the voting audit and dashboards to see participation, vote changes and estimation trends over time.","Auditing and dashboards","\u002Fog\u002Ftutorial-auditing-and-dashboards.jpg",[3459,9050,9051],"estimation dashboard","agile metrics",{},"\u002Ftutorials\u002Fauditing-and-dashboards",{"title":8959,"description":9046},{"loc":9053,"lastmod":8179},"auditing-and-dashboards","tutorials\u002Fen\u002Fauditing-and-dashboards","tutorial\u002Fauditing-and-dashboards","1Bqy4Uocd5zeK1r8FAdqEC_Xy1gEVcFBwu86ozbXlB8",{"id":9061,"title":9062,"body":9063,"dateModified":8179,"datePublished":8179,"description":9147,"extension":162,"heading":9148,"image":9149,"imageAlt":9148,"keywords":9150,"locale":168,"meta":9153,"navigation":170,"order":5210,"path":9154,"section":7989,"seo":9155,"sitemap":9156,"slug":4056,"stem":9157,"translationKey":9158,"__hash__":9159},"tutorials\u002Ftutorials\u002Fen\u002Fbulk-voting.md","Bulk voting in a planning session | Tutorials | Scrumpy Planning Poker",{"type":9,"value":9064,"toc":9141},[9065,9068,9072,9087,9092,9096,9108,9113,9117,9120,9124,9136],[12,9066,9067],{},"A planning session is the team's grooming or refinement meeting. Its table is a spreadsheet for estimation: one row per work item, one column per perspective, and one estimate cell for every pair.",[21,9069,9071],{"id":9070},"fill-the-table-in-bulk-voting","Fill the table in Bulk voting",[12,9073,9074,9075,9077,9078,9080,9081,9083,9084,9086],{},"Switch the session to ",[16,9076,3815],{},". Every started session shows its control directly in the table: a card selector for ",[16,9079,8906],{},", a T-shirt selector for ",[16,9082,8912],{},", and a number field for ",[16,9085,884],{},". Choose a value and the vote is cast for that work item and perspective, without opening the work item.",[61,9088],{"alt":9089,"caption":9090,"stem":9091},"The planning session in Bulk voting with card, size, and number controls in the table","Bulk voting in the planning table","tutorial-bulk-voting-table",[21,9093,9095],{"id":9094},"vote-with-buckets","Vote with buckets",[12,9097,9098,9099,9101,9102,9104,9105,9107],{},"Select the ",[16,9100,8906],{}," perspective row and open the ",[16,9103,1493],{}," tab. Each card is a bucket. Drag a work item under the card that fits, or drop it under ",[16,9106,7472],{}," to withdraw its vote. The bucket view shows the same votes as the table, grouped by card.",[61,9109],{"alt":9110,"caption":9111,"stem":9112},"The Bucket voting tab with work items placed under the Scrum cards","Bucket voting","tutorial-bulk-voting-buckets",[21,9114,9116],{"id":9115},"it-does-not-matter-where-the-vote-is-cast","It does not matter where the vote is cast",[12,9118,9119],{},"Participants can vote from the work item's ad-hoc panel, from the planning table, or from the Bucket tab by dragging. All three write the same vote for the work item and perspective, so the moderator reviews the same result everywhere. From the planning table the moderator can start, pause, resume, complete, cancel, or accept sessions in bulk.",[21,9121,9123],{"id":9122},"accept-the-estimates","Accept the estimates",[12,9125,9126,9127,9129,9130,9132,9133,9135],{},"Select all work items, choose ",[16,9128,8906],{}," in the perspective selector, and press ",[16,9131,491],{},". Then press ",[16,9134,509],{},". Scrumpy writes each accepted estimate to the Jira field the perspective targets, and the planning table shows the accepted value in the Scrum column.",[61,9137],{"alt":9138,"caption":9139,"stem":9140},"The planning session after accepting the Scrum estimates, with the values in the table","Accepted estimates in the planning table","tutorial-bulk-voting-accepted",{"title":153,"searchDepth":154,"depth":154,"links":9142},[9143,9144,9145,9146],{"id":9070,"depth":154,"text":9071},{"id":9094,"depth":154,"text":9095},{"id":9115,"depth":154,"text":9116},{"id":9122,"depth":154,"text":9123},"Estimate a whole backlog in one table, edit several work items at once and accept results in bulk.","Bulk voting in a planning session","\u002Fog\u002Ftutorial-bulk-voting.jpg",[4843,9151,9152],"backlog estimation","planning poker table",{},"\u002Ftutorials\u002Fbulk-voting",{"title":9062,"description":9147},{"loc":9154,"lastmod":8179},"tutorials\u002Fen\u002Fbulk-voting","tutorial\u002Fbulk-voting","UUL82KHZSZCCWLnlVgMUC8e-CH2FSfRs8qSJXyLUpIU",{"id":9161,"title":9162,"body":9163,"dateModified":6480,"datePublished":8179,"description":9445,"extension":162,"heading":9446,"image":9447,"imageAlt":9446,"keywords":9448,"locale":168,"meta":9451,"navigation":170,"order":5561,"path":9452,"section":7989,"seo":9453,"sitemap":9454,"slug":9455,"stem":9456,"translationKey":9457,"__hash__":9458},"tutorials\u002Ftutorials\u002Fen\u002Faffinity-and-dot-ranking.md","Affinity and Dot ranking | Tutorials | Scrumpy Planning Poker",{"type":9,"value":9164,"toc":9434},[9165,9168,9184,9188,9204,9207,9211,9225,9231,9245,9250,9254,9262,9265,9273,9278,9282,9298,9304,9321,9324,9329,9333,9349,9352,9356,9365,9374,9378,9398,9406,9410,9415,9418,9422,9425],[12,9166,9167],{},"A team does not always need an estimate to agree on what matters most. Affinity ranking asks every participant to put the work items in order. Dot voting gives every participant a small budget of dots, and the dots decide the order. Scrumpy then uses that order in the Bucket voting table, where the team can estimate the work items without losing it.",[12,9169,9170,9171,9173,9174,334,9176,917,9178,9180,9181,9183],{},"This tutorial continues the setup from ",[16,9172,3498],{},": ten work items, the ",[16,9175,884],{},[16,9177,8906],{},[16,9179,8912],{}," perspectives, and three participants. It uses the ",[16,9182,8906],{}," perspective.",[21,9185,9187],{"id":9186},"open-the-ranking-panel","Open the ranking panel",[12,9189,9190,9191,9193,9194,9196,9197,334,9199,917,9201,9203],{},"Open the planning session and switch the edit mode to ",[16,9192,3815],{},". A row for each perspective appears below the work items. Select the radio beside ",[16,9195,8906],{},". The panel on the right opens with ",[16,9198,1487],{},[16,9200,1490],{},[16,9202,1493],{}," tabs, the perspective title and description, a settings gear, your role badge, and the sound bell.",[12,9205,9206],{},"Only voters can rank. A guest sees the same tables read-only.",[21,9208,9210],{"id":9209},"rank-with-affinity","Rank with Affinity",[12,9212,6545,9213,9215,9216,9218,9219,9221,9222,9224],{},[16,9214,1487],{}," tab. Drag a work item up or down to change its position. Every move is saved as you drag and shared live, so the other participants see your order at once. The table keeps your own order. ",[16,9217,4291],{}," is your position, ",[16,9220,1175],{}," is your distance from the agreed position, and ",[16,9223,4310],{}," is the agreed position. A positive deviation means the team ranked the work item above your position, and a negative one means it ranked it below.",[12,9226,9227,9228,9230],{},"Every listed work item takes part, even when you never moved it. Below the table you see the participants who have ranked. ",[16,9229,2310],{}," removes your ranking.",[12,9232,9233,9234,2537,9236,9238,9239,9241,9242,9244],{},"A moderator chooses the agreed position with ",[16,9235,4239],{},[16,9237,4243],{}," beside the perspective title. ",[16,9240,4239],{}," averages the positions, and ",[16,9243,4243],{}," uses the middle position.",[61,9246],{"alt":9247,"caption":9248,"stem":9249},"The Affinity tab after three participants ranked ten work items","The Affinity panel with three participants","tutorial-affinity-ranking",[21,9251,9253],{"id":9252},"rank-with-dots","Rank with dots",[12,9255,6545,9256,9258,9259,9261],{},[16,9257,1490],{}," tab. Each participant can place one dot on a work item, and placing the same dot again removes it. A work item's rank is the total number of dots it receives from all participants. The ",[16,9260,4310],{}," column shows that total.",[12,9263,9264],{},"The dot budget is the number of dots each participant can give. It is one dot per work item by default, so ten dots for ten work items, and a moderator can lower it. A moderator can also share one budget between all participants; dots are then given first come, first served. The moderator sees the number field, and everyone sees the dots-left badge. In this example each participant spent between five and eight dots.",[12,9266,9267,9269,9270,9272],{},[16,9268,2310],{}," removes all of your dots. The ",[16,9271,1462],{}," tab of both rankings shows a chart: the agreed position for Affinity and the dot count for Dot.",[61,9274],{"alt":9275,"caption":9276,"stem":9277},"The Dot tab after three participants spent between five and eight dots each","The Dot panel with three participants","tutorial-dot-ranking",[21,9279,9281],{"id":9280},"rank-the-bucket-table","Rank the bucket table",[12,9283,6545,9284,9286,9287,9289,9290,2537,9292,9294,9295,9297],{},[16,9285,1493],{}," tab. The dropdown beside the perspective title reads ",[16,9288,4151],{}," by default. Choose ",[16,9291,4536],{},[16,9293,4539],{}," once at least one participant has submitted that ranking. The table then lists the work items from the best rank to the worst and adds a ",[16,9296,4310],{}," column. The card rows keep their configured order.",[12,9299,9300,9301,9303],{},"Work items with the same rank can be reordered inside the same card row or inside ",[16,9302,4468],{},", but they cannot cross a work item with a different rank. Dragging a work item under a card can change more than one row, because the table keeps the rank order:",[26,9305,9306,9312,9315],{},[29,9307,9308,9309,9311],{},"Drop onto ",[16,9310,4468],{}," to clear the dropped work item and the better-ranked carded work items above it.",[29,9313,9314],{},"Drop onto a better card, higher in the table, to move the dropped work item and the better-ranked carded work items it passes under that card.",[29,9316,9317,9318,9320],{},"Drop onto a worse card, lower in the table, or out of ",[16,9319,4468],{},", to move the dropped work item and the worse-ranked work items that land under that card.",[12,9322,9323],{},"Work items with the same rank as the dropped work item never move with it. Only the dropped work item changes card among its rank peers. Every work item that lands under a card takes that card's estimate, so the whole group is estimated together.",[61,9325],{"alt":9326,"caption":9327,"stem":9328},"The Bucket tab with Affinity ranking, the ranked work items in the No estimate group, and the Rank column","The Bucket tab with Affinity ranking","tutorial-bucket-ranking",[21,9330,9332],{"id":9331},"changing-the-ranking-clears-the-bucket-votes","Changing the ranking clears the bucket votes",[12,9334,9335,9336,4066,9338,2537,9340,9342,9343,9345,9346,9348],{},"Switching from ",[16,9337,4151],{},[16,9339,4536],{},[16,9341,4539],{},", or between the two, resets the votes in the Bucket table and returns every work item to ",[16,9344,4468],{},". The change appears at once, and if it cannot be saved, the previous ranking and votes return. Switching back to ",[16,9347,4151],{}," keeps the votes you have.",[12,9350,9351],{},"Once the enforced ranking has a vote or a completed session in the Bucket table, its own tab locks. You cannot rerank the Affinity table, place or remove dots, or withdraw, and the algorithm selector becomes read-only. Change the enforced ranking to unlock it. The other ranking stays editable.",[21,9353,9355],{"id":9354},"sync-the-rankings-with-jira","Sync the rankings with Jira",[12,9357,9358,9361,9362,9364],{},[16,9359,9360],{},"Affinity:"," only a moderator sees the ",[16,9363,4347],{}," arrow. Scrumpy uses the rank field configured on the board you opened the space page from. If Jira does not report a board, or the board does not configure a rank field, Jira's default rank field is used. Press the arrow and Scrumpy writes the agreed order, not your own order, into the Jira rank. The top work item keeps its place and the rest are ranked after it, so the listed work items become one ranked block. If Jira refuses the change, an error appears below the controls and you can try again. You need permission to rank work items in Jira.",[12,9366,9367,9370,9371,9373],{},[16,9368,9369],{},"Dots:"," every participant presses the ",[16,9372,4347],{}," arrow in their own Dot panel. Scrumpy adds or removes your Jira vote on each listed work item so it matches your dots. Each participant syncs their own votes. This changes the Jira votes, not the estimates. If some work items fail, an error appears and you can try again.",[21,9375,9377],{"id":9376},"reset-a-ranking","Reset a ranking",[26,9379,9380,9385,9393],{},[29,9381,9382,9384],{},[16,9383,2310],{}," removes your own ranking or all of your dots.",[29,9386,9387,9389,9390,9392],{},[16,9388,4147],{},", the delete icon beside ",[16,9391,2310],{},", is for a moderator and deletes the rankings for everyone on that tab.",[29,9394,1342,9395,9397],{},[16,9396,4151],{}," in the Bucket tab to stop enforcing a ranking.",[12,9399,9400,9401,9403,9404,569],{},"If the ranking you clear was the enforced one, the Bucket tab returns to ",[16,9402,4151],{}," by itself. With a completed session, the Bucket tab allows only ",[16,9405,4151],{},[21,9407,9409],{"id":9408},"when-the-rankings-are-deleted","When the rankings are deleted",[12,9411,9412,9413,569],{},"Cancelling or accepting a work item's voting session removes that work item from both rankings. When you accept the estimates and close the last voting session, both rankings for that perspective are deleted and the enforced ranking returns to ",[16,9414,4151],{},[12,9416,9417],{},"Completing a session does not delete its ranking. The completed work item keeps its place, and the enforced order stays locked until you cancel or accept that session.",[21,9419,9421],{"id":9420},"completed-sessions-lock-the-bucket-table","Completed sessions lock the bucket table",[12,9423,9424],{},"A completed session stays in the Bucket table with its recorded vote, so you can compare it with the others. It cannot be moved or re-estimated.",[12,9426,9427,9428,9430,9431,9433],{},"When a ranking is enforced and at least one voting session is completed, the whole Bucket table is locked. You cannot drag work items or press ",[16,9429,2310],{},", and the ranking dropdown allows only ",[16,9432,4151],{},". Cancel or accept the completed sessions to unlock the table.",{"title":153,"searchDepth":154,"depth":154,"links":9435},[9436,9437,9438,9439,9440,9441,9442,9443,9444],{"id":9186,"depth":154,"text":9187},{"id":9209,"depth":154,"text":9210},{"id":9252,"depth":154,"text":9253},{"id":9280,"depth":154,"text":9281},{"id":9331,"depth":154,"text":9332},{"id":9354,"depth":154,"text":9355},{"id":9376,"depth":154,"text":9377},{"id":9408,"depth":154,"text":9409},{"id":9420,"depth":154,"text":9421},"Group work items by affinity and rank them with dot voting to speed up large refinements.","Affinity and Dot ranking","\u002Fog\u002Ftutorial-affinity-and-dot-ranking.jpg",[9449,9450,4842],"affinity ranking","dot voting",{},"\u002Ftutorials\u002Faffinity-and-dot-ranking",{"title":9162,"description":9445},{"loc":9452,"lastmod":6480},"affinity-and-dot-ranking","tutorials\u002Fen\u002Faffinity-and-dot-ranking","tutorial\u002Faffinity-and-dot-ranking","rcWzwNos5qn1ewoWDRh93HZS_38wLdC3_wwXb-YKeio",{"id":9460,"title":9461,"body":9462,"dateModified":8179,"datePublished":8179,"description":9689,"extension":162,"heading":9690,"image":9691,"imageAlt":9690,"keywords":9692,"locale":168,"meta":9696,"navigation":170,"order":6488,"path":9697,"section":7989,"seo":9698,"sitemap":9699,"slug":9700,"stem":9701,"translationKey":9702,"__hash__":9703},"tutorials\u002Ftutorials\u002Fen\u002Funderstanding-charts.md","Understanding the charts | Tutorials | Scrumpy Planning Poker",{"type":9,"value":9463,"toc":9682},[9464,9467,9471,9490,9495,9505,9523,9528,9531,9536,9539,9542,9545,9554,9559,9562,9565,9568,9576,9581,9584,9587,9591,9606,9610,9613,9616,9635,9638,9642,9654,9659,9662,9665,9679],[12,9465,9466],{},"Charts turn the votes of a session into a picture. The estimate itself never changes when you switch charts: every chart shows the same votes in a different shape, so you can choose the view that makes agreement, spread, and outliers easiest to read. The charts are pictures only. They cannot be clicked, dragged, or focused.",[21,9468,9470],{"id":9469},"the-result-chart","The result chart",[12,9472,9473,9474,9476,9477,9479,9480,334,9483,917,9486,9489],{},"Open a completed session and select ",[16,9475,1462],{},". While open voting is running, ",[16,9478,1462],{}," updates as votes arrive. The chart counts how many participants voted each value. With the three votes ",[16,9481,9482],{},"2 sp",[16,9484,9485],{},"5 sp",[16,9487,9488],{},"8 sp",", it shows three equal parts or bars.",[61,9491],{"alt":9492,"caption":9493,"stem":9494},"A pie chart with one vote each for 2, 5, and 8 story points","Pie result chart","tutorial-chart-pie",[12,9496,9497,9498,334,9500,917,9502,9504],{},"The pie legend sits below the chart and lists ",[16,9499,9482],{},[16,9501,9485],{},[16,9503,9488],{},", one colour for each voted value. A larger slice means that more participants chose that value. Three equal slices mean the team split evenly.",[12,9506,9507,9508,9511,9512,9515,9516,334,9518,4178,9520,9522],{},"Your chart type is personal and does not change anyone else's view. Open your Jira avatar menu, choose ",[16,9509,9510],{},"Scrumpy Poker",", find ",[16,9513,9514],{},"Chart type",", and select ",[16,9517,2757],{},[16,9519,2763],{},[16,9521,2769],{},". The choice follows you across spaces and applies to every result you open.",[61,9524],{"alt":9525,"caption":9526,"stem":9527},"A vertical bar chart with one vote each for 2, 5, and 8 story points","Vertical bar result chart","tutorial-chart-vertical-bar",[12,9529,9530],{},"The vertical bar chart keeps the same three votes. Its legend sits above the chart, the card values are on the horizontal axis, and the bar height is the number of voters. It is easier to compare two values that are close together.",[61,9532],{"alt":9533,"caption":9534,"stem":9535},"A horizontal bar chart with one vote each for 2, 5, and 8 story points","Horizontal bar result chart","tutorial-chart-horizontal-bar",[12,9537,9538],{},"The horizontal bar chart turns the same bars on their side. The card values are on the left, the bar length is the number of voters, and long labels stay readable.",[12,9540,9541],{},"Use the pie for a quick share at a glance, the vertical bars to compare close values, and the horizontal bars when the labels are long.",[21,9543,1466],{"id":9544},"quadrant",[12,9546,9547,9548,9550,9551,9553],{},"A perspective with two parameters shows a ",[16,9549,1466],{}," tab after ",[16,9552,1462],{}," once the session completes. Each axis is one parameter, drawn with its real values, including negative ones.",[61,9555],{"alt":9556,"caption":9557,"stem":9558},"A quadrant chart with three voters and the averaged position","Quadrant chart","tutorial-chart-quadrant",[12,9560,9561],{},"Each dot is one participant's vote at its pair of parameter values. The dashed crosshair marks the averaged position calculated from the recorded votes. The chart has no legend: the colours keep the dots apart, but they do not map a dot to a person. That is deliberate, because the chart shows how the votes compare, not who cast them.",[12,9563,9564],{},"Read a cluster of dots as agreement, a wide spread as a discussion that is still open, and a dot far from the crosshair as an outlier. The quadrant is useful when two factors decide the estimate, for example risk and value.",[21,9566,1470],{"id":9567},"radar",[12,9569,9570,9571,9550,9573,9575],{},"A perspective with three or more parameters shows a ",[16,9572,1470],{},[16,9574,1462],{}," once the session completes. Each ray is one parameter, scaled from its minimum at the centre to its maximum on the outer ring.",[61,9577],{"alt":9578,"caption":9579,"stem":9580},"A radar chart with three voters and the averaged polygon","Radar chart","tutorial-chart-radar",[12,9582,9583],{},"Each participant is one polygon. A corner pulled toward the outer ring means a high value on that parameter. The dotted polygon is the averaged position calculated from the recorded votes. The chart has no legend, so read the shapes rather than looking for names.",[12,9585,9586],{},"Overlapping polygons mean the team agrees on the profile. A polygon that pulls away on one ray shows where the disagreement sits. The radar is useful when several parameters describe the estimate at once.",[21,9588,9590],{"id":9589},"heat-map","Heat map",[12,9592,9593,9594,9596,9597,9599,9600,9602,9603,9605],{},"Open a planning session, switch the edit mode to ",[16,9595,3815],{},", select a card perspective such as ",[16,9598,8906],{},", open the ",[16,9601,1493],{}," tab, and select ",[16,9604,1462],{},". The heat map compares every listed work item in one picture.",[61,9607],{"alt":9608,"caption":9590,"stem":9609},"A heat map with three voters across ten work items","tutorial-chart-heatmap",[12,9611,9612],{},"Rows are the work items and columns are the cards of the perspective. The number inside a cell is how many participants chose that card for that work item. The colour runs from light orange at one vote to dark red at the highest count, and a grey cell means nobody voted that card.",[12,9614,9615],{},"The heat map has no legend. The card labels and the numbers in the cells are the key:",[26,9617,9618,9625,9632],{},[29,9619,9620,9621,9624],{},"A dark cell with ",[16,9622,9623],{},"3"," means all three voters agree.",[29,9626,9627,9628,9631],{},"Three separate ",[16,9629,9630],{},"1"," cells in a row mean the team split three ways.",[29,9633,9634],{},"A grey row means the work item has no votes yet.",[12,9636,9637],{},"Use it to spot the work items that need another round of discussion and the ones that are already settled.",[21,9639,9641],{"id":9640},"scatter","Scatter",[12,9643,9644,9645,9647,9648,9650,9651,9653],{},"Open the same ",[16,9646,1493],{}," tab for a free-scale perspective such as ",[16,9649,884],{}," and select ",[16,9652,1462],{},". The scatter chart compares the story points voted for every listed work item.",[61,9655],{"alt":9656,"caption":9657,"stem":9658},"A scatter chart with three voters across ten work items","Scatter chart","tutorial-chart-scatter",[12,9660,9661],{},"Rows are the work items, the horizontal axis is story points, and every dot is one vote. Dots of the same work item share a colour, and votes at the same value fan out vertically so none is hidden. The dashed cross marks the averaged story points for that work item, and it appears only when more than one vote exists.",[12,9663,9664],{},"The scatter chart has no legend. Read each row from left to right:",[26,9666,9667,9670,9673,9676],{},[29,9668,9669],{},"Dots close together mean the team agrees on that work item.",[29,9671,9672],{},"Dots spread far apart mean the estimates differ, and the work item needs discussion.",[29,9674,9675],{},"The dashed cross is the average that becomes the estimate.",[29,9677,9678],{},"A dot far from the cross is an outlier worth talking about.",[12,9680,9681],{},"The heat map answers what card the team chose. The scatter answers how far apart the numbers are. Together they show agreement across a whole planning session at a glance.",{"title":153,"searchDepth":154,"depth":154,"links":9683},[9684,9685,9686,9687,9688],{"id":9469,"depth":154,"text":9470},{"id":9544,"depth":154,"text":1466},{"id":9567,"depth":154,"text":1470},{"id":9589,"depth":154,"text":9590},{"id":9640,"depth":154,"text":9641},"Read the estimation charts: pie, bar, radar, scatter, quadrant and heatmap views of a vote.","Understanding the charts","\u002Fog\u002Ftutorial-understanding-charts.jpg",[9693,9694,9695,9051],"estimation charts","heatmap","scatter plot",{},"\u002Ftutorials\u002Funderstanding-charts",{"title":9461,"description":9689},{"loc":9697,"lastmod":8179},"understanding-charts","tutorials\u002Fen\u002Funderstanding-charts","tutorial\u002Funderstanding-charts","5yoIYYZbaXtR0HixB8a1KIP-qKjmY_9_kuDp-7ZXYUg",{"id":9705,"title":9706,"body":9707,"dateModified":159,"datePublished":159,"description":9840,"extension":162,"heading":343,"image":9841,"imageAlt":343,"keywords":9842,"locale":168,"meta":9843,"navigation":170,"order":7101,"path":9844,"section":7989,"seo":9845,"sitemap":9846,"slug":393,"stem":9847,"translationKey":9848,"__hash__":9849},"tutorials\u002Ftutorials\u002Fen\u002Fcapacity-planning.md","Capacity planning | Tutorials | Scrumpy Planning Poker",{"type":9,"value":9708,"toc":9830},[9709,9712,9716,9728,9732,9735,9739,9746,9751,9755,9758,9763,9767,9778,9782,9785,9788,9793,9797,9802,9806,9810,9815,9819,9825],[12,9710,9711],{},"Capacity planning helps your team see how much work fits into the next sprints before you commit to it. Scrumpy compares the work you plan with the capacity your team really has, so the conversation starts from numbers instead of guesses.",[21,9713,9715],{"id":9714},"start-with-the-sprints-you-finished","Start with the sprints you finished",[12,9717,9718,9719,9721,9722,9724,9725,9727],{},"Open the space page and choose the ",[16,9720,343],{}," tab. Select your planning session, then select ",[16,9723,399],{},". In the ",[16,9726,5657],{}," tab, tick the closed sprints that should set your team's velocity. Three past sprints give a steady average. Each past sprint should include the work the team completed, and its team should be filled in.",[61,9729],{"alt":9730,"caption":5657,"stem":9731},"The Plan sprint dialog with three past sprints selected","tutorial-capacity-plan-sprint-past",[12,9733,9734],{},"If you are starting for the first time and there are no past sprints, you can still plan. Add the team to the sprint you want to plan, set each person's utilization and hours of work, and Scrumpy calculates the target from that team. Add past sprints later to get a velocity.",[21,9736,9738],{"id":9737},"add-the-active-and-future-sprints-you-want-to-plan","Add the active and future sprints you want to plan",[12,9740,6545,9741,9743,9744,569],{},[16,9742,5663],{}," tab in the same dialog and tick the active or future sprints you want to include. You can plan several sprints at once, so the team can compare the next few weeks in one view. Select ",[16,9745,3765],{},[61,9747],{"alt":9748,"caption":9749,"stem":9750},"The Sprints tab of the Plan sprint dialog with an active sprint selected","Active and future sprints","tutorial-capacity-plan-sprint-future",[21,9752,9754],{"id":9753},"the-board-selector-decides-which-sprints-you-can-plan","The board selector decides which sprints you can plan",[12,9756,9757],{},"This part is important. The sprint picker only lists sprints that originated from the board currently chosen in the board selector at the top left of the capacity table. Switch the board and the list changes. Each board keeps its own plan, so choose the board first, then add its sprints.",[61,9759],{"alt":9760,"caption":9761,"stem":9762},"The board selector at the top left of the capacity planning page","Board selector","tutorial-capacity-board-selector",[21,9764,9766],{"id":9765},"add-and-remove-work-items","Add and remove work items",[12,9768,9769,9770,9772,9773,9775,9776,569],{},"With a sprint selected in the table, use ",[16,9771,3695],{}," to bring in work items from a saved Jira filter, a sprint, or a Refinement\u002Fgrooming session. Drag a work item to reorder it inside its sprint, or drag it onto another sprint row to move it. To remove items, tick them and select ",[16,9774,4017],{},". Removing an item changes the plan, not Jira, until you select ",[16,9777,3592],{},[21,9779,9781],{"id":9780},"read-the-capacity-timeline","Read the capacity timeline",[12,9783,9784],{},"In this example the planned sprint has seven work items. Their estimates are 1, 2, 3, 5, 8, 5, and 3 story points. The timeline adds them up as you read down the table. Green means there is room, yellow means you are close to the healthy range, and red means the running total is above the capacity your team has.",[12,9786,9787],{},"If the later work items sit behind a red line, the plan is too big for this team. Remove an item, lower an estimate, or add capacity before you start the sprint.",[61,9789],{"alt":9790,"caption":9791,"stem":9792},"The capacity table with seven work items and the timeline turning red above capacity","Capacity timeline","tutorial-capacity-timeline",[21,9794,9796],{"id":9795},"set-up-the-team","Set up the team",[12,9798,6545,9799,9801],{},[16,9800,6014],{}," tab. This example has three team members. Each person has a utilization percentage and hours of work for the sprint. Time off is added in the person's calendar. When you change a value, the target and the timeline update right away.",[61,9803],{"alt":9804,"caption":6014,"stem":9805},"The Team capacity table with three team members and their hours","tutorial-capacity-team",[21,9807,9809],{"id":9808},"agree-on-the-sprint-goal","Agree on the sprint goal",[12,9811,6545,9812,9814],{},[16,9813,5670],{}," tab to write the sprint goal. Everyone can vote with the thumbs up and thumbs down buttons, and the counts update for the whole team. A clear goal helps the team agree on what the sprint is for before voting starts.",[21,9816,9818],{"id":9817},"vote-on-a-work-item-and-chat","Vote on a work item and chat",[12,9820,9821,9822,9824],{},"Select a work item in the table, then open a perspective tab to vote with the same cards you use in Refinement\u002Fgrooming. A ",[16,9823,1877],{}," tab appears for the selected work item, so the team can discuss that item without leaving the capacity plan.",[61,9826],{"alt":9827,"caption":9828,"stem":9829},"The perspective voting panel and the Chat tab for a planned work item","Vote and chat","tutorial-capacity-voting-chat",{"title":153,"searchDepth":154,"depth":154,"links":9831},[9832,9833,9834,9835,9836,9837,9838,9839],{"id":9714,"depth":154,"text":9715},{"id":9737,"depth":154,"text":9738},{"id":9753,"depth":154,"text":9754},{"id":9765,"depth":154,"text":9766},{"id":9780,"depth":154,"text":9781},{"id":9795,"depth":154,"text":9796},{"id":9808,"depth":154,"text":9809},{"id":9817,"depth":154,"text":9818},"Plan the next sprints from recent velocity, read the capacity timeline and apply the plan to Jira.","\u002Fog\u002Ftutorial-capacity-planning.jpg",[6484,6485,5884],{},"\u002Ftutorials\u002Fcapacity-planning",{"title":9706,"description":9840},{"loc":9844,"lastmod":159},"tutorials\u002Fen\u002Fcapacity-planning","tutorial\u002Fcapacity-planning","dXqFjEQiGF7gHvaxbkFg7mAJK_PdEsz8aLt9oMCwdxI",{"id":9851,"title":9852,"body":9853,"dateModified":159,"datePublished":159,"description":9924,"extension":162,"heading":9925,"image":9926,"imageAlt":9925,"keywords":9927,"locale":168,"meta":9931,"navigation":170,"order":7914,"path":9932,"section":7989,"seo":9933,"sitemap":9934,"slug":9935,"stem":9936,"translationKey":9937,"__hash__":9938},"tutorials\u002Ftutorials\u002Fen\u002Farchiving.md","Archiving your plans | Tutorials | Scrumpy Planning Poker",{"type":9,"value":9854,"toc":9919},[9855,9858,9862,9876,9881,9884,9888,9898,9903,9906,9910],[12,9856,9857],{},"Archiving keeps a permanent record of a planning session or a capacity plan in Confluence. The team can look back later and see what was estimated, what was planned, and why. A space administrator chooses the Confluence space in space settings before anyone can archive.",[21,9859,9861],{"id":9860},"archive-a-refinement-session","Archive a refinement session",[12,9863,6545,9864,9866,9867,9869,9870,9872,9873,9875],{},[16,9865,340],{}," tab, select the planning session, and select ",[16,9868,5259],{}," next to ",[16,9871,491],{},". The dialog shows the planning window and a preview of the work items with accepted estimates that will be written. Select ",[16,9874,5259],{}," to create the page.",[61,9877],{"alt":9878,"caption":9879,"stem":9880},"The Refinement\u002Fgrooming archive dialog with the preview of accepted estimates","Refinement archive preview","tutorial-archive-planning",[12,9882,9883],{},"The generated page keeps the planning title, description, start and end time, the participants, and every accepted estimate with its perspective, votes, participants, and moderator.",[21,9885,9887],{"id":9886},"archive-a-capacity-plan","Archive a capacity plan",[12,9889,6545,9890,9892,9893,9895,9896,9875],{},[16,9891,343],{}," tab, select an active or future sprint in the combined table, and select ",[16,9894,5259],{}," in the toolbar. The dialog previews the sprint and its dates, the sprint goal and its votes, the capacity decision, and the velocity summary. The team and work item tables are written to the page as well. Select ",[16,9897,5259],{},[61,9899],{"alt":9900,"caption":9901,"stem":9902},"The Capacity planning archive dialog with the sprint summary and velocity","Capacity archive preview","tutorial-archive-capacity",[12,9904,9905],{},"The generated page keeps the planning window, the sprint and goal, the goal votes, the velocity and target capacity, the team with hours and utilization, and the planned work items in order.",[21,9907,9909],{"id":9908},"find-the-pages-later","Find the pages later",[12,9911,9912,9913,9915,9916,9918],{},"Planning session archives sit under the ",[16,9914,250],{}," parent page. Capacity archives sit under the ",[16,9917,5462],{}," parent page, in a child page named after the space and \"Capacity planning\". Archiving the same sprint again updates its page instead of creating a duplicate.",{"title":153,"searchDepth":154,"depth":154,"links":9920},[9921,9922,9923],{"id":9860,"depth":154,"text":9861},{"id":9886,"depth":154,"text":9887},{"id":9908,"depth":154,"text":9909},"Archive planning sessions, capacity plans, stand-ups and retrospectives to Confluence, with a clear page hierarchy.","Archiving your plans","\u002Fog\u002Ftutorial-archiving.jpg",[9928,9929,9930],"confluence archive","planning archive","retrospective archive",{},"\u002Ftutorials\u002Farchiving",{"title":9852,"description":9924},{"loc":9932,"lastmod":159},"archiving","tutorials\u002Fen\u002Farchiving","tutorial\u002Farchiving","LUADFXzNR2iP2wk39AwMP3Kv49FDRx0r3OwXBe_zD0Y",{"id":9940,"title":9941,"body":9942,"dateModified":802,"datePublished":10212,"description":10213,"extension":162,"heading":10214,"image":10215,"imageAlt":10214,"keywords":10216,"locale":168,"meta":10218,"navigation":170,"order":10219,"path":10220,"section":7989,"seo":10221,"sitemap":10222,"slug":10223,"stem":10224,"translationKey":10225,"__hash__":10226},"tutorials\u002Ftutorials\u002Fen\u002Fleading-a-standup.md","Leading a standup | Tutorials | Scrumpy Planning Poker",{"type":9,"value":9943,"toc":10202},[9944,9950,9954,9968,9973,9976,9978,9981,9984,9989,9994,9998,10003,10007,10027,10033,10037,10042,10045,10050,10073,10078,10082,10091,10099,10104,10145,10149,10155,10167,10182,10187,10191],[12,9945,9946,9947,9949],{},"A standup is the easiest meeting to run in Scrumpy. Open the tab, pick the running sprint, and talk through the cards in the order the team sees them. Everything you change stays in the standup until you press ",[16,9948,3592],{},", so you can rearrange the board while you talk without touching Jira.",[21,9951,9953],{"id":9952},"pick-the-planning-session-board-and-sprint","Pick the planning session, board, and sprint",[12,9955,6545,9956,9958,9959,9961,9962,9964,9965,9967],{},[16,9957,346],{}," tab and pick a planning session from the tabs above the board. Pick the ",[16,9960,6556],{}," first, then the ",[16,9963,6562],{},". The sprint list only shows the sprints that are running right now, so the standup opens on the work the team is doing today. The sprint name and goal sit above the columns, and the link icon opens the sprint in Jira. When the space has no board, pick a saved ",[16,9966,7183],{}," instead, and the standup shows the work items that filter returns, with one column per status.",[61,9969],{"alt":9970,"caption":9971,"stem":9972},"The board and sprint selectors above the standup","Choose the board and the running sprint","tutorial-standup-sprint",[12,9974,9975],{},"Only a moderator changes the shared board. A voter or guest who picks another sprint does so only for their own browser tab.",[21,9977,7270],{"id":7269},[12,9979,9980],{},"Every column of the board is a lane, in the board's own order. The cards follow the shared standup order, which starts as the order of the sprint in Jira. Each card shows the assignee, the priority, the key as a link, the estimate, and one or two lines of the summary. A card with an estimate shows it as a badge, so the team can see the size without opening Jira. A work item the team has passed shows a small green check right of its key.",[12,9982,9983],{},"In this example the To Do column holds the most work, one card has a red flag, and two cards were already moved while the team talked. The two moved cards carry an undo button next to their checkbox. Three cards carry the green passed check, and the two cards of the absent teammate are gray and dimmed.",[12,9985,8916,9986,9988],{},[16,9987,7193],{}," in the toolbar to cap how many cards a column loads and shows. Work items beyond the cap stay in Jira and are loaded when you raise the cap. A work item the standup already loaded keeps its place and staged changes while it is hidden.",[61,9990],{"alt":9991,"caption":9992,"stem":9993},"The standup board with cards in every column","The sprint as a standup board","tutorial-standup-board",[21,9995,9997],{"id":9996},"flag-a-work-item-that-needs-attention","Flag a work item that needs attention",[12,9999,10000,10001,569],{},"Select the flag at the right of a card to mark it for the team. A card that is already flagged in Jira opens with a red flag. Select it again to clear the flag. The flag shows for everyone right away, and it is written to the Jira Flagged field when you press ",[16,10002,3592],{},[21,10004,10006],{"id":10005},"move-work-items-without-leaving-the-standup","Move work items without leaving the standup",[12,10008,5870,10009,10011,10012,10014,10015,10017,10018,10020,10021,10023,10024,10026],{},[16,10010,7362],{}," dropdown on a card to change its status or its place in the lane. ",[16,10013,7623],{}," offers the statuses the card can reach in Jira, and ",[16,10016,7636],{}," moves the card one place up or down. Select several cards with their checkboxes to move them together. A card with a staged status move keeps ",[16,10019,7623],{}," disabled until you undo or apply that move, while ",[16,10022,7636],{}," stays available. The statuses are read when you open the menu, so the first open can take a moment and shows ",[16,10025,7694],{}," until they arrive.",[12,10028,10029,10030,10032],{},"The change is shared with the team immediately, but it is not written to Jira yet. The moved card shows an undo button next to its checkbox. Select it to remove that staged change right away, without a confirmation and without changing Jira. ",[16,10031,6739],{}," is the button that asks you to confirm before it clears everything.",[21,10034,10036],{"id":10035},"follow-the-same-standup-in-the-status-table","Follow the same standup in the Status table",[12,10038,930,10039,10041],{},[16,10040,5727],{}," tab at the left of the side panel shows the same standup in a second view. It is not another list: every work item of the sprint is there, in the same columns and the same order, with the same flags and the same staged moves. Move a work item in the table and its card moves on the board at the same time.",[12,10043,10044],{},"Each board column is a wide row with its name in the middle, and the work items of that column sit under it. A row shows the work type, the priority, the flag, the key, the green passed check, the undo button, and the estimate, so the whole sprint fits in a short list. That makes the table quick to scan, and sometimes it is simply easier to walk through the work items here than on the board.",[61,10046],{"alt":10047,"caption":10048,"stem":10049},"The Status table with the same work items and staged moves as the board","The same standup as a compact table","tutorial-standup-order",[26,10051,10052,10058,10061,10064,10070],{},[29,10053,10054,10055,10057],{},"Select the round button at the left of a row to make that work item the one under discussion, exactly like clicking its card. Everyone else sees a yellow ",[16,10056,1515],{}," on that row.",[29,10059,10060],{},"Drag a row to change its place in its column, or drop it under another column to move it there when the workflow allows it.",[29,10062,10063],{},"Select the flag to stage a flag, and the undo button to remove a staged change. These are the same buttons and the same staged moves as on the board.",[29,10065,10066,10067,10069],{},"A green check in the narrow column after the key means the team has passed that work item: the moderator forwarded its countdown, or moved the selection on after the countdown ran out. The same check appears next to the key on the card and in the ",[16,10068,6758],{}," table.",[29,10071,10072],{},"A moderator can move and flag every work item, a voter only the work items assigned to them, and a guest reads the table.",[12,10074,10075,10077],{},[16,10076,3592],{}," writes the new order and the staged moves to Jira from here too.",[21,10079,10081],{"id":10080},"see-who-is-in-the-room","See who is in the room",[12,10083,930,10084,7466,10086,10088,10089,7473],{},[16,10085,6758],{},[16,10087,5727],{}," at the left of the side panel. It groups the same work items by the person doing them, so the standup can walk through the team person by person instead of column by column. ",[16,10090,7472],{},[12,10092,10093,10094,10096,10097,10069],{},"Every assignee is a wide row with the person's name in the middle, and that person's work items sit under it, in the same board order. A row shows the same facts as the ",[16,10095,5727],{}," table: the work type, the priority, the flag, the key, the green passed check, the undo button, and the estimate. The check and the undo button are the same ones you see on the board and in the ",[16,10098,5727],{},[61,10100],{"alt":10101,"caption":10102,"stem":10103},"The Assignee table with the team grouped by person, one absent assignee, and the same passed checks","The same standup grouped by person","tutorial-standup-assignee",[26,10105,10106,10114,10121,10124,10129,10135,10140],{},[29,10107,10108,10109,10111,10112,569],{},"Drag a work item into another person's row to give it to them. The board avatar, the card color, and the ",[16,10110,5727],{}," row show the new person right away, but Jira changes only when you press ",[16,10113,3592],{},[29,10115,930,10116,10118,10119,7481],{},[16,10117,7193],{}," cap also applies here, so the table lists only the work items the board shows. A person whose work items all sit beyond the cap is not listed, in the table or in the ",[16,10120,5495],{},[29,10122,10123],{},"A moderator can give any work item to another person. A voter can give only their own work items. Guests read the table.",[29,10125,930,10126,10128],{},[16,10127,5495],{}," picker below the table lists everyone whose checkbox is checked. A moderator clears the checkbox at the left of an assignee row to remove that person from the picker and mark them absent. The row stays, with the checkbox unchecked and disabled, because the work items still belong to that person. Add the person back in the picker to check it again. Clearing a person who has no work items removes their row. The choice is shared with the team right away.",[29,10130,10131,10132,10134],{},"When a person is absent, their work items cannot be selected, from this table, from the ",[16,10133,5727],{}," table, or by clicking the card. Their cards use a gray border with dimmed text and avatar, so the team can tell them apart, and they lose the countdown pause, resume, and forward buttons.",[29,10136,1640,10137,10139],{},[16,10138,6758],{}," tab open, the countdown forward button walks this table and skips every absent person, so the standup continues with the next teammate.",[29,10141,10142,10144],{},[16,10143,7472],{}," is always present and has no checkbox.",[21,10146,10148],{"id":10147},"apply-the-changes-to-jira","Apply the changes to Jira",[12,10150,10151,10152,10154],{},"This is the step that makes the changes real. Press ",[16,10153,3592],{}," in the action bar under the board. Scrumpy writes the new status of every moved work item, the new order of the sprint, the staged flags, and the new assignees to Jira, in one go.",[12,10156,10157,10158,10160,10161,10163,10164,10166],{},"A moderator can also archive the standup with ",[16,10159,5259],{},", which sits before ",[16,10162,3592],{}," and appears when a Confluence space is configured for archives. The dialog lists the planning window, the sprint, board, or filter, every assignee with presence and presentation time, and every work item with its status, presentation time, and changes. A staged change is marked ",[16,10165,5456],{},". Archiving never changes Jira or the staged changes.",[12,10168,10169,10170,10172,10173,10175,10176,10178,10179,10181],{},"Without ",[16,10171,3592],{},", nothing is saved to Jira. Closing the tab or picking another sprint leaves Jira exactly as it was. If you change your mind, press ",[16,10174,6739],{}," and confirm the dialog instead. Discard removes every staged change and clears every passed check, and it does not touch Jira. ",[16,10177,3592],{}," clears the passed checks too, because the walkthrough is over. ",[16,10180,7808],{}," reads the sprint from Jira again.",[61,10183],{"alt":10184,"caption":10185,"stem":10186},"The action bar with the pending changes and the Apply button","Apply writes the standup to Jira","tutorial-standup-apply",[21,10188,10190],{"id":10189},"keep-everyone-in-step","Keep everyone in step",[12,10192,10193,10194,10196,10197,6318,10199,10201],{},"The moderator clicks the card the team is talking about, and everyone locked to the moderator follows the same card. The countdown at the right of the action bar follows that card, so each work item gets the same amount of time. When the ",[16,10195,6758],{}," tab is open, the forward button moves through the people in that table and skips every absent teammate; on any other tab it follows the board. Select ",[16,10198,491],{},[16,10200,3592],{}," when the session is done, and the planning session and its standup are removed.",{"title":153,"searchDepth":154,"depth":154,"links":10203},[10204,10205,10206,10207,10208,10209,10210,10211],{"id":9952,"depth":154,"text":9953},{"id":7269,"depth":154,"text":7270},{"id":9996,"depth":154,"text":9997},{"id":10005,"depth":154,"text":10006},{"id":10035,"depth":154,"text":10036},{"id":10080,"depth":154,"text":10081},{"id":10147,"depth":154,"text":10148},{"id":10189,"depth":154,"text":10190},"2026-11-15","Lead a standup in Scrumpy: pick the sprint, follow the speaking order, flag blockers and apply status moves.","Leading a standup","\u002Fog\u002Ftutorial-leading-a-standup.jpg",[7910,10217,7912],"standup board",{},16,"\u002Ftutorials\u002Fleading-a-standup",{"title":9941,"description":10213},{"loc":10220,"lastmod":802},"leading-a-standup","tutorials\u002Fen\u002Fleading-a-standup","tutorial\u002Fleading-a-standup","G3s5x-Jy40FmGpEPfhchMsjxbL93ImE5ucBaVVLHWXo",{"id":10228,"title":10229,"body":10230,"dateModified":802,"datePublished":10212,"description":10450,"extension":162,"heading":10451,"image":10452,"imageAlt":10451,"keywords":10453,"locale":168,"meta":10456,"navigation":170,"order":10457,"path":10458,"section":7989,"seo":10459,"sitemap":10460,"slug":10461,"stem":10462,"translationKey":10463,"__hash__":10464},"tutorials\u002Ftutorials\u002Fen\u002Frunning-a-retrospective.md","Running a retrospective | Tutorials | Scrumpy Planning Poker",{"type":9,"value":10231,"toc":10441},[10232,10235,10237,10254,10257,10261,10264,10270,10275,10279,10287,10293,10296,10300,10313,10318,10332,10336,10343,10348,10362,10364,10374,10395,10406,10411,10415,10429,10432],[12,10233,10234],{},"A retrospective takes minutes to set up and keeps the whole team on the same page at the end of a sprint. Add notes to three columns, like the ones you agree with, group the related ones, and turn the best of them into action items that become Jira work items.",[21,10236,9953],{"id":9952},[12,10238,6545,10239,10241,10242,10244,10245,10247,10248,10251,10252,569],{},[16,10240,349],{}," tab and pick a planning session from the tabs above the retrospective board. Pick the ",[16,10243,6556],{},", then the ",[16,10246,6562],{}," that just ended. The last six started sprints are listed, so the sprint you want is normally the first one. When the board has no started sprint, the sprint selector is hidden and the retrospective works for the board. When the space has no board, the retrospective works for the planning session. The ",[16,10249,10250],{},"type"," dropdown on the right changes the three column names, for example ",[16,10253,6599],{},[12,10255,10256],{},"Guests can read the retrospective. Moderators and voters can add notes and like them.",[21,10258,10260],{"id":10259},"add-a-note-to-each-column","Add a note to each column",[12,10262,10263],{},"Under each column name, select the add button with the plus icon. An empty note appears and its editor is ready, so you type straight away. Your notes sit on the right of the column and the notes from other participants sit on the left.",[12,10265,10266,10267,10269],{},"During the ",[16,10268,359],{}," stage the notes from other people stay face down, so nobody is influenced by what the others wrote. Your own notes stay visible to you.",[61,10271],{"alt":10272,"caption":10273,"stem":10274},"The retrospective board with notes in all three columns","Notes for the good, the bad, and the ugly","tutorial-retro-board",[21,10276,10278],{"id":10277},"like-and-group-the-notes","Like and group the notes",[12,10280,10281,10282,4066,10284,10286],{},"Switch the ",[16,10283,6915],{},[16,10285,2303],{}," when the team has finished writing. The notes are revealed and everyone can like the ones worth acting on. The like button shows how many people agree, and in this example three voters took part, with one, two, and three likes on different cards.",[12,10288,10289,10290,10292],{},"Select several notes in the same column, then choose ",[16,10291,6692],{},". Related notes join one card, and the group keeps one like count for all of them. Grouping is available from the Vote stage on and is disabled during Feedback. In the middle column three notes are grouped into one card, so the discussion stays together.",[12,10294,10295],{},"A moderator can also highlight notes without grouping them. A highlighted note is filled with the light accent colour, and everyone sees the same fill. Here two notes are highlighted for the discussion.",[21,10297,10299],{"id":10298},"follow-the-same-notes-in-the-status-table","Follow the same notes in the Status table",[12,10301,930,10302,10304,10305,430,10307,10309,10310,10312],{},[16,10303,5727],{}," tab at the left of the side panel shows the same retrospective as a compact table. The ",[16,10306,5727],{},[16,10308,6758],{}," tabs appear from the ",[16,10311,2303],{}," stage on. The three columns are wide bucket rows, and the notes of each column sit under their column in board order. A row shows the selection checkbox, the author, and the first line of the note, shortened with an ellipsis. A group is one row, with the first line of each note stacked and separated by a dashed line.",[61,10314],{"alt":10315,"caption":10316,"stem":10317},"The Status table with the same notes and group as the board","The same retrospective grouped by column","tutorial-retro-status",[26,10319,10320,10323,10326,10329],{},[29,10321,10322],{},"Drag a row into another column to move the note there. Dragging inside its own column changes only its order. Grouped notes travel together as one row.",[29,10324,10325],{},"A moderator can move any row, a voter only their own notes, and a guest reads the table. A row the viewer may not move returns to its place.",[29,10327,10328],{},"A column holds at most 200 notes, so a drop into a full column is refused and the row returns.",[29,10330,10331],{},"The checkbox is the same selection as on the board. Ticking a row ticks its note on the board, and ticking a note on the board ticks its row. A group row ticks every note in the group. Select notes here to group them or to create action items from them.",[21,10333,10335],{"id":10334},"walk-the-notes-person-by-person-in-the-assignee-table","Walk the notes person by person in the Assignee table",[12,10337,930,10338,7466,10340,10342],{},[16,10339,6758],{},[16,10341,5727],{},". It groups the same notes by the person who wrote them, in the order the authors first appear on the board. A group sits under the author of its first note. Each person is a wide bucket row, and their notes sit under it with the same columns as the Status table.",[61,10344],{"alt":10345,"caption":10346,"stem":10347},"The Assignee table with the notes grouped by author","The same retrospective grouped by author","tutorial-retro-assignee",[26,10349,10350,10353,10356,10359],{},[29,10351,10352],{},"Drag a note into another person's bucket to make that person its author. The note header on the board changes right away. A group moves together, so every note in the group takes the new author.",[29,10354,10355],{},"A moderator can reassign any note. A voter can reassign only their own notes. A guest reads the table.",[29,10357,10358],{},"You can drop a note only under a person who already has a note in the retrospective, because only they have a bucket.",[29,10360,10361],{},"The checkboxes and the shared selection work the same as in the Status table, so you can select notes here too.",[21,10363,6796],{"id":6795},[12,10365,10281,10366,4066,10368,10370,10371,10373],{},[16,10367,6915],{},[16,10369,5395],{},". Select a note or a group, then choose ",[16,10372,6720],{},". Each selected note or group becomes one row in the action items table, with the note text as the summary and the authors and likes beside it. Drag a row to change its place in the table. Everyone sees the new order, and the archive keeps it.",[12,10375,10376,10377,10380,10381,10383,10384,10386,10387,10389,10390,10392,10393,569],{},"For each row, pick the Jira ",[16,10378,10379],{},"work type"," in the Type column. Then press ",[16,10382,3592],{},". Scrumpy creates a Jira work item for every action item with a work type and links it in the Work item column. Action items set to ",[16,10385,8394],{}," are skipped, and a second ",[16,10388,3592],{}," without an edit stays disabled. Once a Jira work item is created from an action item, its estimate appears in the ",[16,10391,6826],{}," column and you can estimate it in the voting tabs next to ",[16,10394,1877],{},[12,10396,10397,10399,10400,10402,10403,10405],{},[16,10398,6739],{}," sits before ",[16,10401,3592],{}," and appears to a moderator. It asks for confirmation and removes every note, action item, and the timer of the retrospective on screen. It is disabled when the retrospective has nothing to discard. The ",[16,10404,1877],{}," tab in the side panel holds the full planning session conversation, including messages from the work items your action items link to.",[61,10407],{"alt":10408,"caption":10409,"stem":10410},"The action items with a linked Jira work item","Action items become Jira work items","tutorial-retro-action-items",[21,10412,10414],{"id":10413},"guide-the-session-with-stages-and-the-timer","Guide the session with stages and the timer",[12,10416,930,10417,10419,10420,10422,10423,10425,10426,10428],{},[16,10418,6915],{}," dropdown sits in the action bar with the countdown. ",[16,10421,359],{}," is for writing, ",[16,10424,2303],{}," for choosing, and ",[16,10427,5395],{}," for turning notes into work. A line below the notes explains what the current stage is for, and everyone sees it. Only a moderator changes the stage.",[12,10430,10431],{},"A timer keeps each stage inside its timebox. The first note you add in Feedback starts the countdown, and while a countdown runs the stage is locked. When the countdown ends, or when a moderator presses the fast-forward button, the stage ends early and everyone moves to the next one. In the Actions stage the timer controls are disabled.",[12,10433,10434,10435,10437,10438,10440],{},"When the team is done, ",[16,10436,5259],{}," saves the retrospective to Confluence. It is available in the Actions stage only. ",[16,10439,491],{}," closes the planning session and removes its notes, action items, standup, and chat.",{"title":153,"searchDepth":154,"depth":154,"links":10442},[10443,10444,10445,10446,10447,10448,10449],{"id":9952,"depth":154,"text":9953},{"id":10259,"depth":154,"text":10260},{"id":10277,"depth":154,"text":10278},{"id":10298,"depth":154,"text":10299},{"id":10334,"depth":154,"text":10335},{"id":6795,"depth":154,"text":6796},{"id":10413,"depth":154,"text":10414},"Run a retrospective in Jira: add notes, group them, vote, create action items and archive the result.","Running a retrospective","\u002Fog\u002Ftutorial-running-a-retrospective.jpg",[7097,10454,10455],"retrospective board","action items",{},17,"\u002Ftutorials\u002Frunning-a-retrospective",{"title":10229,"description":10450},{"loc":10458,"lastmod":802},"running-a-retrospective","tutorials\u002Fen\u002Frunning-a-retrospective","tutorial\u002Frunning-a-retrospective","ZthKA7-wmBPaegvb5BtG0p9GVOyzegAsoIIstoRSIfU",1795345557134]