[{"data":1,"prerenderedAt":1792},["ShallowReactive",2],{"guide-en-sprint-standups":3},{"doc":4,"prev":882,"next":1494,"related":1495,"reading":1787},{"id":5,"title":6,"body":7,"dateModified":860,"datePublished":861,"description":862,"extension":863,"heading":864,"image":865,"imageAlt":864,"keywords":866,"locale":870,"meta":871,"navigation":872,"order":873,"path":874,"section":875,"seo":876,"sitemap":877,"slug":878,"stem":879,"translationKey":880,"__hash__":881},"guide\u002Fguide\u002Fen\u002Fsprint-standups.md","Sprint standups | Scrumpy Planning Poker",{"type":8,"value":9,"toc":841},"minimark",[10,19,30,35,40,60,64,117,120,124,135,152,155,166,187,191,198,204,208,233,250,280,284,300,304,316,320,325,331,336,386,390,402,411,414,419,491,495,513,539,543,555,613,628,713,716,720,729,736,751,755,774,783,791,795,798,827,831,838],[11,12,13,14,18],"p",{},"The ",[15,16,17],"strong",{},"Standup"," tab reviews one sprint, one board, or one saved filter inside a planning session. Work items are shown in the lanes of the selected scope, in a shared standup order that starts as the order Jira returns. Every planning session keeps its own data for each board and sprint, and for each filter. Switching planning sessions shows that session's data, and when the session you last opened is no longer available, the first planning session opens instead. The assignee avatar is on each card, but assignee grouping does not control the position. Status moves stay stored in the standup session until you apply them to Jira.",[11,20,21,22,25,26,29],{},"The side panel gives you two compact views of the same standup. The ",[15,23,24],{},"Status"," table groups the work by board column, and the ",[15,27,28],{},"Assignee"," table groups it by person. Both show the same flags, passed checks, staged changes, and estimates as the board.",[11,31,32],{},[15,33,34],{},"Everything you change on this screen is virtual: status moves, flags, the order, and the work items you add from a filter stay in Scrumpy. Jira changes only when you select Apply.",[36,37,39],"h2",{"id":38},"before-you-start","Before you start",[41,42,43,51,54,57],"ul",{},[44,45,46,47,50],"li",{},"Moderators can create a new planning session with the ",[15,48,49],{},"Create"," button at the top of the tab.",[44,52,53],{},"The space does not need a board. When the space has a board, the standup uses the board and, on a Scrum board with a running sprint, that sprint. When the space has no board, the standup reads a saved Jira filter.",[44,55,56],{},"A planning session must exist. Moderators choose the shared board, sprint, or filter. Locked participants follow that selection.",[44,58,59],{},"The standup is locked by the space password when one is set.",[36,61,63],{"id":62},"choose-what-the-standup-shows","Choose what the standup shows",[65,66,67,73,87,101,111,114],"ol",{},[44,68,69,70,72],{},"Open the ",[15,71,17],{}," tab and pick a planning session from the tabs above the board.",[44,74,75,78,79,82,83,86],{},[15,76,77],{},"The space has a board:"," pick a ",[15,80,81],{},"board",". If the board is a Scrum board with a running sprint, pick a ",[15,84,85],{},"sprint"," too. The sprint list shows only the sprints that are currently running; sprints that already ended and sprints that have not started yet are not listed. When the board has no running sprint, the sprint selector is hidden and the standup shows the work items currently on the board. Only a moderator changes the shared board. A voter or guest can pick another sprint locally, which detaches the viewer from the moderator.",[44,88,89,92,93,96,97,100],{},[15,90,91],{},"The space has no board:"," the board selector and the sprint selector are hidden. Pick a saved ",[15,94,95],{},"filter",", and the standup shows only the work items that filter returns from this space. The filter selector sits in the toolbar next to the ",[15,98,99],{},"estimate perspective"," selector. The perspective selector chooses whose estimate the cards show; the default perspective is selected at first. While no filter is selected, the toolbar asks you to choose one and the standup shows no work items. A voter or guest can pick another filter or perspective locally, which detaches the viewer from the moderator.",[44,102,103,104,107,108,110],{},"Use the ",[15,105,106],{},"Max per column"," dropdown before the columns selector to cap how many work items each column shows. The options are 5, 10, 15, 25, 50, 100, 150, and 200, and the default is 15. The standup reads up to 200 work items for the selected scope in one read, and the dropdown only filters the loaded work items. Changing the cap does not read Jira again. A column with more work items than the cap shows a left-aligned hint at its bottom. A capped column ends with a hint that shows the number shown and the number loaded, for example showing 15 of 23. The numbers sit in badges on one vertically centered line. Work items beyond the cap are already loaded when the scope read includes them and stay hidden until you raise the cap. A work item the standup loaded before it was hidden keeps its place in the shared order and its staged changes. A moderator shares the cap with everyone who is locked to the moderator. If you pick another cap while you are locked, you detach and keep your own choice in this browser tab. The same cap applies to the ",[15,109,24],{}," tab: each column lists only the first work items up to the cap, and a capped column ends with the same hint row. The hint row is not a work item and cannot be dragged.",[44,112,113],{},"Next to the limit dropdown, use the columns multi-select to choose which columns are shown. It starts empty and shows every column. Select one or more columns to show only those, or clear the selection to show all again. A moderator shares the visible columns with everyone who is locked to the moderator. If you pick another selection while you are locked, you detach and keep your own choice in this browser tab.",[44,115,116],{},"The sprint name and goal sit above the lanes. The link icon opens the sprint in the Jira backlog in a new browser tab. A board without a running sprint hides that line completely, so the lanes start right under the toolbar. A filter standup shows the filter name instead.",[11,118,119],{},"Work items that belong to another space are never shown, even when the selected sprint, board, or filter includes them. The per-column cap counts only the work items of this space.",[36,121,123],{"id":122},"add-work-items-from-a-filter","Add work items from a filter",[11,125,126,127,130,131,134],{},"A moderator can stage more work items for the sprint from the standup. The ",[15,128,129],{},"Add from filter"," button sits next to the primary ",[15,132,133],{},"Edit"," button at the start of the bottom action bar, and it appears only while the standup shows a running sprint.",[65,136,137,143,146],{},[44,138,139,140,142],{},"Select ",[15,141,129],{},".",[44,144,145],{},"Pick a saved Jira filter, an active sprint, or the backlog. The dialog previews the work items of the choice.",[44,147,148,149,142],{},"Select the work items you want, then select ",[15,150,151],{},"Add",[11,153,154],{},"To start over, clear the picker. The chosen source is dropped, the search box empties, and the first 100 shared filters return.",[11,156,157,158,161,162,165],{},"The work items appear in their status columns with a ",[15,159,160],{},"New"," badge. Every participant sees them right away, like a staged status move. You can still move, flag, or reassign a staged work item. Jira is not changed until a moderator selects ",[15,163,164],{},"Apply",", which moves the staged work items into the sprint together with the other standup changes. After Apply the badge disappears and the work items are part of the sprint.",[41,167,168,171,174,177,184],{},[44,169,170],{},"Work items that already belong to the sprint, or that belong to another space, cannot be selected.",[44,172,173],{},"A work item that sits in another sprint moves to this sprint on Apply.",[44,175,176],{},"A staged work item in a status that is not mapped to a board column stays hidden, like any other work item.",[44,178,179,180,183],{},"To remove one staged work item before Apply, select its undo button. ",[15,181,182],{},"Discard changes"," removes every staged work item with the other staged changes.",[44,185,186],{},"If Jira refuses to add a work item, it stays staged and the error names it.",[36,188,190],{"id":189},"read-the-board","Read the board",[11,192,193,194,197],{},"Each column of the selected board is a lane, in the board's configured order. In a filter standup, each status of the space is a lane, ordered by status category. Every visible column shares the width of the board equally, so all columns stay side by side and get narrower as you show more of them. Work items whose status is not mapped to a column are not shown on a board. Inside a lane, work items follow the shared standup order. The lanes start in the order the sprint shows on the board the first time you open the standup. That is the only time the Jira order is used. From then on the standup keeps its own order and every participant sees it. A work item that joins a sprint later, or whose status changes in Jira, appears at the bottom of its column and keeps that place. A reorder someone makes in the Jira backlog never changes the standup order. The order is not grouped by assignee. Each card keeps the note look of a retrospective note: the accent border, the regular assignee avatar, the priority icon, the work item key as a link, and the estimate badge at the top right, the summary in a two-line subtle inline text area, and the action row. The priority icon appears when the work item has a priority; hover it to see the priority name. The key link opens the work item in the Jira view issue dialog. A work item the team has passed shows a small green check right of its key. At the top right, a badge shows the estimate of the work item: story points when the selected board estimates in story points, a duration when it estimates in time. A work item without an estimate shows no badge. The card does not show the last updated time. The rounded card border uses a light accent color from the Atlassian palette. Every card assigned to the same person uses the same border color, different assignees get different colors, and an unassigned card keeps the usual own or other assignee border. An unselected card background stays neutral. A selected card uses a light tint of its own border color. When an assignee is marked absent, that person's cards replace the assignee color with a gray border, and the avatar and text on those cards are dimmed. Own work items align to the right of the lane and other assignees' work items to the left. A card without an assignee shows the same empty avatar image as a retrospective note without an avatar. The status is shown by the column, not repeated on the card. A moderator can edit the summary in place: select the summary, change it in the two-line text area, then click away. The summary saves when the field loses focus. Voters and guests see the summary read only. The inline text area is left aligned, shows the ",[15,195,196],{},"Work item summary"," placeholder, and grows vertically when the summary is long.",[199,200],"docs-figure",{"alt":201,"caption":202,"stem":203},"The standup board with cards in every column, the max per column selector, and the shared countdown","The standup board","guide-standup",[36,205,207],{"id":206},"details-chat-and-sound","Details, chat, and sound",[11,209,210,211,213,214,216,217,220,221,224,225,227,228,230,231,142],{},"A side panel sits to the right of the standup. It has a ",[15,212,24],{}," tab and an ",[15,215,28],{}," tab on the left, then ",[15,218,219],{},"Details"," or the perspective tabs when a work item is selected, and the ",[15,222,223],{},"Chat"," tab on the right, followed by the red video link icon when the planning session has one, your role badge, and the sound bell. The side panel is 400px wide. When nothing is selected, it shows ",[15,226,24],{},", ",[15,229,28],{},", and ",[15,232,223],{},[11,234,235,236,239,240,227,242,227,244,246,247,249],{},"The moderator chooses which tab everyone sees. Locked participants follow the tab as the moderator changes it. When you detach from the moderator, you can choose your own tab. A yellow ",[15,237,238],{},"M"," badge marks the tab the moderator has open: ",[15,241,24],{},[15,243,28],{},[15,245,219],{},", a perspective tab, or ",[15,248,223],{},". Every non-moderator sees it, whether they follow the moderator or browse on their own, so the moderator's current tab is always clear.",[41,251,252,257,262,274,277],{},[44,253,254,256],{},[15,255,223],{}," always shows the full session conversation: every message sent from the planning session, plus messages sent from outside the session for every work item the standup shows, ordered by publish time, and every work item message keeps its work item key link. The focused work item only chooses where a new message is sent: that work item's chat. With no work item selected, a new message goes to the planning-session chat. The conversation and the selected Chat tab stay the same when you change the focused work item, and the conversation is shared with the other tabs that open the same planning session.",[44,258,259,261],{},[15,260,219],{}," appears on the left when a work item is selected and no perspective tab is shown. It shows the summary and description of the selected work item. A moderator can edit both; voters and guests see them read only.",[44,263,264,267,268,270,271,273],{},[15,265,266],{},"Perspective tabs"," appear before ",[15,269,223],{}," when a work item is selected. Each tab is a perspective whose estimation target is the board and whose estimation board matches the board selected in the Standup. A perspective for another board does not appear. A perspective tab already shows the work item details, so ",[15,272,219],{}," is hidden while at least one perspective tab is shown. The tabs disappear when no work item is selected.",[44,275,276],{},"The bell at the right of the tabs controls sound notifications for the active chat. Select it once to turn sound on. The bell starts muted.",[44,278,279],{},"The role badge before the bell links to the Permissions settings.",[36,281,283],{"id":282},"flag-a-work-item","Flag a work item",[11,285,286,287,290,291,293,294,296,297,299],{},"A flag marks a work item that needs attention. The flag button sits at the right of the card action row, before the ",[15,288,289],{},"Move to"," dropdown. It shows the Jira flag: a work item that is already flagged in Jira opens with a red flag. Select the flag button on an unflagged work item to stage a flag, then press ",[15,292,164],{}," to write the Jira Flagged field. Select a red flag to stage clearing it, then press ",[15,295,164],{}," to clear the flag in Jira. Selecting the same button again before Apply returns the work item to the Jira state. The flag is shared with every participant as soon as you select it, but Jira is not changed until Apply. If Jira refuses the change, the flag stays staged and the error names the affected work items. A moderator can flag any work item, and a voter can flag only the work items assigned to them. Guests see the flag and its tooltip but cannot change it. ",[15,298,182],{}," also removes the flag changes you can discard once you confirm. The flag belongs to the standup session and is not a separate Jira comment or label. Selecting the flag changes the button at once, and the participant who selected it ignores the echo of their own change, so a delayed echo cannot undo a newer toggle.",[36,301,303],{"id":302},"mark-the-work-item-under-discussion","Mark the work item under discussion",[11,305,306,307,309,310,312,313,315],{},"A moderator clicks the card of the work item the team is discussing. The card itself is the click target: the avatar, the key, the priority, the estimate badge, the summary, and the empty space around them all select the work item. The flag button, the bulk checkbox, and the ",[15,308,289],{}," dropdown in the card action row keep their own behavior and do not change the selection. The whole card is highlighted for everyone who is locked to the moderator until the moderator clicks it again. A voter or guest can click a card to highlight it locally, which detaches the viewer without changing the shared selection. The shared selection changes immediately without reloading the board. The selecting participant ignores the echo of their own selection, so a delayed echo cannot move the highlight back. Every non-moderator also sees an ",[15,311,238],{}," badge on the work item the moderator has selected. The badge stays visible whether you follow the moderator or view the standup locally, so the moderator's current work item is always clear. When you can also check that card, the badge sits to the right of the checkbox. A small left-aligned hint below the columns and above the action bar also explains that a moderator selects a work item by clicking the card, that the shared selection is between the participants, and that ",[15,314,164],{}," must be pressed to synchronize the changes with Jira.",[36,317,319],{"id":318},"check-the-work-in-the-status-table","Check the work in the Status table",[11,321,13,322,324],{},[15,323,24],{}," tab is the first tab of the side panel. It lists every work item of the sprint, of the board when no sprint is running, or of the selected filter, in one table. Each board column is a wide row with its name in the center, and the work items of that column sit under it. Only the columns you show on the board appear here.",[11,326,327,328,330],{},"Use this table when you want to walk the sprint in order without scanning the full board. The ",[15,329,106],{}," cap applies here too, so a crowded column ends with the same hint row as the board.",[199,332],{"alt":333,"caption":334,"stem":335},"The Status table with work items grouped under each board column","The Status table","guide-standup-status",[41,337,338,341,353,359,362,371,374,377,380],{},[44,339,340],{},"Each row shows the work type icon, the priority icon, the flag button, the work item key, a green check when the work item is passed, the undo button, and the estimate. The key opens the work item in Jira.",[44,342,343,344,346,347,349,350,352],{},"The narrow column after the work item key shows a green check once the team has passed the work item. A work item is passed when the moderator forwards its countdown, or when the moderator selects another work item or clears the selection after its countdown has run out. A countdown that only runs out does not mark it. The check appears in the same place in the ",[15,345,28],{}," tab and next to the key on the card, and it stays for the rest of the planning session and scope. A passed check counts as a change, so ",[15,348,182],{}," removes every check for everyone in the standup, and ",[15,351,164],{}," clears them too when it writes the staged changes.",[44,354,355,356,358],{},"A moderator has a radio button in the first column to select the work item under discussion. Everyone else sees a yellow ",[15,357,238],{}," badge in the first column, on the work item the moderator selected, and a radio button for their own selection. The table and the board keep the same selection: pick a work item in one place and the other follows.",[44,360,361],{},"Drag a work item to change its place in its column. The row and the board move at once, before the change is saved. The person who dragged ignores the echo of their own change, so a delayed echo cannot move the row back or undo a newer drop.",[44,363,364,365,367,368,370],{},"Drop a work item into another column to move it there. This works only when the ",[15,366,289],{}," menu of that work item offers a status of that column and the work item has no staged move. If the choices for that work item have not been read yet, the board reads them first and then drops the work item. A work item with a staged move keeps its place, just like its disabled ",[15,369,289],{}," menu, until you undo or apply that move. Otherwise the row returns to its place. A dismissible warning explains why.",[44,372,373],{},"A moderator can drag every work item. A voter can drag only the work items assigned to them. Guests can read the table but cannot change it.",[44,375,376],{},"Select the flag button to stage a flag or clear it, exactly like the flag on a card.",[44,378,379],{},"The undo button appears on a work item with a staged change: a moved place, a staged status move, or a staged flag. The card on the board shows the same undo button at the same time. Select either one to remove the staged change without changing Jira. You see the button only when you may discard that change, so a guest or another person's work item shows no undo button. Undoing a staged flag returns the work item to its original Jira flag state.",[44,381,382,383,385],{},"Press ",[15,384,164],{}," to write the new order to the sprint rank. On a board without a sprint, the board rank is written instead. In a filter standup there is no board to rank, so the order stays in the standup and only the status and flag changes reach Jira.",[36,387,389],{"id":388},"check-who-works-on-what-in-the-assignee-table","Check who works on what in the Assignee table",[11,391,13,392,394,395,397,398,401],{},[15,393,28],{}," tab follows ",[15,396,24],{}," in the side panel. It groups the same work items by the person doing them. Each assignee is a wide row with the person's name in the center, and that person's work items sit under it. ",[15,399,400],{},"Unassigned"," sits last and holds the work items that have no assignee.",[11,403,13,404,406,407,410],{},[15,405,106],{}," cap applies here too, so the table lists only the work items the board shows. A person whose work items all sit beyond the cap is not listed, in the table or in the ",[15,408,409],{},"Participants"," picker, until you raise the cap.",[11,412,413],{},"Use this table when you want to see how the sprint is spread across the team, or when you need to hand a work item to someone else. The presence checkbox at the left of each row shows who is taking part in the standup.",[199,415],{"alt":416,"caption":417,"stem":418},"The Assignee table with one person marked absent","The Assignee table","guide-standup-assignee",[41,420,421,427,436,439,442,448,457,462,468,477,483,486],{},[44,422,423,424,426],{},"The rows show the same facts as the ",[15,425,24],{}," tab: the work type icon, the priority icon, the flag button, the work item key, the same green passed check, the undo button, and the estimate. The check appears in the same column here, so both tables show how far the team has got.",[44,428,429,430,432,433,435],{},"Drag a work item into another assignee's row to give it to that person. The change appears for everyone right away, but Jira is not changed until you press ",[15,431,164],{},". The board avatar, the card color, and the ",[15,434,24],{}," row show the new person too. The row moves as soon as you drop it, and the person who dragged ignores the echo of their own change, so a delayed echo cannot put the row back or undo a newer drop.",[44,437,438],{},"The work items inside a row keep the board order. Dragging a work item inside its own row does not change anything, because the board order decides the order here.",[44,440,441],{},"A moderator can give any work item to another person. A voter can give only their own work items. Guests can read the table but cannot change it.",[44,443,444,445,447],{},"Below the table and the hint, a moderator can use the ",[15,446,409],{}," picker. It lists every participant whose presence checkbox is checked. Add a person who has no work items in this scope and they get their own row right away, taking part like every other assignee; drag a work item into that row to give it to them. Clear a person in the picker to remove them from the standup. A person who still has work items keeps their row, with the checkbox unchecked and disabled, while a person with no work items loses their row. Adding or removing a participant is shared right away and is saved immediately. Work items already staged to a removed person keep their row until you discard or apply the change.",[44,449,450,451,453,454,456],{},"An assignee change puts the undo button on the ",[15,452,28],{}," row, the ",[15,455,24],{}," row, and the card. Select it to return the work item to its Jira assignee without changing Jira.",[44,458,382,459,461],{},[15,460,164],{}," to write the new assignee to Jira. A rejected change stays staged and the error names the affected work items.",[44,463,464,465,467],{},"A moderator can clear the checkbox at the left of an assignee row to remove that person from the ",[15,466,409],{}," picker and mark them absent. The checkbox is checked by default for every assignee, and only a moderator can change it. Once cleared, the checkbox stays disabled because the person's work items still belong to them; add them back in the picker to check it again. Voters and guests see the checkbox but cannot change it.",[44,469,470,471,473,474,476],{},"When an assignee is absent, their work items cannot be selected from the ",[15,472,28],{}," table, from the ",[15,475,24],{}," table, or by clicking the card on the board. Their cards use a gray border and dimmed text and avatar, so you can tell them apart at a glance. They also lose the countdown pause, resume, and forward controls.",[44,478,479,480,482],{},"With the ",[15,481,28],{}," tab open, the countdown forward button moves to the next work item in this table. It skips every absent assignee and stops at the first work item of the next present assignee. On any other tab, the forward button keeps following the board order.",[44,484,485],{},"The presence choice is shared right away, stays after a reload, and resets when the selected board, sprint, or filter changes. If you change several checkboxes quickly, every checkbox keeps your latest choice.",[44,487,488,490],{},[15,489,400],{}," is always shown and is always treated as present. It has no presence checkbox.",[36,492,494],{"id":493},"follow-the-moderator","Follow the moderator",[11,496,497,498,500,501,227,504,227,507,230,509,512],{},"Voters and guests start locked to the moderator. While locked, you follow the moderator's work item, sprint, board, ",[15,499,106],{}," cap, visible columns, and side panel tab. The moderator's changes arrive right away. You also follow the moderator's space page tab, so the page moves between ",[15,502,503],{},"Refinement\u002Fgrooming",[15,505,506],{},"Capacity planning",[15,508,17],{},[15,510,511],{},"Retrospective"," for the same planning session.",[41,514,515,521,527,530,536],{},[44,516,517,520],{},[15,518,519],{},"Lock to moderator"," applies to the planning tab you are on. Switching to another planning tab yourself clears it, so you start detached on the new tab. A move caused by the moderator's tab change keeps it checked.",[44,522,523,524,526],{},"Clear ",[15,525,519],{}," to browse on your own. You can click another card, pick another tab, pick another sprint, change the cap, or change the visible columns. Your choices stay with this tab and are not shared with the team.",[44,528,529],{},"Picking a card, tab, sprint, cap, or column selection while locked also detaches you.",[44,531,532,533,535],{},"Check ",[15,534,519],{}," again to discard your local choices and follow the moderator. The sprint and board return to the moderator's shared choice.",[44,537,538],{},"The lock is remembered in this browser tab while you stay on the tab.",[36,540,542],{"id":541},"stage-and-apply-status-moves","Stage and apply status moves",[11,544,545,546,548,549,551,552,554],{},"Status moves, flags, and assignee changes are stored in the standup session and are not written to Jira until you apply them. Selecting, undoing a move, moving by status, flagging, changing an assignee, and discarding changes update the board immediately. A staged status move, a staged flag, a staged assignee, or a moved place puts the undo button on the card, and the same button appears on its row in the ",[15,547,24],{}," tab and the ",[15,550,28],{}," tab. The button removes the staged change right away, without changing Jira, and the card returns to its lane. You see it only when you may discard that change. Their controls stay available while the request runs. If a request fails, the change rolls back and an error explains it. The board, sprint, filter, and estimate perspective selectors and ",[15,553,164],{}," still wait for the server.",[41,556,557,567,573,599],{},[44,558,559,560,562,563,566],{},"Select the checkbox on one or more cards, then choose an entry from the bottom ",[15,561,289],{}," dropdown. The menu lists only the Jira statuses every selected work item can reach under ",[15,564,565],{},"By status",". A moderator can check every card. A voter can check only the cards assigned to them, so a bulk move never targets another person's work item.",[44,568,569,570,572],{},"Each card has the same subtle ",[15,571,289],{}," dropdown. The placeholder is only a hint and resets after each action.",[44,574,575,576,579,580,583,584,587,588,590,591,594,595,598],{},"The menu has two groups. ",[15,577,578],{},"By rank"," holds ",[15,581,582],{},"Up"," and ",[15,585,586],{},"Down",", which move the work item one place up or down inside its own column. ",[15,589,565],{}," holds the Jira statuses the card can reach with a direct workflow transition, for example ",[15,592,593],{},"To Do"," or ",[15,596,597],{},"Done",". Statuses that are not mapped to another board column are not listed.",[44,600,601,602,604,605,607,608,583,610,612],{},"A work item that is first in its column has ",[15,603,582],{}," disabled, and a work item that is last in its column has ",[15,606,586],{}," disabled. For a bulk selection, ",[15,609,582],{},[15,611,586],{}," are disabled when no checked work item can move that way.",[11,614,615,616,618,619,621,622,624,625,627],{},"After a card has a staged status move, its ",[15,617,289],{}," menu disables every ",[15,620,565],{}," choice until the move is undone or applied, and the ",[15,623,578],{}," choices stay available. The bulk ",[15,626,289],{}," menu does the same while any selected card has a staged move. Apply recalculates the choices for each moved work item from its new Jira status.",[41,629,630,650,656,659,668,671,688,693],{},[44,631,632,633,635,636,639,640,642,643,646,647,649],{},"The app reads the status choices of a work item when you open its ",[15,634,289],{}," menu, so the first open can take a moment and the menu shows ",[15,637,638],{},"Loading statuses"," under ",[15,641,565],{}," until the choices arrive. It keeps the choices for as long as the board is shown, so the next open of the same menu is instant. Voting, starting or forwarding the countdown, selecting a card, moving cards around the board, and discarding changes do not read Jira again. ",[15,644,645],{},"Refresh"," forgets the choices together with the rest of the board, and the next time you open a menu it reads them again. The bulk ",[15,648,289],{}," menu reads the choices for every checked work item that it has not read yet.",[44,651,652,653,655],{},"A staged item moves to the target column and shows an error colored undo button right of its checkbox and moderator badge. The undo button removes the staged status move right away without changing Jira. Use ",[15,654,182],{}," to clear every staged move, and that action asks you to confirm.",[44,657,658],{},"A moderator can stage moves for any work item. A voter can check and move only the work items assigned to them.",[44,660,661,662,664,665,667],{},"The bottom bar shows the pending count. ",[15,663,164],{}," writes the staged status moves to Jira. The standup also keeps the order of each lane, so a card that changed lane is placed after the cards already in its new lane. Apply writes the new order of every lane whose order changed into the selected sprint, so the sprint and the board show the standup order. On a board without a sprint, the order is written to the board order instead. In a filter standup, no Jira rank is written because there is no board; the order stays in the standup. Apply writes only the cards whose place in a lane changed, so the other cards stay where they are. A lane that holds only one card is ranked next to the neighbouring lane, so a card moved into an otherwise empty lane still leaves the order of the lane it came from. Only the lanes whose order changed are written, so a status-only ",[15,666,164],{}," leaves the sprint order alone.",[44,669,670],{},"A moderator applies every staged move in the selected sprint, board, or filter; a voter applies only the moves for their own work items.",[44,672,673,675,676,678,679,681,682,684,685,687],{},[15,674,164],{}," is enabled only while the standup has a staged move or an order change to write. A passed check counts as a change only for ",[15,677,182],{},", because the check is not written to Jira, so passed checks alone never enable ",[15,680,164],{},". When ",[15,683,164],{}," runs, it writes the staged changes and clears every passed check. A work item that someone adds to the sprint or moves to another status in Jira appears in its lane after the board reloads, but it does not enable ",[15,686,164],{}," by itself.",[44,689,690,692],{},[15,691,182],{}," asks you to confirm, then removes every staged move you can discard, every staged work item a moderator added from a filter, clears every passed check, and returns the lanes to the order the sprint has in Jira now, including a reorder someone made in the Jira backlog. Cancel the confirmation to keep every staged change.",[44,694,695,696,699,700,702,703,706,707,709,710,712],{},"A moderator can delete the planning session with the danger-colored ",[15,697,698],{},"Delete"," button above the session tabs, beside ",[15,701,49],{},". A moderator can also archive the standup with the ",[15,704,705],{},"Archive"," button before ",[15,708,164],{},", and pressing ",[15,711,164],{}," does not archive anything by itself. Deleting asks for confirmation and permanently removes the planning session and its standup, retrospective, and chat data.",[11,714,715],{},"A status move fails and stays staged when the work item changed status in Jira after it was staged. The board reloads after Apply. An order write failure leaves that lane pending and reports the affected work items so you can retry. The failed order is never written to another place, so the sprint order and the board order cannot disagree because of it.",[36,717,719],{"id":718},"archive-the-standup","Archive the standup",[11,721,722,723,725,726,728],{},"A moderator can archive the standup to Confluence. The ",[15,724,705],{}," button sits before ",[15,727,164],{}," and appears when a Confluence space is configured. Archiving never changes Jira, the standup, or the staged changes.",[11,730,731,732,735],{},"The dialog shows the planning window, the sprint, board, or filter name, the space name, every assignee with presence and total presentation time, and every work item with its status, presentation time, and changes. A person the moderator added with the participant picker is listed too, with zero work items until something is assigned to them. A staged change is marked ",[15,733,734],{},"Pending",". Presentation time is the countdown time the work item spent on screen and counts toward its assignee.",[11,737,738,739,741,742,745,746,748,749,142],{},"Confirm with ",[15,740,705],{}," to create or update the page. The page is written under ",[15,743,744],{},"Plannings"," in a child page named after the space with a ",[15,747,17],{}," suffix, and its title carries the word ",[15,750,17],{},[36,752,754],{"id":753},"reload-and-live-updates","Reload and live updates",[11,756,757,760,761,763,764,766,767,227,769,230,771,773],{},[15,758,759],{},"Reload sprints and work items"," in the bottom action bar, after the ",[15,762,289],{}," dropdown, reloads the selected sprint or board, its Jira statuses, the estimates shown on the cards, and the Jira flags, and it forgets the ",[15,765,289],{}," choices so the next open reads them again. It does not change the standup order, and it does not move a work item to the place its Jira rank gives it. The rest of the bar follows it on the left: a gap, then ",[15,768,182],{},[15,770,705],{},[15,772,164],{}," for a moderator. The countdown sits at the right of the bar. Stages, undos, flags, and applies from other participants arrive right away. Staged moves, flags, and lane order changes are kept per planning session and per board and sprint, or per filter, and are removed when the planning session is deleted.",[11,775,776,777,779,780,782],{},"A moderator selects ",[15,778,133],{}," above the session tabs, beside ",[15,781,49],{},", to open the Edit planning session dialog. You can change the title, description, and schedule of the planning session there. The new values show on the planning tab and the progress bar right away. If the save fails, the previous values come back and a message tells you that the planning session could not be saved.",[11,784,785,786,583,788,790],{},"Accepting an estimate in a perspective tab updates it right away for everyone: the estimate badge on the card and the estimate in the ",[15,787,24],{},[15,789,28],{}," tabs change without a reload. The other work items on the board stay as they are.",[36,792,794],{"id":793},"the-standup-countdown","The standup countdown",[11,796,797],{},"A countdown at the right of the action bar follows the work item the moderator is discussing. A moderator sees the duration choice, the play or pause button, and the forward button. A voter who is assigned to the selected work item also sees the play or pause button and the forward button for that item. Guests see only the clock, even when the selected work item is assigned to them, so everyone can follow the same countdown.",[41,799,800,803,806,809,812,815,818,821,824],{},[44,801,802],{},"A voter assigned to the selected work item can pause, resume, and forward the countdown. Starting a stopped countdown and changing the duration stay with the moderator.",[44,804,805],{},"The clock keeps following the moderator even while you browse locally, so a detached voter or guest still sees the moderator's countdown.",[44,807,808],{},"The duration choice offers 15 seconds, 30 seconds, 1 minute, 2 minutes, and 3 minutes. It starts at 1 minute.",[44,810,811],{},"The countdown stops and resets when the moderator selects another work item, and it starts again right away for the new card. Clearing the selection stops the countdown.",[44,813,814],{},"Changing the duration stops the countdown and shows the new duration. The moderator starts it again with the play button.",[44,816,817],{},"The forward button ends the current countdown and moves the shared selection to the next work item in the column. When the current card is the last one in its column, it selects the first work item in the previous column. On the last card of the first column the selection stays and the countdown ends. A new selection starts a fresh countdown automatically.",[44,819,820],{},"In the last 10 seconds the selected card alternates between its normal background and the same highlight background used for the selected work item once per second. It never switches to a gray warning background. In the last 5 seconds it alternates twice per second. The card returns to its selected highlight when the countdown ends.",[44,822,823],{},"When the countdown reaches zero, everyone hears the same end sound as the retrospective countdown, subject to their sound setting. Pressing the forward button while the countdown still has time left plays the same end sound for everyone right away, whether the countdown is running or paused. Reaching zero alone does not pass the work item. The moderator passes it by pressing the forward button, or by selecting another work item or clearing the selection after the countdown ran out. The passed work item then shows the green check on its card and in both tables.",[44,825,826],{},"The passed checks are shared, so every participant sees the same green checks without a reload. They belong to the planning session and the selected board, sprint, or filter.",[36,828,830],{"id":829},"planning-session-progress","Planning session progress",[11,832,833,834,837],{},"The planning session progress bar sits at the bottom of the standup, below the action bar and to the left of the side panel. It shows how much of the planning session has elapsed, the time until it starts or the time remaining, and a ",[15,835,836],{},"Completed"," state once the end date has passed.",[11,839,840],{},"Standup data is kept for 12 hours after the last change. Each planning session keeps one record for its shared selection and one set of records for each board and sprint, or for each filter. Older standup data is removed automatically.",{"title":842,"searchDepth":843,"depth":843,"links":844},"",2,[845,846,847,848,849,850,851,852,853,854,855,856,857,858,859],{"id":38,"depth":843,"text":39},{"id":62,"depth":843,"text":63},{"id":122,"depth":843,"text":123},{"id":189,"depth":843,"text":190},{"id":206,"depth":843,"text":207},{"id":282,"depth":843,"text":283},{"id":302,"depth":843,"text":303},{"id":318,"depth":843,"text":319},{"id":388,"depth":843,"text":389},{"id":493,"depth":843,"text":494},{"id":541,"depth":843,"text":542},{"id":718,"depth":843,"text":719},{"id":753,"depth":843,"text":754},{"id":793,"depth":843,"text":794},{"id":829,"depth":843,"text":830},"2026-11-21","2026-11-13","Run a daily standup in Jira: review the sprint board, flag blockers, move statuses and keep a shared speaking order.","md","Sprint standups","\u002Fog\u002Fguide-sprint-standups.jpg",[867,868,869],"daily standup","sprint standup","jira standup","en",{},true,15,"\u002Fgetting-started\u002Fsprint-standups","guide",{"title":6,"description":862},{"loc":874,"lastmod":860},"sprint-standups","guide\u002Fen\u002Fsprint-standups","guide\u002Fsprint-standups","KhlYqMMmhDBToVDozBl0yOiJXza38DOzQDytXMAhSJs",{"id":883,"title":884,"body":885,"dateModified":860,"datePublished":861,"description":1478,"extension":863,"heading":1479,"image":1480,"imageAlt":1479,"keywords":1481,"locale":870,"meta":1485,"navigation":872,"order":1486,"path":1487,"section":875,"seo":1488,"sitemap":1489,"slug":1490,"stem":1491,"translationKey":1492,"__hash__":1493},"guide\u002Fguide\u002Fen\u002Fsprint-retrospectives.md","Sprint retrospectives | Scrumpy Planning Poker",{"type":8,"value":886,"toc":1462},[887,892,897,899,924,928,951,955,958,1018,1021,1027,1031,1042,1045,1049,1063,1068,1072,1075,1085,1088,1119,1122,1125,1137,1141,1149,1161,1164,1173,1176,1182,1186,1196,1221,1231,1241,1244,1257,1260,1264,1267,1296,1299,1303,1312,1332,1335,1338,1341,1344,1348,1357,1366,1370,1373,1382,1393,1410,1413,1415,1426,1446,1450,1453,1456,1459],[11,888,13,889,891],{},[15,890,511],{}," tab runs a retrospective for a sprint, for a board without sprints, or for the space when it has no board, inside a planning session. You and the other participants add notes to three columns, like the notes you agree with, group related notes, and turn notes into action items. The notes stay face down during Feedback, which is the first stage, and are revealed in the Vote stage, except your own notes, which only you can see.",[11,893,894],{},[15,895,896],{},"The retrospective is virtual: notes, groups, stages, and the timer stay in Scrumpy. Jira changes only when you select Apply, which creates or updates the Jira work items for your action items.",[36,898,39],{"id":38},[41,900,901,904,918,921],{},[44,902,903],{},"The space does not need a board. A Scrum board with sprints, a Kanban board, or a Scrum board without sprints works too. With no board at all, the retrospective saves its notes, timer, action items, and type for the planning session itself.",[44,905,906,907,909,910,909,912,914,915,917],{},"A planning session must exist. Create one from the ",[15,908,503],{}," tab, the ",[15,911,506],{},[15,913,17],{}," tab, or the ",[15,916,511],{}," tab.",[44,919,920],{},"Each sprint of a board, each board without sprints, and a planning session without a board has its own retrospective: its own notes, timer, action items, stage, and type. A change in one never reaches another.",[44,922,923],{},"Moderators choose the shared board, retrospective type, and sprint when the board has one. Locked participants follow that selection.",[36,925,927],{"id":926},"choose-the-board-and-sprint","Choose the board and sprint",[65,929,930,934,937,943,948],{},[44,931,69,932,917],{},[15,933,511],{},[44,935,936],{},"Pick a planning session from the tabs above the retrospective board. When the session you last opened is no longer available, the first planning session opens instead.",[44,938,939,940,942],{},"Pick a ",[15,941,81],{}," in the top left corner.",[44,944,939,945,947],{},[15,946,85],{}," next to the board. The list shows the six most recently started sprints of that board. A sprint that has not started yet is not listed. If the board has no started sprint, the sprint selector is hidden and the retrospective works for the board. A voter or guest can pick another sprint locally; that detaches the viewer from the moderator. Every sprint opens its own retrospective.",[44,949,950],{},"The sprint name appears in the center, with its goal underneath. Use the link icon next to the goal to open the sprint in the Jira backlog in a new browser tab. A board without sprints hides the sprint name, the goal, and the link. A space without a board shows an empty disabled board selector and hides the sprint selector, and the retrospective works for the planning session.",[36,952,954],{"id":953},"choose-the-retrospective-type","Choose the retrospective type",[11,956,957],{},"Use the dropdown in the top right corner. The three columns change with the type:",[959,960,961,974],"table",{},[962,963,964],"thead",{},[965,966,967,971],"tr",{},[968,969,970],"th",{},"Type",[968,972,973],{},"Columns",[975,976,977,986,994,1002,1010],"tbody",{},[965,978,979,983],{},[980,981,982],"td",{},"The good \u002F The bad \u002F The ugly",[980,984,985],{},"The good, The bad, The ugly",[965,987,988,991],{},[980,989,990],{},"Start \u002F Stop \u002F Continue",[980,992,993],{},"Start, Stop, Continue",[965,995,996,999],{},[980,997,998],{},"Mad \u002F Glad \u002F Sad",[980,1000,1001],{},"Mad, Glad, Sad",[965,1003,1004,1007],{},[980,1005,1006],{},"Sunny skies \u002F Hot air \u002F Storm clouds",[980,1008,1009],{},"Sunny skies, Hot air, Storm clouds",[965,1011,1012,1015],{},[980,1013,1014],{},"What worked well? \u002F What didn't go well? \u002F What should we try next?",[980,1016,1017],{},"The three questions",[11,1019,1020],{},"Switching the type only changes the column names. The notes stay in their columns. The new column names appear right away, and you can keep adding notes and using the actions while the change saves. If the change cannot be saved, the previous type returns.",[11,1022,1023,1024,1026],{},"The type belongs to the retrospective you are looking at. Each sprint keeps its own type, and so does a board without sprints and a planning session without a board. Switching the sprint or the board shows that retrospective's own type, or the default ",[15,1025,982],{}," when it never had one. Changing the type on one sprint never changes another sprint's columns.",[36,1028,1030],{"id":1029},"add-a-note","Add a note",[65,1032,1033,1036,1039],{},[44,1034,1035],{},"Find the column you want. Its name sits above the retrospective board, centered over the lane.",[44,1037,1038],{},"Select the add button with the plus icon under the column name.",[44,1040,1041],{},"An empty note appears in the column and its editor is ready. Type your note.",[11,1043,1044],{},"Your own notes are always visible to you, even during Feedback. Notes from other participants stay hidden during Feedback and are revealed in the Vote stage. The note sits in the retrospective board as a sticky card with the same layout as a chat message. Your own notes sit on the right of the column, and notes from other participants sit on the left. Each card shows the author and the author's role (Moderator or Voter), the time, the note text, and the actions you can use on that note. The role uses the same label as a chat message. A single note has no separate accent line inside the card; the card's rounded border is the only accent border, in blue for your notes and purple for notes from other participants. The cards use the same 8px vertical spacing as the standup work item cards. Notes in a group have a 20px gap before and after the group. Guests can read the notes but cannot add or edit them.",[36,1046,1048],{"id":1047},"read-edit-and-like-a-note","Read, edit, and like a note",[41,1050,1051,1054,1057,1060],{},[44,1052,1053],{},"If you wrote the note, the card itself contains an editor. Change the text directly on the card and it is saved shortly after you stop typing. Only the author or a moderator can edit a note.",[44,1055,1056],{},"Select the like button on a card to like a note. Select it again to remove your like. The button shows how many likes the note has. You can like notes in the Vote stage. In the Actions stage the like button and its count stay on the card but are read-only, so you can still see the totals. The like button, and the delete button on notes you wrote, sit at the right edge of the action row for every participant, close together.",[44,1058,1059],{},"A group shows one like button with the sum of its notes' likes. A new like is added to the first note in the group. If you already liked a note in the group, selecting the group like removes your like from the first note you liked.",[44,1061,1062],{},"The delete button on a card asks for confirmation, then removes that note, only if you wrote it. A group has one delete action that removes every note in the group, and only a participant who wrote every note in the group can use it. A note that belongs to an action item keeps its text and editor, but its like is disabled until the action item is removed. Grouping is still available; grouping linked notes adds the whole group to their action items.",[199,1064],{"alt":1065,"caption":1066,"stem":1067},"The retrospective board with notes in the three columns, the stage selector, and the shared countdown","The retrospective board","guide-retrospective",[36,1069,1071],{"id":1070},"select-several-notes","Select several notes",[11,1073,1074],{},"Each card has a checkbox at the start of its action row. A moderator sees one on every card. A voter sees one on every card during the Vote stage, so they can like several notes at once, including notes written by other people, and only on their own notes in the other stages. A group has one checkbox in its action bar, and it selects every note in the group; it appears to a moderator, to a voter during the Vote stage, and to a participant who wrote every note in the group. Checking a note ticks its checkbox. The moderator's checked notes are filled with the light accent colour that matches their border, and every participant sees the same fill, even when they browse the retrospective locally. A voter's own checkbox only ticks, because the fill always shows the moderator's shared selection. A group is filled as one card when any of its notes is checked. The fill is stored with the retrospective, survives a reload, and is cleared when the sprint changes.",[11,1076,1077,1078,1080,1081,1084],{},"A moderator also has an ",[15,1079,133],{}," button at the start of the action bar, before ",[15,1082,1083],{},"Group notes",". It opens the Edit planning session dialog, where you can change the title, description, and schedule of the planning session. The new values show on the planning tab and the progress bar right away. If the save fails, the previous values come back and a message tells you that the planning session could not be saved.",[11,1086,1087],{},"Select the checkboxes of the notes you want, then use the action bar below the notes and action items:",[41,1089,1090,1095,1101,1107,1113],{},[44,1091,1092,1094],{},[15,1093,1083],{}," is available to moderators. The selected notes in each column join one group. The button is enabled from the Vote stage on, when at least two selected notes are in the same column and at least one of them is not already in a group. If a selected note already belongs to an action item, that action item takes on the whole group's notes, authors, and likes.",[44,1096,1097,1100],{},[15,1098,1099],{},"Ungroup notes"," is available to moderators. The selected notes in each column leave their group. The button is enabled from the Vote stage on, when at least one selected note belongs to a group.",[44,1102,1103,1106],{},[15,1104,1105],{},"Like notes"," adds your like to every selected note. It is enabled in the Vote stage, including when the selection contains another participant's notes.",[44,1108,1109,1112],{},[15,1110,1111],{},"Create action items"," uses the tasks icon and is available to moderators. It creates one action item for each selected note and one for each selected group. Notes that already belong to an action item, and groups containing one, are skipped. The action is enabled when at least one selected note or group is not already linked.",[44,1114,1115,1118],{},[15,1116,1117],{},"Delete notes"," removes the selected notes you wrote. The action is disabled when the selection includes a note written by someone else, so a mixed selection is for liking only. The checked action items are removed with the separate action item delete action. A confirmation dialog appears before anything is deleted.",[11,1120,1121],{},"Grouped notes stay together and are separated from the rest of the column by a 20px gap. The whole group shares one comment card, one pair of left and right borders, one author header, and one action bar. The author header shows the first note's author and time. Each grouped note has its own editor inside the card; your own notes are editable and the other notes are read-only. Each note except the last is separated from the next by a 1px dashed bottom border in the group card's accent colour. The last note has no bottom border, so the group keeps one clean end, and a single note has no separator. The group action bar has one selection checkbox that selects every note in the group, one like button with the summed like count, and one delete action. The delete action appears only when you wrote every note in the group, and it removes every note in the group after confirmation. The group like and delete buttons sit at the right edge of the group action row, close together.",[11,1123,1124],{},"Deleting a note is disabled while the note belongs to an action item. Remove the action item first if you need to delete its source notes. Removing the action item leaves the source notes in the retrospective.",[11,1126,1127,1128,1130,1131,1133,1134,1136],{},"A moderator also has a ",[15,1129,182],{}," text button immediately after the delete actions, the same action the Standup offers. It asks for confirmation and deletes every note, action item, and the timer of the retrospective on screen, returning it to its initial state with its chosen type. Other sprints, other boards, and the planning session's other retrospectives keep their notes, action items, and timer. The ",[15,1132,705],{}," action sits after Discard changes with spacing before it, and ",[15,1135,164],{}," follows it and creates or updates Jira work items for every action item in the selected sprint that has a work item type other than None. Only a moderator sees Discard changes and Apply. Discard changes is disabled when the retrospective on screen has no notes, no action items, and an untouched timer, and it stays disabled while the discard is being saved. Apply is available when at least one action item has a work item type other than None and is new or has changed since the last Apply, even when no rows are checked. After a successful Apply it is disabled until an action item changes.",[36,1138,1140],{"id":1139},"see-your-notes-in-the-status-and-assignee-tables","See your notes in the Status and Assignee tables",[11,1142,1143,1144,583,1146,1148],{},"From the Vote stage on, the right side panel has two more tabs, ",[15,1145,24],{},[15,1147,28],{},". Both tables list the notes of the retrospective. A group is one row, with the first line of each note shown one under the other and separated by a dashed line. A row shows a checkbox, the author, and the first line of the note, cut with an ellipsis when it is longer.",[41,1150,1151,1156],{},[44,1152,1153,1155],{},[15,1154,24],{}," groups the notes by the three columns of the retrospective type.",[44,1157,1158,1160],{},[15,1159,28],{}," groups the notes by the person who wrote them. A group sits under the author of its first note.",[11,1162,1163],{},"A checkbox in a table is the same checkbox as on the note. Selecting a row selects the note on the board, and selecting a note on the board selects its row. A group row selects every note in the group. A voter can select their own notes outside the Vote stage and any note in the Vote stage.",[11,1165,1166,1167,1169,1170,1172],{},"Drag a row into another section to move it. In ",[15,1168,24],{},", a section is a column, so the note moves to that column; inside its own section it changes only the order. In ",[15,1171,28],{},", a section is one author, so this makes that person the note's author. Grouped notes move together. Only a moderator or the note's author can drag a row; another row returns to its place with a message. A column can hold at most 200 notes, so a move into a full column is refused.",[11,1174,1175],{},"The tables appear in the Vote and Actions stages. During Feedback they are hidden, because another participant's note is still face down.",[11,1177,1178,1179,1181],{},"Changing a note's author also changes the role shown on the note and the Authors column of every action item built from it. The move saves right away, so there is nothing to Apply. When you are ready, ",[15,1180,1111],{}," in the action bar is the blue primary action.",[36,1183,1185],{"id":1184},"turn-notes-into-action-items","Turn notes into action items",[11,1187,1188,1189,1191,1192,1195],{},"A moderator selects one or more notes or groups, then selects ",[15,1190,1111],{}," in the note action bar. The button is enabled when at least one selected note or group has no action item yet. Only those unlinked notes and groups create rows; the ones that already have an action item are skipped. The action items appear in a table above the action bar. A centered ",[15,1193,1194],{},"Action items"," heading sits above the table, with a short line below it that reads \"Follow-up action items based on the team retrospective notes.\" The heading is smaller than the sprint or board name and is hidden when the table has no rows. The table stretches across the left content, and the selected action item's details are in the Details tab of the right side panel when the action item has no voting tab. While no action item is selected, the side panel has no Details tab. A moderator can drag a row to change the order of the action items. Everyone sees the new order right away, and the Confluence archive writes the action items in that order.",[41,1197,1198,1201,1204,1211,1218],{},[44,1199,1200],{},"One selected single note creates one row.",[44,1202,1203],{},"One selected group creates one row. The row uses the group's first note as its summary and lists every author in the group.",[44,1205,1206,1207,1210],{},"The Type column header is the work-item icon, and the next column is headed ",[15,1208,1209],{},"Work item",". Its cells show the same issue key link as the planning session tables, with the action item summary on hover. For a moderator, the matching work item type icon comes before the compact dropdown, and the header icon and the type icon are left aligned. The dropdown starts with None, which is not the default. When None is selected, the icon becomes an empty space of the same width so the cell does not resize. For a voter or guest, the Type column shows only the work item type icon and uses the minimum width, and their first column is a new empty column that marks the action item the moderator selected. The remaining columns show the summary, the authors, the total likes of the source notes, and the estimate. The Summary column cells show the summary without a Summary label.",[44,1212,1213,1214,1217],{},"The last column is headed ",[15,1215,1216],{},"Estimate",". It shows the linked work item's current estimate in the selected board's unit: story points for a numeric board and a work-day duration for a time board. The cell stays empty for an action item without a Jira link or without an estimate. The column is hidden when the board has no estimation field.",[44,1219,1220],{},"For everyone else the type cell shows only the work item type icon, with an empty space of the same width when the type is None, and the header icon and the type icon are centered in their column. The Type column for a voter or guest uses the minimum width. A moderator changes the type in the dropdown; the icon updates immediately, and if the change cannot be saved, the previous type returns.",[11,1222,1223,1224,1226,1227,1230],{},"A moderator sees a checkbox column for selection and a radio column for choosing the shared row shown in the Details tab of the side panel. The radio column header uses the same presenter mode icon as the single selection column of the Refinement and grooming tab. Everyone else sees the same radio column, and their first column is an empty column of the minimum width that shows a warning ",[15,1225,238],{}," badge on the action item the moderator selected, with a tooltip that names it, like the Refinement and grooming table. The badge follows the moderator's current selection even while you browse the retrospective locally. While you are locked to the moderator, your radio follows the moderator's row. Select another row's radio to browse that action item yourself: the choice detaches you from the moderator, appears only in this browser tab, and leaves the moderator's shared row unchanged. Selecting another action item by the moderator does not replace your local row while you stay detached. Selecting an action item with its checkbox also selects the notes that were used to create it. Choosing another radio button replaces the summary and description in the Details tab with the newly selected action item. The like count in the table is shown in a purple lozenge with no icon. The ",[15,1228,1229],{},"Summary"," column in the table shows plain text. Edit the summary in the Details tab while no voting tab is shown; only a moderator can change it there.",[11,1232,1233,1234,1236,1237,1240],{},"The action item details show a ",[15,1235,1229],{}," label and a ",[15,1238,1239],{},"Description"," label above the two fields. Only a moderator can edit the summary, the description, and the work item type. The summary uses the same inline text field as a work item summary in the Details tab. The description uses the same editor as a work item description. Voters and guests see the action item details read-only. The type dropdown starts with None, then lists the work item types of the board's project, without subtasks. The first Jira work item type remains the default.",[11,1242,1243],{},"The action bar below the action item table controls both kinds of selection:",[41,1245,1246,1252],{},[44,1247,1248,1251],{},[15,1249,1250],{},"Delete action items"," uses the table-row-delete icon and removes only the checked action items after a confirmation dialog. It is available to moderators. The source notes stay in the retrospective when you remove an action item. A Jira work item that was already created stays in Jira.",[44,1253,1254,1256],{},[15,1255,164],{}," creates a work item for every action item in the selected sprint that has a work item type other than None and no Jira link, and updates the linked work item for every action item that has a type and a link. It is available to moderators. Action items with None are skipped entirely, so no Jira work item is created or updated for them. The checked rows do not limit it. It is a text button immediately after Archive, and it is available only when at least one action item has a work item type other than None and is new or has changed since the last Apply, so a second Apply without an edit stays disabled. New work items are added to the project backlog. If some rows fail, the retrospective shows a warning and the successful rows keep their links. A small hint below the action item table explains that Apply creates or updates Jira work items from the action items and that estimation becomes available once a Jira work item is created from an action item. The hint appears to moderators only, when at least one action item has a work item type other than None.",[11,1258,1259],{},"The action bar sits directly below the action item table, with the planning progress bar directly below it and a space.200 vertical gap between them. This is the same placement as the action toolbar in the capacity planning tab.",[36,1261,1263],{"id":1262},"the-timer","The timer",[11,1265,1266],{},"The countdown clock sits at the right of the action bar below the retrospective board. A moderator also sees the controls there, with the clock to the right of the fast-forward button. Everyone sees the clock.",[41,1268,1269,1272,1275,1278,1281,1284,1287,1290,1293],{},[44,1270,1271],{},"A moderator chooses 1, 3, 5, 10, or 15 minutes. Choosing a duration resets the countdown.",[44,1273,1274],{},"The first note you add in Feedback starts the countdown automatically with the selected duration. Anyone in the team can start it this way. The stage then locks until the countdown ends or a moderator fast-forwards it. If the countdown was already started or paused, adding a note does not restart or resume it.",[44,1276,1277],{},"The play button starts the timer, pauses it while it runs, and resumes it when paused. Only a moderator sees the duration selector, the play button, and the fast-forward button.",[44,1279,1280],{},"A moderator can use the fast-forward button to end the countdown and move to the next stage right away.",[44,1282,1283],{},"The remaining time is shown in a large rounded box. When the countdown ends, the same box shows that time is up.",[44,1285,1286],{},"The clock updates every second.",[44,1288,1289],{},"While the stage is Feedback, the cards written by other participants keep their layout but hide the note text and the like button. Your own note keeps its text and editor. Grouping and ungrouping are disabled in Feedback; creating action items is enabled only in the Actions stage. Delete stays available.",[44,1291,1292],{},"When the countdown reaches zero, the stage moves to Vote and the note text is revealed. The text appears for everyone at the same time, including the person who changes the stage. Your own notes stay visible all the time.",[44,1294,1295],{},"In the Vote and Actions stages the timer is just a timer. A moderator can start it again at any time to timebox the discussion without hiding the notes, except in the Actions stage where the timer controls are disabled.",[11,1297,1298],{},"The progress bar under the action bar shows how far the planning session is from its start and end dates. It ends to the left of the side panel.",[36,1300,1302],{"id":1301},"stages","Stages",[11,1304,13,1305,1308,1309,1311],{},[15,1306,1307],{},"Stage"," dropdown sits after the timer controls in the action bar. Its three stages are grouped under the ",[15,1310,1307],{}," label inside the menu:",[41,1313,1314,1320,1326],{},[44,1315,1316,1319],{},[15,1317,1318],{},"Feedback"," is the default. You can add notes. Grouping, ungrouping, likes, and creating action items are disabled.",[44,1321,1322,1325],{},[15,1323,1324],{},"Vote"," disables new notes. You can like notes. Creating action items is disabled.",[44,1327,1328,1331],{},[15,1329,1330],{},"Actions"," disables new notes and likes. Like buttons and counts stay visible but cannot be selected. A moderator can create action items. The countdown controls are disabled.",[11,1333,1334],{},"A small line below the notes explains the current stage. Everyone sees it. In Feedback it invites the team to add sticky notes with their feedback. In Vote it explains that this is the time to collect which notes are worth creating action items from. In Actions it explains that notes can be grouped by common meaning and action items created from the most-voted notes.",[11,1336,1337],{},"A moderator switches the stage. Everyone else sees the current stage in the dropdown but cannot change it. The stage is remembered with the retrospective and survives a reload.",[11,1339,1340],{},"While a countdown has started and has not ended, the stage is locked. When the countdown ends or is fast-forwarded, the next stage is selected automatically. The notes are revealed when you leave Feedback, and they are hidden again if you go back to Feedback.",[11,1342,1343],{},"An action item shows the total likes of all its source notes. When the action item comes from a group, this includes every note in the group. Grouping notes later also adds the whole group's notes, authors, and likes to every action item already linked to a note in the group. Ungrouping keeps the action item linked to the notes and keeps the total.",[36,1345,1347],{"id":1346},"archive-and-complete","Archive and complete",[11,1349,1350,1351,1353,1354,1356],{},"A moderator can archive the retrospective to Confluence with the ",[15,1352,705],{}," button before Apply in the action bar. It is available in the ",[15,1355,1330],{}," stage, because the notes stay hidden from everyone until the team reveals them. The archive writes the notes, the participants, and the action items of the selected sprint to the page, and it creates or updates the page. It does not close the planning session. See Archiving to Confluence for the page contents.",[11,1358,1359,1360,1362,1363,1365],{},"The danger-colored ",[15,1361,698],{}," button, above the session tabs beside ",[15,1364,49],{},", closes the planning session. It asks for confirmation, then permanently removes the planning session and its notes, action items, standup, and chat.",[36,1367,1369],{"id":1368},"details-and-chat","Details and chat",[11,1371,1372],{},"The right side panel has a Chat tab on the right. When an action item is selected and it has no voting tab, a Details tab appears on the left. The Details tab shows the selected action item. While no action item is selected, the panel shows only the Chat tab. The Chat tab holds the full session conversation: every message sent from the planning session, plus messages sent from outside the session for the work items the retrospective shows, including the work items linked from action items, ordered by time. A work item message shows its work item key as a small link at the start of its action row; select it to open the work item in Jira. When you select an action item that is linked to a Jira work item, the messages you send go to that work item chat, and the message shows the work item key as a small link. With no action item selected, with an action item that has no Jira link, or when you cannot open the linked work item, the messages go to the planning-session chat. The planning conversation belongs to the planning session, so it is the same chat in every tab that opens that planning session.",[11,1374,1375,1376,1378,1379,1381],{},"When the selected action item is linked to a Jira work item, the side panel also shows a voting tab for every perspective whose estimation uses the board in the board selector. The voting tabs appear before ",[15,1377,223],{},". Each tab opens the voting panel for the linked Jira work item. A voting tab already shows the linked work item details, so the Details tab is hidden while at least one voting tab is shown. An action item without a Jira link shows no voting tabs. Changing the board selector changes the voting tabs to that board's matching perspectives. When you accept an estimate in a voting tab, the linked action item's ",[15,1380,1216],{}," cell shows the new value right away, and every other participant sees it as soon as the accepted estimate reaches them.",[11,1383,1384,1385,239,1387,1389,1390,1392],{},"The side panel is 400px wide and starts at the top of the planning session content, level with the board and sprint selectors. The Details tab is selected by default when it is shown. When a voting tab is shown, the panel opens on the first voting tab. The moderator's chosen tab is part of the shared retrospective data, so locked participants follow it. A yellow ",[15,1386,238],{},[15,1388,219],{},", a voting tab, or ",[15,1391,223],{},". Every non-moderator sees it, whether they follow the moderator or browse on their own. The retrospective type selector sits at the end of the board and sprint row, immediately left of the side panel.",[41,1394,1395,1398,1401,1404,1407],{},[44,1396,1397],{},"Moderators and voters can send public or private messages. Guests can send public messages and cannot see private messages.",[44,1399,1400],{},"Work item messages appear next to planning messages by their sent time. They stay available for 72 hours and are hidden when you cannot open that work item in Jira.",[44,1402,1403],{},"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.",[44,1405,1406],{},"Messages can be edited or deleted by their author, and can be reacted to with thumbs up or thumbs down.",[44,1408,1409],{},"The side panel stretches to the height of the retrospective content. The note columns, action item table, and progress bar stay to its left.",[11,1411,1412],{},"The bell at the right of the Details and Chat tabs, after your role badge, controls sound notifications for the timer and the chat. Select it once to turn sound on. The bell starts muted.",[36,1414,494],{"id":493},[11,1416,1417,1418,227,1420,227,1422,230,1424,512],{},"Voters and guests start locked to the moderator. While locked, you follow the moderator's action item, sprint, retrospective type, and side panel tab. The checked-note highlight is always shared, even while you browse locally. The moderator's changes arrive right away. You also follow the moderator's space page tab, so the page moves between ",[15,1419,503],{},[15,1421,506],{},[15,1423,17],{},[15,1425,511],{},[41,1427,1428,1432,1437,1440,1444],{},[44,1429,1430,520],{},[15,1431,519],{},[44,1433,523,1434,1436],{},[15,1435,519],{}," to browse on your own. You can pick another tab, pick another sprint, or pick another action item. Your action item choice applies only to you and is not shared with the team. Your choices stay with this tab. The shared board and retrospective type stay moderator controlled.",[44,1438,1439],{},"Picking another tab, sprint, or action item while locked also detaches you.",[44,1441,532,1442,535],{},[15,1443,519],{},[44,1445,538],{},[36,1447,1449],{"id":1448},"changes-appear-for-everyone","Changes appear for everyone",[11,1451,1452],{},"Every note, like, group, action item, and timer change is saved for the planning session and appears for the other participants right away. If the connection drops, the tab reloads the current state when the connection returns.",[11,1454,1455],{},"Most changes appear in your own view immediately, before the server answers. This includes the timer duration and controls, the Stage, adding and deleting notes, likes, groups, action items, and Discard changes. Confirmation dialogs close as soon as you confirm. If a change cannot be saved, the previous state is restored and a warning appears. The controls stay available while the change is being saved.",[11,1457,1458],{},"A like you give or take back stays as you left it. A slower copy of your earlier like never adds it back, and other people's likes still appear as they give them. If a like cannot be saved, only the likes from that click go back to how they were, and your other notes stay as you left them.",[11,1460,1461],{},"Retrospective data is kept for 72 hours after the last change. Older retrospective data is removed automatically.",{"title":842,"searchDepth":843,"depth":843,"links":1463},[1464,1465,1466,1467,1468,1469,1470,1471,1472,1473,1474,1475,1476,1477],{"id":38,"depth":843,"text":39},{"id":926,"depth":843,"text":927},{"id":953,"depth":843,"text":954},{"id":1029,"depth":843,"text":1030},{"id":1047,"depth":843,"text":1048},{"id":1070,"depth":843,"text":1071},{"id":1139,"depth":843,"text":1140},{"id":1184,"depth":843,"text":1185},{"id":1262,"depth":843,"text":1263},{"id":1301,"depth":843,"text":1302},{"id":1346,"depth":843,"text":1347},{"id":1368,"depth":843,"text":1369},{"id":493,"depth":843,"text":494},{"id":1448,"depth":843,"text":1449},"Run a sprint retrospective in Jira: collect notes, group them, vote and turn the result into action items.","Sprint retrospectives","\u002Fog\u002Fguide-sprint-retrospectives.jpg",[1482,1483,1484],"sprint retrospective","agile retrospective","jira retrospective",{},14,"\u002Fgetting-started\u002Fsprint-retrospectives",{"title":884,"description":1478},{"loc":1487,"lastmod":860},"sprint-retrospectives","guide\u002Fen\u002Fsprint-retrospectives","guide\u002Fsprint-retrospectives","ybCpunharAAtUbt5ZQmwP9arm2Kx-gjKWlDo-VcdhwU",null,{"id":1496,"title":1497,"body":1498,"dateModified":860,"datePublished":1771,"description":1772,"extension":863,"heading":1773,"image":1774,"imageAlt":1773,"keywords":1775,"locale":870,"meta":1777,"navigation":872,"order":1778,"path":1779,"section":1780,"seo":1781,"sitemap":1782,"slug":1783,"stem":1784,"translationKey":1785,"__hash__":1786},"tutorials\u002Ftutorials\u002Fen\u002Fleading-a-standup.md","Leading a standup | Tutorials | Scrumpy Planning Poker",{"type":8,"value":1499,"toc":1761},[1500,1506,1510,1524,1529,1532,1534,1537,1540,1546,1551,1555,1560,1564,1584,1590,1594,1599,1602,1607,1630,1635,1639,1648,1656,1661,1702,1706,1712,1724,1739,1744,1748],[11,1501,1502,1503,1505],{},"A standup is the easiest meeting to run in Scrumpy. Open the tab, pick the running sprint, and talk through the cards in the order the team sees them. Everything you change stays in the standup until you press ",[15,1504,164],{},", so you can rearrange the board while you talk without touching Jira.",[36,1507,1509],{"id":1508},"pick-the-planning-session-board-and-sprint","Pick the planning session, board, and sprint",[11,1511,69,1512,1514,1515,1517,1518,1520,1521,1523],{},[15,1513,17],{}," tab and pick a planning session from the tabs above the board. Pick the ",[15,1516,81],{}," first, then the ",[15,1519,85],{},". The sprint list only shows the sprints that are running right now, so the standup opens on the work the team is doing today. The sprint name and goal sit above the columns, and the link icon opens the sprint in Jira. When the space has no board, pick a saved ",[15,1522,95],{}," instead, and the standup shows the work items that filter returns, with one column per status.",[199,1525],{"alt":1526,"caption":1527,"stem":1528},"The board and sprint selectors above the standup","Choose the board and the running sprint","tutorial-standup-sprint",[11,1530,1531],{},"Only a moderator changes the shared board. A voter or guest who picks another sprint does so only for their own browser tab.",[36,1533,190],{"id":189},[11,1535,1536],{},"Every column of the board is a lane, in the board's own order. The cards follow the shared standup order, which starts as the order of the sprint in Jira. Each card shows the assignee, the priority, the key as a link, the estimate, and one or two lines of the summary. A card with an estimate shows it as a badge, so the team can see the size without opening Jira. A work item the team has passed shows a small green check right of its key.",[11,1538,1539],{},"In this example the To Do column holds the most work, one card has a red flag, and two cards were already moved while the team talked. The two moved cards carry an undo button next to their checkbox. Three cards carry the green passed check, and the two cards of the absent teammate are gray and dimmed.",[11,1541,1542,1543,1545],{},"Use ",[15,1544,106],{}," in the toolbar to cap how many cards a column loads and shows. Work items beyond the cap stay in Jira and are loaded when you raise the cap. A work item the standup already loaded keeps its place and staged changes while it is hidden.",[199,1547],{"alt":1548,"caption":1549,"stem":1550},"The standup board with cards in every column","The sprint as a standup board","tutorial-standup-board",[36,1552,1554],{"id":1553},"flag-a-work-item-that-needs-attention","Flag a work item that needs attention",[11,1556,1557,1558,142],{},"Select the flag at the right of a card to mark it for the team. A card that is already flagged in Jira opens with a red flag. Select it again to clear the flag. The flag shows for everyone right away, and it is written to the Jira Flagged field when you press ",[15,1559,164],{},[36,1561,1563],{"id":1562},"move-work-items-without-leaving-the-standup","Move work items without leaving the standup",[11,1565,103,1566,1568,1569,1571,1572,1574,1575,1577,1578,1580,1581,1583],{},[15,1567,289],{}," dropdown on a card to change its status or its place in the lane. ",[15,1570,565],{}," offers the statuses the card can reach in Jira, and ",[15,1573,578],{}," moves the card one place up or down. Select several cards with their checkboxes to move them together. A card with a staged status move keeps ",[15,1576,565],{}," disabled until you undo or apply that move, while ",[15,1579,578],{}," stays available. The statuses are read when you open the menu, so the first open can take a moment and shows ",[15,1582,638],{}," until they arrive.",[11,1585,1586,1587,1589],{},"The change is shared with the team immediately, but it is not written to Jira yet. The moved card shows an undo button next to its checkbox. Select it to remove that staged change right away, without a confirmation and without changing Jira. ",[15,1588,182],{}," is the button that asks you to confirm before it clears everything.",[36,1591,1593],{"id":1592},"follow-the-same-standup-in-the-status-table","Follow the same standup in the Status table",[11,1595,13,1596,1598],{},[15,1597,24],{}," tab at the left of the side panel shows the same standup in a second view. It is not another list: every work item of the sprint is there, in the same columns and the same order, with the same flags and the same staged moves. Move a work item in the table and its card moves on the board at the same time.",[11,1600,1601],{},"Each board column is a wide row with its name in the middle, and the work items of that column sit under it. A row shows the work type, the priority, the flag, the key, the green passed check, the undo button, and the estimate, so the whole sprint fits in a short list. That makes the table quick to scan, and sometimes it is simply easier to walk through the work items here than on the board.",[199,1603],{"alt":1604,"caption":1605,"stem":1606},"The Status table with the same work items and staged moves as the board","The same standup as a compact table","tutorial-standup-order",[41,1608,1609,1615,1618,1621,1627],{},[44,1610,1611,1612,1614],{},"Select the round button at the left of a row to make that work item the one under discussion, exactly like clicking its card. Everyone else sees a yellow ",[15,1613,238],{}," on that row.",[44,1616,1617],{},"Drag a row to change its place in its column, or drop it under another column to move it there when the workflow allows it.",[44,1619,1620],{},"Select the flag to stage a flag, and the undo button to remove a staged change. These are the same buttons and the same staged moves as on the board.",[44,1622,1623,1624,1626],{},"A green check in the narrow column after the key means the team has passed that work item: the moderator forwarded its countdown, or moved the selection on after the countdown ran out. The same check appears next to the key on the card and in the ",[15,1625,28],{}," table.",[44,1628,1629],{},"A moderator can move and flag every work item, a voter only the work items assigned to them, and a guest reads the table.",[11,1631,1632,1634],{},[15,1633,164],{}," writes the new order and the staged moves to Jira from here too.",[36,1636,1638],{"id":1637},"see-who-is-in-the-room","See who is in the room",[11,1640,13,1641,394,1643,1645,1646,401],{},[15,1642,28],{},[15,1644,24],{}," at the left of the side panel. It groups the same work items by the person doing them, so the standup can walk through the team person by person instead of column by column. ",[15,1647,400],{},[11,1649,1650,1651,1653,1654,1626],{},"Every assignee is a wide row with the person's name in the middle, and that person's work items sit under it, in the same board order. A row shows the same facts as the ",[15,1652,24],{}," table: the work type, the priority, the flag, the key, the green passed check, the undo button, and the estimate. The check and the undo button are the same ones you see on the board and in the ",[15,1655,24],{},[199,1657],{"alt":1658,"caption":1659,"stem":1660},"The Assignee table with the team grouped by person, one absent assignee, and the same passed checks","The same standup grouped by person","tutorial-standup-assignee",[41,1662,1663,1671,1678,1681,1686,1692,1697],{},[44,1664,1665,1666,1668,1669,142],{},"Drag a work item into another person's row to give it to them. The board avatar, the card color, and the ",[15,1667,24],{}," row show the new person right away, but Jira changes only when you press ",[15,1670,164],{},[44,1672,13,1673,1675,1676,410],{},[15,1674,106],{}," cap also applies here, so the table lists only the work items the board shows. A person whose work items all sit beyond the cap is not listed, in the table or in the ",[15,1677,409],{},[44,1679,1680],{},"A moderator can give any work item to another person. A voter can give only their own work items. Guests read the table.",[44,1682,13,1683,1685],{},[15,1684,409],{}," picker below the table lists everyone whose checkbox is checked. A moderator clears the checkbox at the left of an assignee row to remove that person from the picker and mark them absent. The row stays, with the checkbox unchecked and disabled, because the work items still belong to that person. Add the person back in the picker to check it again. Clearing a person who has no work items removes their row. The choice is shared with the team right away.",[44,1687,1688,1689,1691],{},"When a person is absent, their work items cannot be selected, from this table, from the ",[15,1690,24],{}," table, or by clicking the card. Their cards use a gray border with dimmed text and avatar, so the team can tell them apart, and they lose the countdown pause, resume, and forward buttons.",[44,1693,479,1694,1696],{},[15,1695,28],{}," tab open, the countdown forward button walks this table and skips every absent person, so the standup continues with the next teammate.",[44,1698,1699,1701],{},[15,1700,400],{}," is always present and has no checkbox.",[36,1703,1705],{"id":1704},"apply-the-changes-to-jira","Apply the changes to Jira",[11,1707,1708,1709,1711],{},"This is the step that makes the changes real. Press ",[15,1710,164],{}," in the action bar under the board. Scrumpy writes the new status of every moved work item, the new order of the sprint, the staged flags, and the new assignees to Jira, in one go.",[11,1713,1714,1715,1717,1718,1720,1721,1723],{},"A moderator can also archive the standup with ",[15,1716,705],{},", which sits before ",[15,1719,164],{}," and appears when a Confluence space is configured for archives. The dialog lists the planning window, the sprint, board, or filter, every assignee with presence and presentation time, and every work item with its status, presentation time, and changes. A staged change is marked ",[15,1722,734],{},". Archiving never changes Jira or the staged changes.",[11,1725,1726,1727,1729,1730,1732,1733,1735,1736,1738],{},"Without ",[15,1728,164],{},", nothing is saved to Jira. Closing the tab or picking another sprint leaves Jira exactly as it was. If you change your mind, press ",[15,1731,182],{}," and confirm the dialog instead. Discard removes every staged change and clears every passed check, and it does not touch Jira. ",[15,1734,164],{}," clears the passed checks too, because the walkthrough is over. ",[15,1737,759],{}," reads the sprint from Jira again.",[199,1740],{"alt":1741,"caption":1742,"stem":1743},"The action bar with the pending changes and the Apply button","Apply writes the standup to Jira","tutorial-standup-apply",[36,1745,1747],{"id":1746},"keep-everyone-in-step","Keep everyone in step",[11,1749,1750,1751,1753,1754,1757,1758,1760],{},"The moderator clicks the card the team is talking about, and everyone locked to the moderator follows the same card. The countdown at the right of the action bar follows that card, so each work item gets the same amount of time. When the ",[15,1752,28],{}," tab is open, the forward button moves through the people in that table and skips every absent teammate; on any other tab it follows the board. Select ",[15,1755,1756],{},"Complete"," after ",[15,1759,164],{}," when the session is done, and the planning session and its standup are removed.",{"title":842,"searchDepth":843,"depth":843,"links":1762},[1763,1764,1765,1766,1767,1768,1769,1770],{"id":1508,"depth":843,"text":1509},{"id":189,"depth":843,"text":190},{"id":1553,"depth":843,"text":1554},{"id":1562,"depth":843,"text":1563},{"id":1592,"depth":843,"text":1593},{"id":1637,"depth":843,"text":1638},{"id":1704,"depth":843,"text":1705},{"id":1746,"depth":843,"text":1747},"2026-11-15","Lead a standup in Scrumpy: pick the sprint, follow the speaking order, flag blockers and apply status moves.","Leading a standup","\u002Fog\u002Ftutorial-leading-a-standup.jpg",[867,1776,869],"standup board",{},16,"\u002Ftutorials\u002Fleading-a-standup","tutorial",{"title":1497,"description":1772},{"loc":1779,"lastmod":860},"leading-a-standup","tutorials\u002Fen\u002Fleading-a-standup","tutorial\u002Fleading-a-standup","G3s5x-Jy40FmGpEPfhchMsjxbL93ImE5ucBaVVLHWXo",[1788],{"heading":1789,"description":1790,"path":1791},"Managing sprint dependencies with chained pull requests","Dependent tickets stall a sprint while people wait. Learn how stacked pull requests keep work moving and reduce idle time.","\u002Fblog\u002Fmanage-sprint-dependencies-with-chained-pull-requests",1795345557193]