[{"data":1,"prerenderedAt":1502},["ShallowReactive",2],{"tutorial-en-voting-with-custom-cards":3},{"doc":4,"prev":152,"next":275,"related":442},{"id":5,"title":6,"body":7,"dateModified":132,"datePublished":132,"description":133,"extension":134,"heading":121,"image":135,"imageAlt":121,"keywords":136,"locale":140,"meta":141,"navigation":142,"order":143,"path":144,"section":145,"seo":146,"sitemap":147,"slug":148,"stem":149,"translationKey":150,"__hash__":151},"tutorials\u002Ftutorials\u002Fen\u002Fvoting-with-custom-cards.md","Voting with custom cards | Tutorials | Scrumpy Planning Poker",{"type":8,"value":9,"toc":123},"minimark",[10,14,19,44,49,52,56,70,76,80,83,89,93,103,108,111,115,118],[11,12,13],"p",{},"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.",[15,16,18],"h2",{"id":17},"every-card-set-is-customizable","Every card set is customizable",[11,20,21,22,26,27,26,30,26,33,26,36,39,40,43],{},"Titles and custom images work on every card-based sequence: ",[23,24,25],"strong",{},"Regular",", ",[23,28,29],{},"Fibonacci",[23,31,32],{},"Tens",[23,34,35],{},"Fingers",[23,37,38],{},"Dice",", and ",[23,41,42],{},"T-Shirt",". Pick the sequence first, then change its titles, choose the active cards, and upload artwork. The same steps apply to each set.",[11,45,46,48],{},[23,47,42],{}," 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.",[11,50,51],{},"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.",[15,53,55],{"id":54},"start-with-a-t-shirt-perspective","Start with a T-shirt perspective",[11,57,58,59,61,62,65,66,69],{},"Open the perspective settings and choose ",[23,60,42],{}," in ",[23,63,64],{},"Sequence",". Tick the sizes the team uses under ",[23,67,68],{},"Available cards",". Only the ticked cards appear during voting, so a short list keeps the session focused.",[71,72],"docs-figure",{"alt":73,"caption":74,"stem":75},"The Available cards list for a T-shirt perspective with the selected sizes and their story points","T-shirt cards and story points","tutorial-custom-cards-configure",[15,77,79],{"id":78},"change-the-titles-and-the-story-points-on-t-shirt","Change the titles, and the story points on T-Shirt",[11,81,82],{},"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.",[11,84,85,86,88],{},"On ",[23,87,42],{},", 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.",[15,90,92],{"id":91},"upload-custom-card-images","Upload custom card images",[11,94,95,96,98,99,102],{},"Click any card preview in ",[23,97,68],{}," or ",[23,100,101],{},"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.",[71,104],{"alt":105,"caption":106,"stem":107},"The Upload card image dialog with the file browser and the PNG or JPG limits","Upload card image","tutorial-custom-cards-configure-images",[11,109,110],{},"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.",[15,112,114],{"id":113},"vote-with-the-custom-board","Vote with the custom board",[11,116,117],{},"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.",[71,119],{"alt":120,"caption":121,"stem":122},"The voting panel with custom titles and custom card artwork","Voting with custom cards","tutorial-custom-cards",{"title":124,"searchDepth":125,"depth":125,"links":126},"",2,[127,128,129,130,131],{"id":17,"depth":125,"text":18},{"id":54,"depth":125,"text":55},{"id":78,"depth":125,"text":79},{"id":91,"depth":125,"text":92},{"id":113,"depth":125,"text":114},"2026-10-29","Build your own planning poker deck: custom card titles, images and story point values for each card.","md","\u002Fog\u002Ftutorial-voting-with-custom-cards.jpg",[137,138,139],"custom cards","planning poker deck","estimation cards","en",{},true,7,"\u002Ftutorials\u002Fvoting-with-custom-cards","tutorial",{"title":6,"description":133},{"loc":144,"lastmod":132},"voting-with-custom-cards","tutorials\u002Fen\u002Fvoting-with-custom-cards","tutorial\u002Fvoting-with-custom-cards","ZmpaQYUlevOG4WnHeCljXE5_e-LcTChoQmaCOffDKgs",{"id":153,"title":154,"body":155,"dateModified":258,"datePublished":132,"description":259,"extension":134,"heading":260,"image":261,"imageAlt":260,"keywords":262,"locale":140,"meta":266,"navigation":142,"order":267,"path":268,"section":145,"seo":269,"sitemap":270,"slug":271,"stem":272,"translationKey":273,"__hash__":274},"tutorials\u002Ftutorials\u002Fen\u002Fvoting-with-tshirts.md","Voting with T-shirts | Tutorials | Scrumpy Planning Poker",{"type":8,"value":156,"toc":253},[157,160,164,172,175,186,190,194,197,214,229,234,241,245,248],[11,158,159],{},"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.",[15,161,163],{"id":162},"set-the-sizes-and-their-story-points","Set the sizes and their story points",[11,165,58,166,61,168,65,170,69],{},[23,167,42],{},[23,169,64],{},[23,171,68],{},[11,173,174],{},"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.",[11,176,177,178,181,182,185],{},"When ",[23,179,180],{},"Story points to hours"," 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 ",[23,183,184],{},"1 sp · 1 day 2 hours · M",".",[71,187],{"alt":188,"caption":74,"stem":189},"The Available cards list for a T-shirt perspective with the story points beside each size","tutorial-tshirt-configure",[15,191,193],{"id":192},"write-the-result-to-one-or-two-jira-fields","Write the result to one or two Jira fields",[11,195,196],{},"A T-shirt vote can update two Jira fields:",[198,199,200,208],"ul",{},[201,202,203,204,207],"li",{},"The ",[23,205,206],{},"story points field",", using the story point value configured for the chosen size (for example, S = 10).",[201,209,203,210,213],{},[23,211,212],{},"T-shirt field",", with the size label (for example, S).",[11,215,216,217,220,221,224,225,228],{},"Set ",[23,218,219],{},"Estimation target"," to ",[23,222,223],{},"Field",", then choose the fields you want. Choose both to update both. Leave a field as ",[23,226,227],{},"None"," when the team does not use it.",[71,230],{"alt":231,"caption":232,"stem":233},"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",[11,235,236,237,240],{},"With ",[23,238,239],{},"Default"," 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.",[15,242,244],{"id":243},"vote-with-the-size-cards","Vote with the size cards",[11,246,247],{},"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.",[71,249],{"alt":250,"caption":251,"stem":252},"The voting panel with the T-shirt size cards","Voting with T-shirt cards","tutorial-tshirt",{"title":124,"searchDepth":125,"depth":125,"links":254},[255,256,257],{"id":162,"depth":125,"text":163},{"id":192,"depth":125,"text":193},{"id":243,"depth":125,"text":244},"2026-10-31","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",[263,264,265],"t-shirt sizing","t shirt estimation","agile sizing",{},6,"\u002Ftutorials\u002Fvoting-with-tshirts",{"title":154,"description":259},{"loc":268,"lastmod":258},"voting-with-tshirts","tutorials\u002Fen\u002Fvoting-with-tshirts","tutorial\u002Fvoting-with-tshirts","-PvkZpXyh5ZpLS6tSG4ept2o2G7zNhCI0u_pSGBE3AE",{"id":276,"title":277,"body":278,"dateModified":425,"datePublished":425,"description":426,"extension":134,"heading":427,"image":428,"imageAlt":427,"keywords":429,"locale":140,"meta":433,"navigation":142,"order":434,"path":435,"section":145,"seo":436,"sitemap":437,"slug":438,"stem":439,"translationKey":440,"__hash__":441},"tutorials\u002Ftutorials\u002Fen\u002Festimation-log.md","Reading the estimation log | Tutorials | Scrumpy Planning Poker",{"type":8,"value":279,"toc":417},[280,283,287,302,305,310,317,321,324,368,374,381,385,388,392,395,399,406,410],[11,281,282],{},"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.",[15,284,286],{"id":285},"find-the-log-on-a-work-item","Find the log on a work item",[11,288,289,290,293,294,297,298,301],{},"Open the work item in Jira, expand the ",[23,291,292],{},"Activity"," area, open ",[23,295,296],{},"Apps",", and choose ",[23,299,300],{},"Estimation log",". The log lists the accepted estimates for the work item, newest first.",[11,303,304],{},"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.",[71,306],{"alt":307,"caption":308,"stem":309},"The estimation log on a work item","The estimation log","tutorial-estimation-log",[11,311,312,313,316],{},"A space administrator can hide the log by hiding both the Scrumpy panel on work items and the ",[23,314,315],{},"Estimations"," page in space settings. While either one is shown, the log stays available.",[15,318,320],{"id":319},"read-an-entry","Read an entry",[11,322,323],{},"Each entry is one accepted estimate:",[198,325,326,332,341,347,353,362],{},[201,327,328,331],{},[23,329,330],{},"Moderator",": the avatar of the person who accepted the estimate",[201,333,334,337,338],{},[23,335,336],{},"Completion",": how many of the required voters had voted, such as ",[23,339,340],{},"100% of required voters",[201,342,343,346],{},[23,344,345],{},"Perspective",": which estimation perspective produced the value",[201,348,349,352],{},[23,350,351],{},"Time",": when the estimate was accepted, in your Jira timezone",[201,354,355,358,359],{},[23,356,357],{},"Duration",": how long the vote took, for example ",[23,360,361],{},"for 4 minutes",[201,363,364,367],{},[23,365,366],{},"Result",": the accepted value in a badge, then every vote in the deck's labels and the people who cast them",[11,369,370,371,185],{},"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 ",[23,372,373],{},"Overridden by the moderator",[11,375,376,377,380],{},"Values follow the perspective: story points carry the ",[23,378,379],{},"sp"," suffix, a T-shirt perspective shows the size labels, and a time perspective shows a work-day duration.",[15,382,384],{"id":383},"move-through-the-history","Move through the history",[11,386,387],{},"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.",[15,389,391],{"id":390},"watch-the-log-during-a-session","Watch the log during a session",[11,393,394],{},"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.",[15,396,398],{"id":397},"see-the-trend-across-the-space","See the trend across the space",[11,400,401,402,405],{},"The estimation log is per work item. To see the whole space, open ",[23,403,404],{},"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.",[15,407,409],{"id":408},"know-how-long-the-history-stays","Know how long the history stays",[11,411,412,413,416],{},"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 ",[23,414,415],{},"Dashboard"," tab; that action cannot be undone. Archiving a planning session to Confluence keeps its estimates on a Confluence page beyond the 90 days.",{"title":124,"searchDepth":125,"depth":125,"links":418},[419,420,421,422,423,424],{"id":285,"depth":125,"text":286},{"id":319,"depth":125,"text":320},{"id":383,"depth":125,"text":384},{"id":390,"depth":125,"text":391},{"id":397,"depth":125,"text":398},{"id":408,"depth":125,"text":409},"2026-11-02","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",[430,431,432],"estimation log","estimation history","jira reporting",{},8,"\u002Ftutorials\u002Festimation-log",{"title":277,"description":426},{"loc":435,"lastmod":425},"estimation-log","tutorials\u002Fen\u002Festimation-log","tutorial\u002Festimation-log","gvxokZmR6GM9dzZGhZslUowlV8TY17qXctdhUNS8IHA",{"id":443,"title":444,"body":445,"dateModified":1484,"datePublished":1485,"description":1486,"extension":134,"heading":546,"image":1487,"imageAlt":546,"keywords":1488,"locale":140,"meta":1493,"navigation":142,"order":1474,"path":1494,"section":1495,"seo":1496,"sitemap":1497,"slug":1498,"stem":1499,"translationKey":1500,"__hash__":1501},"guide\u002Fguide\u002Fen\u002Festimation-perspectives.md","Estimation Perspectives | Scrumpy Planning Poker",{"type":8,"value":446,"toc":1467},[447,450,454,468,471,478,490,494,497,522,526,544,548,552,571,578,581,601,604,694,702,706,709,741,744,748,755,793,796,806,813,819,828,832,835,838,952,958,961,964,967,971,977,1134,1137,1140,1143,1150,1153,1176,1180,1210,1215,1220,1238,1244,1247,1269,1281,1286,1300,1306,1320,1323,1326,1329,1334,1348,1351,1357,1360,1385,1388,1391,1413,1416,1419,1423,1434,1461,1464],[11,448,449],{},"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,451,453],{"id":452},"working-week","Working week",[11,455,456,457,460,461,464,465,467],{},"At the top of the Settings tab, choose the ",[23,458,459],{},"Week starts on"," day and the ",[23,462,463],{},"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,466,463],{}," field turns red and explains what to change.",[11,469,470],{},"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,472,473,474,477],{},"Below the two day fields, ",[23,475,476],{},"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,479,480,481,26,483,486,487,489],{},"Next to ",[23,482,476],{},[23,484,485],{},"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,488,476],{},". 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,491,493],{"id":492},"why-multiple-perspectives","Why Multiple Perspectives?",[11,495,496],{},"Different estimation dimensions help your team look at work from several angles:",[198,498,499,505,510,516],{},[201,500,501,504],{},[23,502,503],{},"Points",": Relative complexity and effort",[201,506,507,509],{},[23,508,351],{},": Hours or days of work",[201,511,512,515],{},[23,513,514],{},"T-Shirt Sizes",": Coarse-grained sizing (XS, S, M, L, XL)",[201,517,518,521],{},[23,519,520],{},"Risk",": Likelihood or impact of unknowns",[15,523,525],{"id":524},"perspective-settings","Perspective Settings",[11,527,528,529,26,532,26,535,26,538,39,541,185],{},"Each perspective is configured through five sub-tabs: ",[23,530,531],{},"General",[23,533,534],{},"Voting",[23,536,537],{},"Cards",[23,539,540],{},"Estimation",[23,542,543],{},"Backup & Restore",[71,545],{"alt":546,"caption":546,"stem":547},"Estimation Perspectives","guide-perspectives",[549,550,531],"h3",{"id":551},"general",[11,553,203,554,556,557,560,561,39,564,567,568,570],{},[23,555,531],{}," tab holds the perspective's ",[23,558,559],{},"name",", optional ",[23,562,563],{},"description",[23,565,566],{},"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,569,566],{}," (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,572,573,574,577],{},"If no perspective applies to a work item's work type, the Scrumpy panel shows ",[23,575,576],{},"No voting perspective",", names the work type, and asks you to configure the space's perspective settings rather than showing an empty deck.",[11,579,580],{},"Below those fields, the General tab has three actions:",[198,582,583,589,595],{},[201,584,585,588],{},[23,586,587],{},"Reset to defaults",": Return the perspective to its initial settings, after a confirmation",[201,590,591,594],{},[23,592,593],{},"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",[201,596,597,600],{},[23,598,599],{},"Delete perspective",": Remove the perspective and all its sessions permanently, after a confirmation. The Default perspective cannot be deleted",[549,602,534],{"id":603},"voting",[605,606,607,620],"table",{},[608,609,610],"thead",{},[611,612,613,617],"tr",{},[614,615,616],"th",{},"Setting",[614,618,619],{},"Description",[621,622,623,634,644,654,664,674,684],"tbody",{},[611,624,625,631],{},[626,627,628],"td",{},[23,629,630],{},"Open voting",[626,632,633],{},"When on, participants see each other's votes in real time",[611,635,636,641],{},[626,637,638],{},[23,639,640],{},"Certainty",[626,642,643],{},"Shows how often participants re-voted during the session, not how spread the votes are. One vote per participant gives 100%",[611,645,646,651],{},[626,647,648],{},[23,649,650],{},"Variation",[626,652,653],{},"Shows how widely the vote values are spread around their average. Lower is better, and it needs at least two numeric votes",[611,655,656,661],{},[626,657,658],{},[23,659,660],{},"Automatic completion",[626,662,663],{},"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",[611,665,666,671],{},[626,667,668],{},[23,669,670],{},"Asynchronous voting",[626,672,673],{},"Participants vote at their own pace, without a countdown timer",[611,675,676,681],{},[626,677,678],{},[23,679,680],{},"Vote duration",[626,682,683],{},"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",[611,685,686,691],{},[626,687,688],{},[23,689,690],{},"Averaging",[626,692,693],{},"How votes are combined: Arithmetic mean, Geometric mean, Harmonic mean, Quadratic mean, Midrange, Median, Minimum, Maximum, Mode (most common), PERT, or Count",[11,695,696,697,185],{},"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 ",[698,699,701],"docs-link",{"to":700},"\u002Fgetting-started\u002Fvoting-session-controls","Voting Session Controls",[549,703,705],{"id":704},"mean-averaging","Mean averaging",[11,707,708],{},"Scrumpy offers five mean-based methods:",[198,710,711,717,723,729,735],{},[201,712,713,716],{},[23,714,715],{},"Arithmetic mean"," adds the votes and divides by the number of votes.",[201,718,719,722],{},[23,720,721],{},"Geometric mean"," multiplies the votes and takes the nth root.",[201,724,725,728],{},[23,726,727],{},"Harmonic mean"," divides the number of votes by the sum of their reciprocals.",[201,730,731,734],{},[23,732,733],{},"Quadratic mean"," squares the votes, averages the squares, and takes the square root.",[201,736,737,740],{},[23,738,739],{},"Midrange"," is halfway between the smallest and largest vote.",[11,742,743],{},"A zero vote makes the geometric and harmonic means zero. Every result is rounded to the nearest available card, like the other averaging methods.",[549,745,747],{"id":746},"pert-averaging","PERT averaging",[11,749,750,751,754],{},"PERT (Program Evaluation and Review Technique) is a three-point estimation method. When you choose ",[23,752,753],{},"PERT"," as the averaging method and the team has cast at least three different values, Scrumpy takes the three points from the votes themselves:",[605,756,757,767],{},[608,758,759],{},[611,760,761,764],{},[614,762,763],{},"Point",[614,765,766],{},"Meaning",[621,768,769,777,785],{},[611,770,771,774],{},[626,772,773],{},"Optimistic (O)",[626,775,776],{},"The smallest value voted",[611,778,779,782],{},[626,780,781],{},"Most Likely (M)",[626,783,784],{},"The average of every value strictly between the smallest and the largest",[611,786,787,790],{},[626,788,789],{},"Pessimistic (P)",[626,791,792],{},"The largest value voted",[11,794,795],{},"The estimate is the weighted PERT average:",[797,798,803],"pre",{"className":799,"code":801,"language":802},[800],"language-text","E = (O + 4M + P) \u002F 6\n","text",[804,805,801],"code",{"__ignoreMap":124},[11,807,808,809,812],{},"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,810,811],{},"Deviation",":",[797,814,817],{"className":815,"code":816,"language":802},[800],"deviation = (P - O) \u002F 6\n",[804,818,816],{"__ignoreMap":124},[11,820,821,822,824,825,827],{},"While ",[23,823,630],{}," 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,826,630],{}," is on.",[549,829,831],{"id":830},"count-averaging","Count averaging",[11,833,834],{},"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.",[549,836,537],{"id":837},"cards",[605,839,840,848],{},[608,841,842],{},[611,843,844,846],{},[614,845,616],{},[614,847,619],{},[621,849,850,859,868,878,888,898,908,921],{},[611,851,852,856],{},[626,853,854],{},[23,855,64],{},[626,857,858],{},"Choose the estimation style from the dropdown: Regular, Fibonacci, Tens, Fingers, Dice, T-Shirt, Free Scale, or Parametric",[611,860,861,865],{},[626,862,863],{},[23,864,68],{},[626,866,867],{},"Which cards from the sequence appear to voters during a session",[611,869,870,875],{},[626,871,872],{},[23,873,874],{},"Card titles",[626,876,877],{},"The name shown for each card, built in per card and editable",[611,879,880,885],{},[626,881,882],{},[23,883,884],{},"T-shirt story points",[626,886,887],{},"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",[611,889,890,895],{},[626,891,892],{},[23,893,894],{},"Extra cards",[626,896,897],{},"Fun cards for team morale (infinity, phoenix, cookie, buffalo, ping pong)",[611,899,900,905],{},[626,901,902],{},[23,903,904],{},"Custom images",[626,906,907],{},"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",[611,909,910,915],{},[626,911,912],{},[23,913,914],{},"Free scale range",[626,916,917,918,920],{},"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,919,379],{}," suffix. The converted duration appears only when the estimation target writes a time value (a time board or a Time field).",[611,922,923,927],{},[626,924,925],{},[23,926,180],{},[626,928,929,930,933,934,937,938,941,942,944,945,948,949,951],{},"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,931,932],{},"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,935,936],{},"1 sp · S",". The same units appear in the vote list, the result chart, the badge beside the narrowed ",[23,939,940],{},"Override"," dropdown, and the final result. When the estimation target is ",[23,943,223],{},", a non-zero conversion also shows the ",[23,946,947],{},"Time field"," for every sequence, including T-shirt. When ",[23,950,180],{}," 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,953,954,955,957],{},"Custom images are set per card and per sequence. The Available cards list shows the cards of the sequence selected in ",[23,956,64],{}," (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,959,960],{},"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,962,963],{},"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,965,966],{},"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.",[549,968,970],{"id":969},"parametric","Parametric",[11,972,973,974,976],{},"Choose ",[23,975,970],{}," 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.",[198,978,979,982,993,1007,1015,1080,1083,1086,1089,1108,1115,1128],{},[201,980,981],{},"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.",[201,983,984,985,988,989,992],{},"Press ",[23,986,987],{},"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,990,991],{},"Delete selected"," to remove them.",[201,994,995,996,26,999,1002,1003,1006],{},"The formula uses the parameter variables shown below the field: ",[804,997,998],{},"p1",[804,1000,1001],{},"p2",", and so on. For example, ",[804,1004,1005],{},"(p1 + p2) \u002F 2"," averages the first two parameters.",[201,1008,1009,1010,1012,1013,185],{},"The preview below the formula uses the same parameters voters see. Move a parameter to see the result update. When ",[23,1011,180],{}," is set, the preview appends the converted duration, for example ",[23,1014,932],{},[201,1016,1017,1018,26,1021,26,1024,26,1027,26,1030,26,1033,26,1036,26,1039,26,1042,26,1045,26,1048,26,1051,26,1054,26,1057,26,1060,26,1063,26,1066,26,1069,1072,1073,1076,1077,185],{},"The formula supports ",[804,1019,1020],{},"+",[804,1022,1023],{},"-",[804,1025,1026],{},"*",[804,1028,1029],{},"\u002F",[804,1031,1032],{},"^",[804,1034,1035],{},"%",[804,1037,1038],{},"min",[804,1040,1041],{},"max",[804,1043,1044],{},"round",[804,1046,1047],{},"floor",[804,1049,1050],{},"ceil",[804,1052,1053],{},"abs",[804,1055,1056],{},"sqrt",[804,1058,1059],{},"sin",[804,1061,1062],{},"cos",[804,1064,1065],{},"tan",[804,1067,1068],{},"log",[804,1070,1071],{},"exp",", and the constants ",[804,1074,1075],{},"pi"," and ",[804,1078,1079],{},"e",[201,1081,1082],{},"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.",[201,1084,1085],{},"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.",[201,1087,1088],{},"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.",[201,1090,1091,1092,1095,1096,1099,1100,1103,1104,1107],{},"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,1093,1094],{},"Results"," with the chart, and the chart tab. A two-parameter perspective shows ",[23,1097,1098],{},"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,1101,1102],{},"Radar"," with one polygon per participant and a dotted averaged polygon. The final result and averaging controls stay below both tabs, and the ",[23,1105,1106],{},"Parameters"," averaging mode averages each position and then applies the formula.",[201,1109,1110,1111,1114],{},"In the planning table each work item's parametric cell shows the result with an ",[23,1112,1113],{},"Edit vote"," control that opens the sliders and a cross-circle control that withdraws the vote. The result is never typed in directly.",[201,1116,1117,1118,26,1121,39,1124,1127],{},"In bulk voting a parametric perspective also has a selectable row with ",[23,1119,1120],{},"Affinity",[23,1122,1123],{},"Dot",[23,1125,1126],{},"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.",[201,1129,1130,1131,1133],{},"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,1132,180],{}," is set.",[11,1135,1136],{},"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,1138,1139],{},"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,1141,1142],{},"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,1144,1145,1146,1149],{},"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,1147,1148],{},"M",", during voting. The size label is written to Jira only when the perspective writes a T-shirt field.",[11,1151,1152],{},"To edit T-shirt story points:",[1154,1155,1156,1159,1164,1170],"ol",{},[201,1157,1158],{},"Open the perspective settings.",[201,1160,1161,1162,185],{},"Go to ",[23,1163,537],{},[201,1165,973,1166,61,1168,185],{},[23,1167,42],{},[23,1169,64],{},[201,1171,1172,1173,1175],{},"In ",[23,1174,68],{},", change the number next to a card title.",[549,1177,1179],{"id":1178},"estimation-target","Estimation Target",[605,1181,1182,1190],{},[608,1183,1184],{},[611,1185,1186,1188],{},[614,1187,616],{},[614,1189,619],{},[621,1191,1192,1201],{},[611,1193,1194,1198],{},[626,1195,1196],{},[23,1197,239],{},[626,1199,1200],{},"Use Jira's built-in board estimation (recommended). The first board is selected automatically, and a link opens the board's estimation settings",[611,1202,1203,1207],{},[626,1204,1205],{},[23,1206,223],{},[626,1208,1209],{},"Write to custom Jira fields for story points, time tracking, or T-shirt sizes",[11,1211,1212,1213,185],{},"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,1214,239],{},[11,1216,203,1217,1219],{},[23,1218,239],{}," 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,1221,203,1222,1225,1226,26,1229,39,1231,1234,1235,1237],{},[23,1223,1224],{},"Estimation board"," list groups boards under ",[23,1227,1228],{},"Story points",[23,1230,351],{},[23,1232,1233],{},"No estimation",". Boards without an estimation field appear under ",[23,1236,1233],{}," 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,1239,1240,1241,1243],{},"The estimation board also decides where the perspective appears in Capacity planning. When the target is ",[23,1242,239],{}," 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,1245,1246],{},"When you use the Field target, the fields shown depend on the sequence and conversion:",[198,1248,1249,1255,1261],{},[201,1250,1251,1254],{},[23,1252,1253],{},"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",[201,1256,1257,1260],{},[23,1258,1259],{},"Story Points",": A number field for story point values, shown for the numeric sequences and optionally for T-shirt perspectives",[201,1262,1263,1265,1266,1268],{},[23,1264,351],{},": A time tracking field for hour-based estimates, shown only when ",[23,1267,180],{}," is set to a non-zero value",[11,1270,1271,1272,1274,1275,1277,1278,1280],{},"With the ",[23,1273,239],{}," 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,1276,212],{}," also appears right next to the ",[23,1279,1224],{}," selector so the same accepted estimate can be written as its size label to that field as well.",[11,1282,1271,1283,1285],{},[23,1284,223],{}," 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,1287,1271,1288,1290,1291,1293,1294,1296,1297,1299],{},[23,1289,223],{}," 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,1292,223],{}," choice stays selected while you pick a field, so the setting does not jump back to ",[23,1295,239],{},". The Time field is hidden for every sequence when ",[23,1298,180],{}," is 0 or empty, and its saved selection is cleared.",[11,1301,1302,1303,1305],{},"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,1304,239],{}," 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,1307,1308,1309,1312,1313,1315,1316,1319],{},"Below the estimation fields, ",[23,1310,1311],{},"Preview"," shows a sample accepted estimate using the same formatting as the voting panel. The sample follows the selected fields and the ",[23,1314,180],{}," mapping, so it can show story points, the converted duration, and the T-shirt size together, for example ",[23,1317,1318],{},"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,1321,1322],{},"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,1324,1325],{},"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.",[549,1327,543],{"id":1328},"backup-restore",[11,1330,203,1331,1333],{},[23,1332,543],{}," tab holds:",[198,1335,1336,1342],{},[201,1337,1338,1341],{},[23,1339,1340],{},"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",[201,1343,1344,1347],{},[23,1345,1346],{},"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,1349,1350],{},"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,1352,1353,1356],{},[23,1354,1355],{},"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,1358,1359],{},"Changing any of these ends the running sessions for the perspective:",[198,1361,1362,1365,1368,1371,1374,1377,1380,1383],{},[201,1363,1364],{},"The card sequence",[201,1366,1367],{},"The active cards of the sequence",[201,1369,1370],{},"The extra cards",[201,1372,1373],{},"The free scale minimum or maximum",[201,1375,1376],{},"The parametric parameters and the parametric formula",[201,1378,1379],{},"The vote duration",[201,1381,1382],{},"Auto-complete",[201,1384,670],{},[11,1386,1387],{},"Reset to defaults also ends them, because it resets the settings above.",[11,1389,1390],{},"Changing any of these never ends a session, even while people are voting:",[198,1392,1393,1396,1399,1402,1405,1408,1410],{},[201,1394,1395],{},"The name, the description, and the Work types",[201,1397,1398],{},"Open voting, certainty, and variation",[201,1400,1401],{},"The averaging method",[201,1403,1404],{},"Card titles and card images",[201,1406,1407],{},"The T-shirt story points",[201,1409,180],{},[201,1411,1412],{},"The estimation target, the estimation board, and the estimation fields",[11,1414,1415],{},"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,1417,1418],{},"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,1420,1422],{"id":1421},"managing-perspectives","Managing Perspectives",[11,1424,1425,1426,1429,1430,1433],{},"In the space settings page, each perspective is a tab, and you can add more with ",[23,1427,1428],{},"Add new perspective",". A new perspective starts with the name ",[23,1431,1432],{},"New view","; rename it to a short, recognizable name. For each perspective you can:",[198,1435,1436,1441,1446,1451,1456],{},[201,1437,1438,1440],{},[23,1439,587],{}," (General): Return the perspective to its initial settings",[201,1442,1443,1445],{},[23,1444,593],{}," (General): Immediately cancel all active voting sessions for the perspective. This cannot be undone, and all participants lose their current votes",[201,1447,1448,1450],{},[23,1449,599],{}," (General): Remove the perspective and all its sessions permanently. The Default perspective cannot be deleted",[201,1452,1453,1455],{},[23,1454,1340],{}," (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",[201,1457,1458,1460],{},[23,1459,1346],{}," (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,1462,1463],{},"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,1465,1466],{},"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":124,"searchDepth":125,"depth":125,"links":1468},[1469,1470,1471,1483],{"id":452,"depth":125,"text":453},{"id":492,"depth":125,"text":493},{"id":524,"depth":125,"text":525,"children":1472},[1473,1475,1476,1477,1478,1479,1480,1481,1482],{"id":551,"depth":1474,"text":531},3,{"id":603,"depth":1474,"text":534},{"id":704,"depth":1474,"text":705},{"id":746,"depth":1474,"text":747},{"id":830,"depth":1474,"text":831},{"id":837,"depth":1474,"text":537},{"id":969,"depth":1474,"text":970},{"id":1178,"depth":1474,"text":1179},{"id":1328,"depth":1474,"text":543},{"id":1421,"depth":125,"text":1422},"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.","\u002Fog\u002Fguide-estimation-perspectives.jpg",[1489,1490,1491,1492],"estimation perspectives","jira story points","pert estimation","planning poker",{},"\u002Fgetting-started\u002Festimation-perspectives","guide",{"title":444,"description":1486},{"loc":1494,"lastmod":1484},"estimation-perspectives","guide\u002Fen\u002Festimation-perspectives","guide\u002Festimation-perspectives","G6e_NyDdXo7KjkRHJalTURKglnw_qMcVk88OAPmeSPw",1795345576525]