[{"data":1,"prerenderedAt":2098},["ShallowReactive",2],{"guide-en-estimation-perspectives":3},{"doc":4,"prev":1090,"next":1708,"related":1961,"reading":2093},{"id":5,"title":6,"body":7,"dateModified":1069,"datePublished":1070,"description":1071,"extension":1072,"heading":119,"image":1073,"imageAlt":119,"keywords":1074,"locale":1079,"meta":1080,"navigation":1081,"order":1059,"path":1082,"section":1083,"seo":1084,"sitemap":1085,"slug":1086,"stem":1087,"translationKey":1088,"__hash__":1089},"guide\u002Fguide\u002Fen\u002Festimation-perspectives.md","Estimation Perspectives | Scrumpy Planning Poker",{"type":8,"value":9,"toc":1051},"minimark",[10,14,19,34,37,44,57,61,64,92,96,116,121,125,145,152,155,175,178,268,276,280,283,315,318,322,329,367,370,381,388,394,403,407,410,413,532,538,541,544,547,551,557,714,717,720,723,730,733,758,762,793,798,803,821,827,830,852,865,870,884,890,904,907,910,913,918,932,935,941,944,969,972,975,997,1000,1003,1007,1018,1045,1048],[11,12,13],"p",{},"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.",[15,16,18],"h2",{"id":17},"working-week","Working week",[11,20,21,22,26,27,30,31,33],{},"At the top of the Settings tab, choose the ",[23,24,25],"strong",{},"Week starts on"," day and the ",[23,28,29],{},"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 ",[23,32,29],{}," field turns red and explains what to change.",[11,35,36],{},"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.",[11,38,39,40,43],{},"Below the two day fields, ",[23,41,42],{},"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.",[11,45,46,47,49,50,53,54,56],{},"Next to ",[23,48,42],{},", ",[23,51,52],{},"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 ",[23,55,42],{},". 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.",[15,58,60],{"id":59},"why-multiple-perspectives","Why Multiple Perspectives?",[11,62,63],{},"Different estimation dimensions help your team look at work from several angles:",[65,66,67,74,80,86],"ul",{},[68,69,70,73],"li",{},[23,71,72],{},"Points",": Relative complexity and effort",[68,75,76,79],{},[23,77,78],{},"Time",": Hours or days of work",[68,81,82,85],{},[23,83,84],{},"T-Shirt Sizes",": Coarse-grained sizing (XS, S, M, L, XL)",[68,87,88,91],{},[23,89,90],{},"Risk",": Likelihood or impact of unknowns",[15,93,95],{"id":94},"perspective-settings","Perspective Settings",[11,97,98,99,49,102,49,105,49,108,111,112,115],{},"Each perspective is configured through five sub-tabs: ",[23,100,101],{},"General",[23,103,104],{},"Voting",[23,106,107],{},"Cards",[23,109,110],{},"Estimation",", and ",[23,113,114],{},"Backup & Restore",".",[117,118],"docs-figure",{"alt":119,"caption":119,"stem":120},"Estimation Perspectives","guide-perspectives",[122,123,101],"h3",{"id":124},"general",[11,126,127,128,130,131,134,135,111,138,141,142,144],{},"The ",[23,129,101],{}," tab holds the perspective's ",[23,132,133],{},"name",", optional ",[23,136,137],{},"description",[23,139,140],{},"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 ",[23,143,140],{}," (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.",[11,146,147,148,151],{},"If no perspective applies to a work item's work type, the Scrumpy panel shows ",[23,149,150],{},"No voting perspective",", names the work type, and asks you to configure the space's perspective settings rather than showing an empty deck.",[11,153,154],{},"Below those fields, the General tab has three actions:",[65,156,157,163,169],{},[68,158,159,162],{},[23,160,161],{},"Reset to defaults",": Return the perspective to its initial settings, after a confirmation",[68,164,165,168],{},[23,166,167],{},"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",[68,170,171,174],{},[23,172,173],{},"Delete perspective",": Remove the perspective and all its sessions permanently, after a confirmation. The Default perspective cannot be deleted",[122,176,104],{"id":177},"voting",[179,180,181,194],"table",{},[182,183,184],"thead",{},[185,186,187,191],"tr",{},[188,189,190],"th",{},"Setting",[188,192,193],{},"Description",[195,196,197,208,218,228,238,248,258],"tbody",{},[185,198,199,205],{},[200,201,202],"td",{},[23,203,204],{},"Open voting",[200,206,207],{},"When on, participants see each other's votes in real time",[185,209,210,215],{},[200,211,212],{},[23,213,214],{},"Certainty",[200,216,217],{},"Shows how often participants re-voted during the session, not how spread the votes are. One vote per participant gives 100%",[185,219,220,225],{},[200,221,222],{},[23,223,224],{},"Variation",[200,226,227],{},"Shows how widely the vote values are spread around their average. Lower is better, and it needs at least two numeric votes",[185,229,230,235],{},[200,231,232],{},[23,233,234],{},"Automatic completion",[200,236,237],{},"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",[185,239,240,245],{},[200,241,242],{},[23,243,244],{},"Asynchronous voting",[200,246,247],{},"Participants vote at their own pace, without a countdown timer",[185,249,250,255],{},[200,251,252],{},[23,253,254],{},"Vote duration",[200,256,257],{},"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",[185,259,260,265],{},[200,261,262],{},[23,263,264],{},"Averaging",[200,266,267],{},"How votes are combined: Arithmetic mean, Geometric mean, Harmonic mean, Quadratic mean, Midrange, Median, Minimum, Maximum, Mode (most common), PERT, or Count",[11,269,270,271,115],{},"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 ",[272,273,275],"docs-link",{"to":274},"\u002Fgetting-started\u002Fvoting-session-controls","Voting Session Controls",[122,277,279],{"id":278},"mean-averaging","Mean averaging",[11,281,282],{},"Scrumpy offers five mean-based methods:",[65,284,285,291,297,303,309],{},[68,286,287,290],{},[23,288,289],{},"Arithmetic mean"," adds the votes and divides by the number of votes.",[68,292,293,296],{},[23,294,295],{},"Geometric mean"," multiplies the votes and takes the nth root.",[68,298,299,302],{},[23,300,301],{},"Harmonic mean"," divides the number of votes by the sum of their reciprocals.",[68,304,305,308],{},[23,306,307],{},"Quadratic mean"," squares the votes, averages the squares, and takes the square root.",[68,310,311,314],{},[23,312,313],{},"Midrange"," is halfway between the smallest and largest vote.",[11,316,317],{},"A zero vote makes the geometric and harmonic means zero. Every result is rounded to the nearest available card, like the other averaging methods.",[122,319,321],{"id":320},"pert-averaging","PERT averaging",[11,323,324,325,328],{},"PERT (Program Evaluation and Review Technique) is a three-point estimation method. When you choose ",[23,326,327],{},"PERT"," as the averaging method and the team has cast at least three different values, Scrumpy takes the three points from the votes themselves:",[179,330,331,341],{},[182,332,333],{},[185,334,335,338],{},[188,336,337],{},"Point",[188,339,340],{},"Meaning",[195,342,343,351,359],{},[185,344,345,348],{},[200,346,347],{},"Optimistic (O)",[200,349,350],{},"The smallest value voted",[185,352,353,356],{},[200,354,355],{},"Most Likely (M)",[200,357,358],{},"The average of every value strictly between the smallest and the largest",[185,360,361,364],{},[200,362,363],{},"Pessimistic (P)",[200,365,366],{},"The largest value voted",[11,368,369],{},"The estimate is the weighted PERT average:",[371,372,377],"pre",{"className":373,"code":375,"language":376},[374],"language-text","E = (O + 4M + P) \u002F 6\n","text",[378,379,375],"code",{"__ignoreMap":380},"",[11,382,383,384,387],{},"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 ",[23,385,386],{},"Deviation",":",[371,389,392],{"className":390,"code":391,"language":376},[374],"deviation = (P - O) \u002F 6\n",[378,393,391],{"__ignoreMap":380},[11,395,396,397,399,400,402],{},"While ",[23,398,204],{}," 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 ",[23,401,204],{}," is on.",[122,404,406],{"id":405},"count-averaging","Count averaging",[11,408,409],{},"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.",[122,411,107],{"id":412},"cards",[179,414,415,423],{},[182,416,417],{},[185,418,419,421],{},[188,420,190],{},[188,422,193],{},[195,424,425,435,445,455,465,475,485,499],{},[185,426,427,432],{},[200,428,429],{},[23,430,431],{},"Sequence",[200,433,434],{},"Choose the estimation style from the dropdown: Regular, Fibonacci, Tens, Fingers, Dice, T-Shirt, Free Scale, or Parametric",[185,436,437,442],{},[200,438,439],{},[23,440,441],{},"Available cards",[200,443,444],{},"Which cards from the sequence appear to voters during a session",[185,446,447,452],{},[200,448,449],{},[23,450,451],{},"Card titles",[200,453,454],{},"The name shown for each card, built in per card and editable",[185,456,457,462],{},[200,458,459],{},[23,460,461],{},"T-shirt story points",[200,463,464],{},"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",[185,466,467,472],{},[200,468,469],{},[23,470,471],{},"Extra cards",[200,473,474],{},"Fun cards for team morale (infinity, phoenix, cookie, buffalo, ping pong)",[185,476,477,482],{},[200,478,479],{},[23,480,481],{},"Custom images",[200,483,484],{},"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",[185,486,487,492],{},[200,488,489],{},[23,490,491],{},"Free scale range",[200,493,494,495,498],{},"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 ",[23,496,497],{},"sp"," suffix. The converted duration appears only when the estimation target writes a time value (a time board or a Time field).",[185,500,501,506],{},[200,502,503],{},[23,504,505],{},"Story points to hours",[200,507,508,509,512,513,516,517,520,521,524,525,528,529,531],{},"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 ",[23,510,511],{},"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 ",[23,514,515],{},"1 sp · S",". The same units appear in the vote list, the result chart, the badge beside the narrowed ",[23,518,519],{},"Override"," dropdown, and the final result. When the estimation target is ",[23,522,523],{},"Field",", a non-zero conversion also shows the ",[23,526,527],{},"Time field"," for every sequence, including T-shirt. When ",[23,530,505],{}," 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.",[11,533,534,535,537],{},"Custom images are set per card and per sequence. The Available cards list shows the cards of the sequence selected in ",[23,536,431],{}," (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.",[11,539,540],{},"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.",[11,542,543],{},"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.",[11,545,546],{},"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.",[122,548,550],{"id":549},"parametric","Parametric",[11,552,553,554,556],{},"Choose ",[23,555,550],{}," 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.",[65,558,559,562,573,587,595,660,663,666,669,688,695,708],{},[68,560,561],{},"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.",[68,563,564,565,568,569,572],{},"Press ",[23,566,567],{},"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 ",[23,570,571],{},"Delete selected"," to remove them.",[68,574,575,576,49,579,582,583,586],{},"The formula uses the parameter variables shown below the field: ",[378,577,578],{},"p1",[378,580,581],{},"p2",", and so on. For example, ",[378,584,585],{},"(p1 + p2) \u002F 2"," averages the first two parameters.",[68,588,589,590,592,593,115],{},"The preview below the formula uses the same parameters voters see. Move a parameter to see the result update. When ",[23,591,505],{}," is set, the preview appends the converted duration, for example ",[23,594,511],{},[68,596,597,598,49,601,49,604,49,607,49,610,49,613,49,616,49,619,49,622,49,625,49,628,49,631,49,634,49,637,49,640,49,643,49,646,49,649,652,653,656,657,115],{},"The formula supports ",[378,599,600],{},"+",[378,602,603],{},"-",[378,605,606],{},"*",[378,608,609],{},"\u002F",[378,611,612],{},"^",[378,614,615],{},"%",[378,617,618],{},"min",[378,620,621],{},"max",[378,623,624],{},"round",[378,626,627],{},"floor",[378,629,630],{},"ceil",[378,632,633],{},"abs",[378,635,636],{},"sqrt",[378,638,639],{},"sin",[378,641,642],{},"cos",[378,644,645],{},"tan",[378,647,648],{},"log",[378,650,651],{},"exp",", and the constants ",[378,654,655],{},"pi"," and ",[378,658,659],{},"e",[68,661,662],{},"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.",[68,664,665],{},"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.",[68,667,668],{},"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.",[68,670,671,672,675,676,679,680,683,684,687],{},"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: ",[23,673,674],{},"Results"," with the chart, and the chart tab. A two-parameter perspective shows ",[23,677,678],{},"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 ",[23,681,682],{},"Radar"," with one polygon per participant and a dotted averaged polygon. The final result and averaging controls stay below both tabs, and the ",[23,685,686],{},"Parameters"," averaging mode averages each position and then applies the formula.",[68,689,690,691,694],{},"In the planning table each work item's parametric cell shows the result with an ",[23,692,693],{},"Edit vote"," control that opens the sliders and a cross-circle control that withdraws the vote. The result is never typed in directly.",[68,696,697,698,49,701,111,704,707],{},"In bulk voting a parametric perspective also has a selectable row with ",[23,699,700],{},"Affinity",[23,702,703],{},"Dot",[23,705,706],{},"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.",[68,709,710,711,713],{},"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 ",[23,712,505],{}," is set.",[11,715,716],{},"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.",[11,718,719],{},"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.",[11,721,722],{},"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.",[11,724,725,726,729],{},"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 ",[23,727,728],{},"M",", during voting. The size label is written to Jira only when the perspective writes a T-shirt field.",[11,731,732],{},"To edit T-shirt story points:",[734,735,736,739,744,752],"ol",{},[68,737,738],{},"Open the perspective settings.",[68,740,741,742,115],{},"Go to ",[23,743,107],{},[68,745,553,746,749,750,115],{},[23,747,748],{},"T-Shirt"," in ",[23,751,431],{},[68,753,754,755,757],{},"In ",[23,756,441],{},", change the number next to a card title.",[122,759,761],{"id":760},"estimation-target","Estimation Target",[179,763,764,772],{},[182,765,766],{},[185,767,768,770],{},[188,769,190],{},[188,771,193],{},[195,773,774,784],{},[185,775,776,781],{},[200,777,778],{},[23,779,780],{},"Default",[200,782,783],{},"Use Jira's built-in board estimation (recommended). The first board is selected automatically, and a link opens the board's estimation settings",[185,785,786,790],{},[200,787,788],{},[23,789,523],{},[200,791,792],{},"Write to custom Jira fields for story points, time tracking, or T-shirt sizes",[11,794,795,796,115],{},"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 ",[23,797,780],{},[11,799,127,800,802],{},[23,801,780],{}," 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.",[11,804,127,805,808,809,49,812,111,814,817,818,820],{},[23,806,807],{},"Estimation board"," list groups boards under ",[23,810,811],{},"Story points",[23,813,78],{},[23,815,816],{},"No estimation",". Boards without an estimation field appear under ",[23,819,816],{}," 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.",[11,822,823,824,826],{},"The estimation board also decides where the perspective appears in Capacity planning. When the target is ",[23,825,780],{}," 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.",[11,828,829],{},"When you use the Field target, the fields shown depend on the sequence and conversion:",[65,831,832,838,844],{},[68,833,834,837],{},[23,835,836],{},"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",[68,839,840,843],{},[23,841,842],{},"Story Points",": A number field for story point values, shown for the numeric sequences and optionally for T-shirt perspectives",[68,845,846,848,849,851],{},[23,847,78],{},": A time tracking field for hour-based estimates, shown only when ",[23,850,505],{}," is set to a non-zero value",[11,853,854,855,857,858,861,862,864],{},"With the ",[23,856,780],{}," target, a T-shirt estimate is written as the story point number you set for the chosen card. For a T-shirt perspective, the ",[23,859,860],{},"T-shirt field"," also appears right next to the ",[23,863,807],{}," selector so the same accepted estimate can be written as its size label to that field as well.",[11,866,854,867,869],{},[23,868,523],{}," 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.",[11,871,854,872,874,875,877,878,880,881,883],{},[23,873,523],{}," 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 ",[23,876,523],{}," choice stays selected while you pick a field, so the setting does not jump back to ",[23,879,780],{},". The Time field is hidden for every sequence when ",[23,882,505],{}," is 0 or empty, and its saved selection is cleared.",[11,885,886,887,889],{},"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 ",[23,888,780],{}," 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.",[11,891,892,893,896,897,899,900,903],{},"Below the estimation fields, ",[23,894,895],{},"Preview"," shows a sample accepted estimate using the same formatting as the voting panel. The sample follows the selected fields and the ",[23,898,505],{}," mapping, so it can show story points, the converted duration, and the T-shirt size together, for example ",[23,901,902],{},"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.",[11,905,906],{},"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.",[11,908,909],{},"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.",[122,911,114],{"id":912},"backup-restore",[11,914,127,915,917],{},[23,916,114],{}," tab holds:",[65,919,920,926],{},[68,921,922,925],{},[23,923,924],{},"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",[68,927,928,931],{},[23,929,930],{},"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",[11,933,934],{},"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.",[11,936,937,940],{},[23,938,939],{},"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.",[11,942,943],{},"Changing any of these ends the running sessions for the perspective:",[65,945,946,949,952,955,958,961,964,967],{},[68,947,948],{},"The card sequence",[68,950,951],{},"The active cards of the sequence",[68,953,954],{},"The extra cards",[68,956,957],{},"The free scale minimum or maximum",[68,959,960],{},"The parametric parameters and the parametric formula",[68,962,963],{},"The vote duration",[68,965,966],{},"Auto-complete",[68,968,244],{},[11,970,971],{},"Reset to defaults also ends them, because it resets the settings above.",[11,973,974],{},"Changing any of these never ends a session, even while people are voting:",[65,976,977,980,983,986,989,992,994],{},[68,978,979],{},"The name, the description, and the Work types",[68,981,982],{},"Open voting, certainty, and variation",[68,984,985],{},"The averaging method",[68,987,988],{},"Card titles and card images",[68,990,991],{},"The T-shirt story points",[68,993,505],{},[68,995,996],{},"The estimation target, the estimation board, and the estimation fields",[11,998,999],{},"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.",[11,1001,1002],{},"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.",[15,1004,1006],{"id":1005},"managing-perspectives","Managing Perspectives",[11,1008,1009,1010,1013,1014,1017],{},"In the space settings page, each perspective is a tab, and you can add more with ",[23,1011,1012],{},"Add new perspective",". A new perspective starts with the name ",[23,1015,1016],{},"New view","; rename it to a short, recognizable name. For each perspective you can:",[65,1019,1020,1025,1030,1035,1040],{},[68,1021,1022,1024],{},[23,1023,161],{}," (General): Return the perspective to its initial settings",[68,1026,1027,1029],{},[23,1028,167],{}," (General): Immediately cancel all active voting sessions for the perspective. This cannot be undone, and all participants lose their current votes",[68,1031,1032,1034],{},[23,1033,173],{}," (General): Remove the perspective and all its sessions permanently. The Default perspective cannot be deleted",[68,1036,1037,1039],{},[23,1038,924],{}," (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",[68,1041,1042,1044],{},[23,1043,930],{}," (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",[11,1046,1047],{},"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.",[11,1049,1050],{},"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":380,"searchDepth":1052,"depth":1052,"links":1053},2,[1054,1055,1056,1068],{"id":17,"depth":1052,"text":18},{"id":59,"depth":1052,"text":60},{"id":94,"depth":1052,"text":95,"children":1057},[1058,1060,1061,1062,1063,1064,1065,1066,1067],{"id":124,"depth":1059,"text":101},3,{"id":177,"depth":1059,"text":104},{"id":278,"depth":1059,"text":279},{"id":320,"depth":1059,"text":321},{"id":405,"depth":1059,"text":406},{"id":412,"depth":1059,"text":107},{"id":549,"depth":1059,"text":550},{"id":760,"depth":1059,"text":761},{"id":912,"depth":1059,"text":114},{"id":1005,"depth":1052,"text":1006},"2026-11-21","2026-07-26","Set up perspectives in Scrumpy: voting rules, card sequences, averaging methods and the Jira field each estimate is written to.","md","\u002Fog\u002Fguide-estimation-perspectives.jpg",[1075,1076,1077,1078],"estimation perspectives","jira story points","pert estimation","planning poker","en",{},true,"\u002Fgetting-started\u002Festimation-perspectives","guide",{"title":6,"description":1071},{"loc":1082,"lastmod":1069},"estimation-perspectives","guide\u002Fen\u002Festimation-perspectives","guide\u002Festimation-perspectives","G6e_NyDdXo7KjkRHJalTURKglnw_qMcVk88OAPmeSPw",{"id":1091,"title":1092,"body":1093,"dateModified":1069,"datePublished":1070,"description":1694,"extension":1072,"heading":1273,"image":1695,"imageAlt":1273,"keywords":1696,"locale":1079,"meta":1701,"navigation":1081,"order":1052,"path":1702,"section":1083,"seo":1703,"sitemap":1704,"slug":1277,"stem":1705,"translationKey":1706,"__hash__":1707},"guide\u002Fguide\u002Fen\u002Fgetting-started.md","Getting Started with Scrumpy | Scrumpy Planning Poker",{"type":8,"value":1094,"toc":1671},[1095,1098,1102,1105,1109,1116,1136,1139,1142,1146,1149,1171,1177,1181,1184,1187,1190,1194,1197,1203,1207,1214,1229,1233,1271,1275,1279,1282,1285,1292,1295,1298,1301,1308,1311,1314,1317,1320,1323,1327,1330,1373,1376,1379,1417,1432,1435,1438,1441,1444,1447,1453,1457,1464,1481,1488,1492,1501,1505,1512,1516,1585,1596,1606,1610,1616,1623,1629,1635,1641,1646,1652,1657,1663],[11,1096,1097],{},"This guide walks you through setting up Scrumpy for your team.",[15,1099,1101],{"id":1100},"step-1-install-the-app","Step 1: Install the App",[11,1103,1104],{},"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.",[15,1106,1108],{"id":1107},"step-2-configure-your-team","Step 2: Configure Your Team",[11,1110,1111,1112,1115],{},"Open ",[23,1113,1114],{},"Space settings > Scrumpy Poker > Permissions"," and assign roles to your team:",[65,1117,1118,1124,1130],{},[68,1119,1120,1123],{},[23,1121,1122],{},"Moderators",": people who start, manage, and complete voting sessions. Typically scrum masters, team leads, or product managers.",[68,1125,1126,1129],{},[23,1127,1128],{},"Voters",": team members who cast estimates during voting sessions.",[68,1131,1132,1135],{},[23,1133,1134],{},"Guests",": anyone who is not a moderator or a voter. Guests can watch sessions and see results, but they cannot vote or moderate.",[11,1137,1138],{},"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.",[11,1140,1141],{},"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.",[122,1143,1145],{"id":1144},"choose-where-scrumpy-appears","Choose Where Scrumpy Appears",[11,1147,1148],{},"The same page controls where Scrumpy appears in Jira. Two checkboxes are selected by default:",[65,1150,1151,1165],{},[68,1152,1153,1156,1157,1160,1161,1164],{},[23,1154,1155],{},"Show the Estimations page"," adds the ",[23,1158,1159],{},"Estimations"," tab to the space navigation. Clearing it hides the page for everyone in the space. It also hides the ",[23,1162,1163],{},"Add to planning"," action on work items, because planning sessions live on that page.",[68,1166,1167,1170],{},[23,1168,1169],{},"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.",[11,1172,1173,1174,1176],{},"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. ",[23,1175,161],{}," does not change them.",[122,1178,1180],{"id":1179},"optional-set-a-password","Optional: Set a Password",[11,1182,1183],{},"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.",[11,1185,1186],{},"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.",[11,1188,1189],{},"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.",[15,1191,1193],{"id":1192},"step-3-set-up-perspectives","Step 3: Set Up Perspectives",[11,1195,1196],{},"Perspectives define how your team estimates. Each perspective has its own voting rules, card sequences, and target Jira field.",[11,1198,1111,1199,1202],{},[23,1200,1201],{},"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.",[15,1204,1206],{"id":1205},"step-4-start-estimating","Step 4: Start Estimating",[11,1208,1209,1210,1213],{},"Open any Jira work item and look for the ",[23,1211,1212],{},"Scrumpy"," panel on the right side of the screen.",[65,1215,1216,1223,1226],{},[68,1217,1218,1219,1222],{},"As a moderator, click ",[23,1220,1221],{},"Start"," to begin a voting session",[68,1224,1225],{},"As a voter, cast your estimate by clicking a card",[68,1227,1228],{},"Once all required voters have submitted, the moderator accepts the result",[15,1230,1232],{"id":1231},"step-5-use-the-space-estimations-page","Step 5: Use the Space Estimations Page",[11,1234,1111,1235,1238,1239,49,1242,49,1245,49,1248,49,1251,49,1254,49,1257,49,1260,1263,1264,1267,1268,1270],{},[23,1236,1237],{},"Space > Estimations",". The page has these tabs: ",[23,1240,1241],{},"Getting started",[23,1243,1244],{},"Tutorials",[23,1246,1247],{},"Refinement\u002Fgrooming",[23,1249,1250],{},"Capacity planning",[23,1252,1253],{},"Standup",[23,1255,1256],{},"Retrospective",[23,1258,1259],{},"Voting sessions",[23,1261,1262],{},"Dashboard",", and a right-aligned ",[23,1265,1266],{},"Feedback"," tab. A support icon to the right of ",[23,1269,1266],{}," 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.",[117,1272],{"alt":1273,"caption":1273,"stem":1274},"Getting Started with Scrumpy","guide-space-tabs",[122,1276,1278],{"id":1277},"getting-started","Getting Started",[11,1280,1281],{},"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.",[122,1283,1244],{"id":1284},"tutorials",[11,1286,1287,1288,1291],{},"Short guided tours with screenshots. Choose a tutorial in the ",[23,1289,1290],{},"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.",[122,1293,1247],{"id":1294},"refinementgrooming",[11,1296,1297],{},"Create and manage planning sessions to organize refinement work. See the Planning sessions page for details.",[122,1299,1250],{"id":1300},"capacity-planning",[11,1302,1303,1304,1307],{},"Plan how much work your team can take on in the next sprints. Open the tab, choose a planning session, and select ",[23,1305,1306],{},"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.",[11,1309,1310],{},"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.",[122,1312,1253],{"id":1313},"standup",[11,1315,1316],{},"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.",[122,1318,1256],{"id":1319},"retrospective",[11,1321,1322],{},"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.",[122,1324,1326],{"id":1325},"voting-sessions","Voting Sessions",[11,1328,1329],{},"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.",[65,1331,1332,1341,1350,1355,1361,1367],{},[68,1333,1334,656,1337,1340],{},[23,1335,1336],{},"Type",[23,1338,1339],{},"Work item",": centered headers and cells. Work item cells have no leading space before the key.",[68,1342,1343,656,1346,1349],{},[23,1344,1345],{},"State",[23,1347,1348],{},"% complete",": left aligned, minimum width, and the % complete header stays on one line.",[68,1351,1352,1354],{},[23,1353,1128],{},": right aligned.",[68,1356,1357,1360],{},[23,1358,1359],{},"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.",[68,1362,1363,1366],{},[23,1364,1365],{},"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.",[68,1368,1369,1372],{},[23,1370,1371],{},"Completion",": shows a status tag.",[11,1374,1375],{},"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.",[11,1377,1378],{},"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.",[65,1380,1381,1387,1393,1399,1405,1411],{},[68,1382,1383,1386],{},[23,1384,1385],{},"Pause"," pauses the selected active sessions. Sessions in perspectives with asynchronous voting are skipped.",[68,1388,1389,1392],{},[23,1390,1391],{},"Resume"," resumes the selected paused sessions. Sessions in perspectives with asynchronous voting are skipped.",[68,1394,1395,1398],{},[23,1396,1397],{},"Complete"," finishes a session that has real votes and cancels one whose votes are missing or are only extra emoji cards.",[68,1400,1401,1404],{},[23,1402,1403],{},"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.",[68,1406,1407,1410],{},[23,1408,1409],{},"Cancel"," stops the selected sessions, including completed ones.",[68,1412,1413,1416],{},[23,1414,1415],{},"Accept"," writes the completed sessions' estimates to Jira.",[11,1418,1419,1420,1422,1423,1425,1426,1428,1429,1431],{},"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; ",[23,1421,1385],{}," needs an active session, ",[23,1424,1391],{}," needs a paused session, and both need a perspective without asynchronous voting. ",[23,1427,1403],{}," needs a completed session. ",[23,1430,1409],{}," is enabled for any selected session, started or completed.",[11,1433,1434],{},"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.",[11,1436,1437],{},"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.",[122,1439,1262],{"id":1440},"dashboard",[11,1442,1443],{},"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.",[122,1445,1266],{"id":1446},"feedback",[11,1448,1449,1450,1452],{},"The right-aligned ",[23,1451,1266],{}," tab lets you rate the app, suggest improvements, and contact the support team. See the Feedback and Support section for details.",[122,1454,1456],{"id":1455},"quick-start-guide","Quick start guide",[11,1458,1459,1460,1463],{},"Above the tab list, a ",[23,1461,1462],{},"Quick start"," guide shows four steps to get going:",[734,1465,1466,1469,1475,1478],{},[68,1467,1468],{},"Set up the space moderators and voters (open the space settings Permissions tab to do this).",[68,1470,1471,1472,115],{},"Create a planning session with an optional start and end time using ",[23,1473,1474],{},"Create",[68,1476,1477],{},"Add Jira work items to the refinement\u002Fgrooming tab from an existing Jira filter.",[68,1479,1480],{},"Arrange the items in the order they will be estimated.",[11,1482,1483,1484,1487],{},"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 ",[23,1485,1486],{},"Dismiss"," in the message to hide it, or use the support icon in the tab bar to show it again.",[122,1489,1491],{"id":1490},"adding-work-items-to-planning-from-the-work-item-view","Adding Work items to Planning from the Work item View",[11,1493,1494,1495,1497,1498,1500],{},"When you view a Jira work item, open the ",[23,1496,1212],{}," panel and click ",[23,1499,1163],{}," 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.",[122,1502,1504],{"id":1503},"filtering-work-items-with-jql","Filtering Work items with JQL",[11,1506,1507,1508,1511],{},"For advanced users who build Jira filters and boards, Scrumpy provides a custom JQL function, ",[378,1509,1510],{},"issuesInEstimation()",", that returns the work items currently being estimated.",[1513,1514,686],"h4",{"id":1515},"parameters",[179,1517,1518,1530],{},[182,1519,1520],{},[185,1521,1522,1525,1528],{},[188,1523,1524],{},"Parameter",[188,1526,1527],{},"Required",[188,1529,193],{},[195,1531,1532,1549,1569],{},[185,1533,1534,1539,1542],{},[200,1535,1536],{},[378,1537,1538],{},"projectKey",[200,1540,1541],{},"Yes",[200,1543,1544,1545,1548],{},"The Jira space key (for example ",[378,1546,1547],{},"\"PROJ\"",")",[185,1550,1551,1556,1559],{},[200,1552,1553],{},[378,1554,1555],{},"state",[200,1557,1558],{},"No",[200,1560,1561,1562,656,1565,1568],{},"Filter by session state. Only ",[378,1563,1564],{},"\"paused\"",[378,1566,1567],{},"\"completed\""," are recognized. Omit to include every state",[185,1570,1571,1576,1578],{},[200,1572,1573],{},[378,1574,1575],{},"perspectives",[200,1577,1558],{},[200,1579,1580,1581,1584],{},"Filter by one or more perspective names, separated by commas (for example ",[378,1582,1583],{},"\"Points, Time\"","). Names must match exactly, including case",[11,1586,1587,1588,1590,1591,656,1593,1595],{},"Values after ",[378,1589,1538],{}," are read by value: ",[378,1592,1564],{},[378,1594,1567],{}," select the state, and any other value is treated as a comma-separated list of perspective names.",[11,1597,1598,1599,656,1602,1605],{},"The function supports both ",[378,1600,1601],{},"in",[378,1603,1604],{},"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.",[1513,1607,1609],{"id":1608},"examples","Examples",[371,1611,1614],{"className":1612,"code":1613,"language":376},[374],"issuekey in issuesInEstimation(\"PROJ\")\n",[378,1615,1613],{"__ignoreMap":380},[11,1617,1618,1619,1622],{},"Return all work items in space ",[378,1620,1621],{},"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.",[371,1624,1627],{"className":1625,"code":1626,"language":376},[374],"issuekey in issuesInEstimation(\"PROJ\", \"paused\")\n",[378,1628,1626],{"__ignoreMap":380},[11,1630,1631,1632,1634],{},"Return work items in ",[378,1633,1621],{}," with a paused voting session. Useful for finding work items that need the moderator's attention.",[371,1636,1639],{"className":1637,"code":1638,"language":376},[374],"issuekey in issuesInEstimation(\"PROJ\", \"completed\")\n",[378,1640,1638],{"__ignoreMap":380},[11,1642,1631,1643,1645],{},[378,1644,1621],{}," where voting has completed but the moderator has not accepted the result yet.",[371,1647,1650],{"className":1648,"code":1649,"language":376},[374],"issuekey in issuesInEstimation(\"PROJ\", \"paused\", \"Points\")\n",[378,1651,1649],{"__ignoreMap":380},[11,1653,1631,1654,1656],{},[378,1655,1621],{}," with a paused session in the Points perspective. You can list several perspective names to match any of them.",[371,1658,1661],{"className":1659,"code":1660,"language":376},[374],"issuekey not in issuesInEstimation(\"PROJ\", \"completed\")\n",[378,1662,1660],{"__ignoreMap":380},[11,1664,1631,1665,1667,1668,1670],{},[378,1666,1621],{}," that are not in a completed estimation session. Use ",[378,1669,1604],{}," to exclude work items from a filter or board.",{"title":380,"searchDepth":1052,"depth":1052,"links":1672},[1673,1674,1678,1679,1680],{"id":1100,"depth":1052,"text":1101},{"id":1107,"depth":1052,"text":1108,"children":1675},[1676,1677],{"id":1144,"depth":1059,"text":1145},{"id":1179,"depth":1059,"text":1180},{"id":1192,"depth":1052,"text":1193},{"id":1205,"depth":1052,"text":1206},{"id":1231,"depth":1052,"text":1232,"children":1681},[1682,1683,1684,1685,1686,1687,1688,1689,1690,1691,1692,1693],{"id":1277,"depth":1059,"text":1278},{"id":1284,"depth":1059,"text":1244},{"id":1294,"depth":1059,"text":1247},{"id":1300,"depth":1059,"text":1250},{"id":1313,"depth":1059,"text":1253},{"id":1319,"depth":1059,"text":1256},{"id":1325,"depth":1059,"text":1326},{"id":1440,"depth":1059,"text":1262},{"id":1446,"depth":1059,"text":1266},{"id":1455,"depth":1059,"text":1456},{"id":1490,"depth":1059,"text":1491},{"id":1503,"depth":1059,"text":1504},"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",[1697,1698,1699,1700],"scrumpy planning poker","jira app","getting started","planning poker setup",{},"\u002Fgetting-started",{"title":1092,"description":1694},{"loc":1702,"lastmod":1069},"guide\u002Fen\u002Fgetting-started","guide\u002Fgetting-started","eCmV9QjcKILJk6QcL30Q00LIA5lvRL3gMKp1jyFhXvk",{"id":1709,"title":1710,"body":1711,"dateModified":1069,"datePublished":1070,"description":1945,"extension":1072,"heading":1946,"image":1947,"imageAlt":1946,"keywords":1948,"locale":1079,"meta":1952,"navigation":1081,"order":1953,"path":1954,"section":1083,"seo":1955,"sitemap":1956,"slug":1957,"stem":1958,"translationKey":1959,"__hash__":1960},"guide\u002Fguide\u002Fen\u002Fchat.md","Chat and Communication | Scrumpy Planning Poker",{"type":8,"value":1712,"toc":1934},[1713,1720,1723,1726,1730,1762,1766,1771,1781,1787,1790,1793,1797,1812,1816,1820,1823,1827,1830,1834,1838,1843,1847,1853,1857,1869,1899,1913,1916,1920],[11,1714,1715,1716,1719],{},"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 ",[23,1717,1718],{},"Chat"," tab in the right-hand tabs shows the same session conversation; selecting a work item only chooses where a new message is sent.",[11,1721,1722],{},"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.",[11,1724,1725],{},"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.",[15,1727,1729],{"id":1728},"chat-features","Chat Features",[65,1731,1732,1738,1744,1750,1756],{},[68,1733,1734,1737],{},[23,1735,1736],{},"Rich text editing",": bold, italic, links, lists, and code blocks",[68,1739,1740,1743],{},[23,1741,1742],{},"Private messages",": moderators and voters can mark a message as private",[68,1745,1746,1749],{},[23,1747,1748],{},"Thumbs up\u002Fdown",": react to messages with voting buttons",[68,1751,1752,1755],{},[23,1753,1754],{},"Edit and delete",": authors can edit or delete their own messages",[68,1757,1758,1761],{},[23,1759,1760],{},"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.",[15,1763,1765],{"id":1764},"sending-a-message","Sending a Message",[117,1767],{"alt":1768,"caption":1769,"stem":1770},"A rich chat message being composed with the Send button","Sending a message","guide-chat-sending",[11,1772,1773,1774,1777,1778,1780],{},"Write in the message box and press ",[23,1775,1776],{},"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 ",[23,1779,1776],{}," button never shows a spinner and never blocks you while the message is being saved.",[11,1782,1783,1784,1786],{},"In a planning session, a small note under ",[23,1785,1776],{}," reminds you that the chat history belongs to that planning session.",[11,1788,1789],{},"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.",[11,1791,1792],{},"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.",[15,1794,1796],{"id":1795},"message-details","Message Details",[11,1798,1799,1800,1803,1804,1807,1808,1811],{},"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 ",[23,1801,1802],{},"Edited"," tag, and a private message shows a ",[23,1805,1806],{},"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 ",[23,1809,1810],{},"Load more ..."," to load the next five until the full history is visible.",[15,1813,1815],{"id":1814},"reactions","Reactions",[117,1817],{"alt":1818,"caption":1815,"stem":1819},"A chat message with thumbs up and thumbs down reactions","guide-chat-reactions",[11,1821,1822],{},"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.",[15,1824,1826],{"id":1825},"editing-and-deleting","Editing and Deleting",[11,1828,1829],{},"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.",[15,1831,1833],{"id":1832},"private-messages","Private Messages",[117,1835],{"alt":1836,"caption":1742,"stem":1837},"A private chat message with the Private tag","guide-chat-private",[11,1839,127,1840,1842],{},[23,1841,1806],{}," 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.",[15,1844,1846],{"id":1845},"new-message-notifications","New Message Notifications",[11,1848,1849,1850,1852],{},"When a new message arrives while you are on another part of the panel, a red dot appears on the ",[23,1851,1718],{}," tab. Guests are not notified about private messages.",[15,1854,1856],{"id":1855},"planning-session-chat-without-a-selected-work-item","Planning Session Chat Without a Selected Work Item",[11,1858,754,1859,49,1861,111,1863,1865,1866,1868],{},[23,1860,1247],{},[23,1862,1250],{},[23,1864,1253],{},", the ",[23,1867,1718],{}," 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.",[65,1870,1871,1886,1891],{},[68,1872,754,1873,1875,1876,1878,1879,1882,1883,1885],{},[23,1874,1247],{},", the same chat appears in the selected work item's ",[23,1877,1718],{}," 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 ",[23,1880,1881],{},"Details"," tab with the no-selection message and a ",[23,1884,1718],{}," tab with the session conversation.",[68,1887,754,1888,1890],{},[23,1889,1250],{},", 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.",[68,1892,754,1893,1895,1896,1898],{},[23,1894,1253],{},", the side panel keeps the ",[23,1897,1718],{}," 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.",[11,1900,1901,1902,656,1904,1906,1907,1909,1910,1912],{},"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 ",[23,1903,1881],{},[23,1905,1718],{}," tabs in the Refinement\u002Fgrooming side panel and to the ",[23,1908,1718],{}," tab in alternative voting. Changing the focused work item never moves the Chat tab and never resets its messages or its ",[23,1911,1810],{}," position.",[11,1914,1915],{},"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.",[15,1917,1919],{"id":1918},"when-to-use-chat","When to Use Chat",[65,1921,1922,1925,1928,1931],{},[68,1923,1924],{},"Discussing estimation discrepancies during a voting round",[68,1926,1927],{},"Clarifying requirements before casting votes",[68,1929,1930],{},"Note-taking and context sharing during planning sessions",[68,1932,1933],{},"Quick polling with thumbs up\u002Fdown reactions",{"title":380,"searchDepth":1052,"depth":1052,"links":1935},[1936,1937,1938,1939,1940,1941,1942,1943,1944],{"id":1728,"depth":1052,"text":1729},{"id":1764,"depth":1052,"text":1765},{"id":1795,"depth":1052,"text":1796},{"id":1814,"depth":1052,"text":1815},{"id":1825,"depth":1052,"text":1826},{"id":1832,"depth":1052,"text":1833},{"id":1845,"depth":1052,"text":1846},{"id":1855,"depth":1052,"text":1856},{"id":1918,"depth":1052,"text":1919},"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",[1949,1950,1951],"planning poker chat","jira estimation","team collaboration",{},4,"\u002Fgetting-started\u002Fchat",{"title":1710,"description":1945},{"loc":1954,"lastmod":1069},"chat","guide\u002Fen\u002Fchat","guide\u002Fchat","DNSPlNCmCcrs8Sy4wEzGbw71zpOn9fhN12TIpMnpRtE",{"id":1962,"title":1963,"body":1964,"dateModified":2076,"datePublished":2077,"description":2078,"extension":1072,"heading":2079,"image":2080,"imageAlt":2079,"keywords":2081,"locale":1079,"meta":2084,"navigation":1081,"order":1059,"path":2085,"section":2086,"seo":2087,"sitemap":2088,"slug":2089,"stem":2090,"translationKey":2091,"__hash__":2092},"tutorials\u002Ftutorials\u002Fen\u002Fparametric-voting.md","Voting with 2 parameters | Tutorials | Scrumpy Planning Poker",{"type":8,"value":1965,"toc":2071},[1966,1969,1973,2013,2018,2022,2041,2045,2049,2066],[11,1967,1968],{},"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.",[15,1970,1972],{"id":1971},"set-up-the-parameters","Set up the parameters",[11,1974,1975,1976,1978,1979,1981,1982,656,1984,1987,1988,1991,1992,1995,1996,1999,2000,2003,2004,2006,2007,2009,2010,2012],{},"In the perspective settings, choose ",[23,1977,550],{}," in the ",[23,1980,431],{}," dropdown. Name the two parameters ",[23,1983,90],{},[23,1985,1986],{},"Value",", give each one a ",[23,1989,1990],{},"Minimum",", a ",[23,1993,1994],{},"Maximum",", and a ",[23,1997,1998],{},"Step",", then write the ",[23,2001,2002],{},"Formula"," from the variable names shown beside the fields, for example ",[378,2005,585],{}," where ",[378,2008,578],{}," is Risk and ",[378,2011,581],{}," 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.",[117,2014],{"alt":2015,"caption":2016,"stem":2017},"Perspective settings with the Parametric sequence, two parameters, and the formula","Parameter settings","tutorial-parametric-configure",[15,2019,2021],{"id":2020},"vote-with-the-sliders","Vote with the sliders",[11,2023,2024,2025,656,2027,2029,2030,2032,2033,2036,2037,2040],{},"During a session, each voter moves the ",[23,2026,90],{},[23,2028,1986],{}," sliders to the values that fit the work. The formula turns those positions into the result shown in large text with an ",[23,2031,497],{}," suffix, and a small badge on the right shows how far the rounded result is from the exact formula value. Press ",[23,2034,2035],{},"Vote"," to cast it, or ",[23,2038,2039],{},"Withdraw"," to take it back.",[117,2042],{"alt":2043,"caption":2021,"stem":2044},"The voting panel with two parameter sliders, the result, the deviation badge, and the Vote and Withdraw buttons","tutorial-parametric",[15,2046,2048],{"id":2047},"read-the-results","Read the results",[11,2050,127,2051,2053,2054,2056,2057,2059,2060,2062,2063,2065],{},[23,2052,678],{}," tab draws one dot per participant, so you can see how the votes spread across ",[23,2055,90],{}," on the horizontal axis and ",[23,2058,1986],{}," on the vertical axis, plus a dashed crosshair for the averaged positions. ",[23,2061,811],{}," averages the results each participant voted, while ",[23,2064,686],{}," 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.",[117,2067],{"alt":2068,"caption":2069,"stem":2070},"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":380,"searchDepth":1052,"depth":1052,"links":2072},[2073,2074,2075],{"id":1971,"depth":1052,"text":1972},{"id":2020,"depth":1052,"text":2021},{"id":2047,"depth":1052,"text":2048},"2026-11-02","2026-10-26","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",[2082,2083,1078],"parametric estimation","two parameter voting",{},"\u002Ftutorials\u002Fparametric-voting","tutorial",{"title":1963,"description":2078},{"loc":2085,"lastmod":2076},"parametric-voting","tutorials\u002Fen\u002Fparametric-voting","tutorial\u002Fparametric-voting","EhSG0Z-zoBeseXjyGKCs9c0MgMPBbErtVRUVNSYw8XU",[2094],{"heading":2095,"description":2096,"path":2097},"Comparison metrics for agile teams","Metrics should create equal ground, not a leaderboard. Four comparison metrics that motivate agile teams without punishing them.","\u002Fblog\u002Fcomparison-metrics-for-agile-teams",1795345557097]