[{"data":1,"prerenderedAt":948},["ShallowReactive",2],{"tutorial-en-archiving":3},{"doc":4,"prev":113,"next":275,"related":595},{"id":5,"title":6,"body":7,"dateModified":92,"datePublished":92,"description":93,"extension":94,"heading":95,"image":96,"imageAlt":95,"keywords":97,"locale":101,"meta":102,"navigation":103,"order":104,"path":105,"section":106,"seo":107,"sitemap":108,"slug":109,"stem":110,"translationKey":111,"__hash__":112},"tutorials\u002Ftutorials\u002Fen\u002Farchiving.md","Archiving your plans | Tutorials | Scrumpy Planning Poker",{"type":8,"value":9,"toc":85},"minimark",[10,14,19,38,44,47,51,62,67,70,74],[11,12,13],"p",{},"Archiving keeps a permanent record of a planning session or a capacity plan in Confluence. The team can look back later and see what was estimated, what was planned, and why. A space administrator chooses the Confluence space in space settings before anyone can archive.",[15,16,18],"h2",{"id":17},"archive-a-refinement-session","Archive a refinement session",[11,20,21,22,26,27,30,31,34,35,37],{},"Open the ",[23,24,25],"strong",{},"Refinement\u002Fgrooming"," tab, select the planning session, and select ",[23,28,29],{},"Archive"," next to ",[23,32,33],{},"Complete",". The dialog shows the planning window and a preview of the work items with accepted estimates that will be written. Select ",[23,36,29],{}," to create the page.",[39,40],"docs-figure",{"alt":41,"caption":42,"stem":43},"The Refinement\u002Fgrooming archive dialog with the preview of accepted estimates","Refinement archive preview","tutorial-archive-planning",[11,45,46],{},"The generated page keeps the planning title, description, start and end time, the participants, and every accepted estimate with its perspective, votes, participants, and moderator.",[15,48,50],{"id":49},"archive-a-capacity-plan","Archive a capacity plan",[11,52,21,53,56,57,59,60,37],{},[23,54,55],{},"Capacity planning"," tab, select an active or future sprint in the combined table, and select ",[23,58,29],{}," in the toolbar. The dialog previews the sprint and its dates, the sprint goal and its votes, the capacity decision, and the velocity summary. The team and work item tables are written to the page as well. Select ",[23,61,29],{},[39,63],{"alt":64,"caption":65,"stem":66},"The Capacity planning archive dialog with the sprint summary and velocity","Capacity archive preview","tutorial-archive-capacity",[11,68,69],{},"The generated page keeps the planning window, the sprint and goal, the goal votes, the velocity and target capacity, the team with hours and utilization, and the planned work items in order.",[15,71,73],{"id":72},"find-the-pages-later","Find the pages later",[11,75,76,77,80,81,84],{},"Planning session archives sit under the ",[23,78,79],{},"Estimations"," parent page. Capacity archives sit under the ",[23,82,83],{},"Plannings"," parent page, in a child page named after the space and \"Capacity planning\". Archiving the same sprint again updates its page instead of creating a duplicate.",{"title":86,"searchDepth":87,"depth":87,"links":88},"",2,[89,90,91],{"id":17,"depth":87,"text":18},{"id":49,"depth":87,"text":50},{"id":72,"depth":87,"text":73},"2026-11-10","Archive planning sessions, capacity plans, stand-ups and retrospectives to Confluence, with a clear page hierarchy.","md","Archiving your plans","\u002Fog\u002Ftutorial-archiving.jpg",[98,99,100],"confluence archive","planning archive","retrospective archive","en",{},true,15,"\u002Ftutorials\u002Farchiving","tutorial",{"title":6,"description":93},{"loc":105,"lastmod":92},"archiving","tutorials\u002Fen\u002Farchiving","tutorial\u002Farchiving","LUADFXzNR2iP2wk39AwMP3Kv49FDRx0r3OwXBe_zD0Y",{"id":114,"title":115,"body":116,"dateModified":92,"datePublished":92,"description":260,"extension":94,"heading":55,"image":261,"imageAlt":55,"keywords":262,"locale":101,"meta":266,"navigation":103,"order":267,"path":268,"section":106,"seo":269,"sitemap":270,"slug":271,"stem":272,"translationKey":273,"__hash__":274},"tutorials\u002Ftutorials\u002Fen\u002Fcapacity-planning.md","Capacity planning | Tutorials | Scrumpy Planning Poker",{"type":8,"value":117,"toc":250},[118,121,125,139,143,146,150,160,165,169,172,177,181,195,199,202,205,210,214,220,224,228,234,238,245],[11,119,120],{},"Capacity planning helps your team see how much work fits into the next sprints before you commit to it. Scrumpy compares the work you plan with the capacity your team really has, so the conversation starts from numbers instead of guesses.",[15,122,124],{"id":123},"start-with-the-sprints-you-finished","Start with the sprints you finished",[11,126,127,128,130,131,134,135,138],{},"Open the space page and choose the ",[23,129,55],{}," tab. Select your planning session, then select ",[23,132,133],{},"Plan sprint",". In the ",[23,136,137],{},"Past sprints"," tab, tick the closed sprints that should set your team's velocity. Three past sprints give a steady average. Each past sprint should include the work the team completed, and its team should be filled in.",[39,140],{"alt":141,"caption":137,"stem":142},"The Plan sprint dialog with three past sprints selected","tutorial-capacity-plan-sprint-past",[11,144,145],{},"If you are starting for the first time and there are no past sprints, you can still plan. Add the team to the sprint you want to plan, set each person's utilization and hours of work, and Scrumpy calculates the target from that team. Add past sprints later to get a velocity.",[15,147,149],{"id":148},"add-the-active-and-future-sprints-you-want-to-plan","Add the active and future sprints you want to plan",[11,151,21,152,155,156,159],{},[23,153,154],{},"Sprints"," tab in the same dialog and tick the active or future sprints you want to include. You can plan several sprints at once, so the team can compare the next few weeks in one view. Select ",[23,157,158],{},"Add",".",[39,161],{"alt":162,"caption":163,"stem":164},"The Sprints tab of the Plan sprint dialog with an active sprint selected","Active and future sprints","tutorial-capacity-plan-sprint-future",[15,166,168],{"id":167},"the-board-selector-decides-which-sprints-you-can-plan","The board selector decides which sprints you can plan",[11,170,171],{},"This part is important. The sprint picker only lists sprints that originated from the board currently chosen in the board selector at the top left of the capacity table. Switch the board and the list changes. Each board keeps its own plan, so choose the board first, then add its sprints.",[39,173],{"alt":174,"caption":175,"stem":176},"The board selector at the top left of the capacity planning page","Board selector","tutorial-capacity-board-selector",[15,178,180],{"id":179},"add-and-remove-work-items","Add and remove work items",[11,182,183,184,187,188,191,192,159],{},"With a sprint selected in the table, use ",[23,185,186],{},"Add from filter"," to bring in work items from a saved Jira filter, a sprint, or a Refinement\u002Fgrooming session. Drag a work item to reorder it inside its sprint, or drag it onto another sprint row to move it. To remove items, tick them and select ",[23,189,190],{},"Remove",". Removing an item changes the plan, not Jira, until you select ",[23,193,194],{},"Apply",[15,196,198],{"id":197},"read-the-capacity-timeline","Read the capacity timeline",[11,200,201],{},"In this example the planned sprint has seven work items. Their estimates are 1, 2, 3, 5, 8, 5, and 3 story points. The timeline adds them up as you read down the table. Green means there is room, yellow means you are close to the healthy range, and red means the running total is above the capacity your team has.",[11,203,204],{},"If the later work items sit behind a red line, the plan is too big for this team. Remove an item, lower an estimate, or add capacity before you start the sprint.",[39,206],{"alt":207,"caption":208,"stem":209},"The capacity table with seven work items and the timeline turning red above capacity","Capacity timeline","tutorial-capacity-timeline",[15,211,213],{"id":212},"set-up-the-team","Set up the team",[11,215,21,216,219],{},[23,217,218],{},"Team capacity"," tab. This example has three team members. Each person has a utilization percentage and hours of work for the sprint. Time off is added in the person's calendar. When you change a value, the target and the timeline update right away.",[39,221],{"alt":222,"caption":218,"stem":223},"The Team capacity table with three team members and their hours","tutorial-capacity-team",[15,225,227],{"id":226},"agree-on-the-sprint-goal","Agree on the sprint goal",[11,229,21,230,233],{},[23,231,232],{},"Sprint"," tab to write the sprint goal. Everyone can vote with the thumbs up and thumbs down buttons, and the counts update for the whole team. A clear goal helps the team agree on what the sprint is for before voting starts.",[15,235,237],{"id":236},"vote-on-a-work-item-and-chat","Vote on a work item and chat",[11,239,240,241,244],{},"Select a work item in the table, then open a perspective tab to vote with the same cards you use in Refinement\u002Fgrooming. A ",[23,242,243],{},"Chat"," tab appears for the selected work item, so the team can discuss that item without leaving the capacity plan.",[39,246],{"alt":247,"caption":248,"stem":249},"The perspective voting panel and the Chat tab for a planned work item","Vote and chat","tutorial-capacity-voting-chat",{"title":86,"searchDepth":87,"depth":87,"links":251},[252,253,254,255,256,257,258,259],{"id":123,"depth":87,"text":124},{"id":148,"depth":87,"text":149},{"id":167,"depth":87,"text":168},{"id":179,"depth":87,"text":180},{"id":197,"depth":87,"text":198},{"id":212,"depth":87,"text":213},{"id":226,"depth":87,"text":227},{"id":236,"depth":87,"text":237},"Plan the next sprints from recent velocity, read the capacity timeline and apply the plan to Jira.","\u002Fog\u002Ftutorial-capacity-planning.jpg",[263,264,265],"capacity planning","sprint capacity","velocity",{},14,"\u002Ftutorials\u002Fcapacity-planning",{"title":115,"description":260},{"loc":268,"lastmod":92},"capacity-planning","tutorials\u002Fen\u002Fcapacity-planning","tutorial\u002Fcapacity-planning","dXqFjEQiGF7gHvaxbkFg7mAJK_PdEsz8aLt9oMCwdxI",{"id":276,"title":277,"body":278,"dateModified":577,"datePublished":578,"description":579,"extension":94,"heading":580,"image":581,"imageAlt":580,"keywords":582,"locale":101,"meta":586,"navigation":103,"order":587,"path":588,"section":106,"seo":589,"sitemap":590,"slug":591,"stem":592,"translationKey":593,"__hash__":594},"tutorials\u002Ftutorials\u002Fen\u002Fleading-a-standup.md","Leading a standup | Tutorials | Scrumpy Planning Poker",{"type":8,"value":279,"toc":567},[280,286,290,308,313,316,320,323,326,333,338,342,347,351,376,383,387,394,397,402,429,434,438,450,458,463,507,511,517,530,546,551,555],[11,281,282,283,285],{},"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 ",[23,284,194],{},", so you can rearrange the board while you talk without touching Jira.",[15,287,289],{"id":288},"pick-the-planning-session-board-and-sprint","Pick the planning session, board, and sprint",[11,291,21,292,295,296,299,300,303,304,307],{},[23,293,294],{},"Standup"," tab and pick a planning session from the tabs above the board. Pick the ",[23,297,298],{},"board"," first, then the ",[23,301,302],{},"sprint",". 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 ",[23,305,306],{},"filter"," instead, and the standup shows the work items that filter returns, with one column per status.",[39,309],{"alt":310,"caption":311,"stem":312},"The board and sprint selectors above the standup","Choose the board and the running sprint","tutorial-standup-sprint",[11,314,315],{},"Only a moderator changes the shared board. A voter or guest who picks another sprint does so only for their own browser tab.",[15,317,319],{"id":318},"read-the-board","Read the board",[11,321,322],{},"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,324,325],{},"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,327,328,329,332],{},"Use ",[23,330,331],{},"Max per column"," 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.",[39,334],{"alt":335,"caption":336,"stem":337},"The standup board with cards in every column","The sprint as a standup board","tutorial-standup-board",[15,339,341],{"id":340},"flag-a-work-item-that-needs-attention","Flag a work item that needs attention",[11,343,344,345,159],{},"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 ",[23,346,194],{},[15,348,350],{"id":349},"move-work-items-without-leaving-the-standup","Move work items without leaving the standup",[11,352,353,354,357,358,361,362,365,366,368,369,371,372,375],{},"Use the ",[23,355,356],{},"Move to"," dropdown on a card to change its status or its place in the lane. ",[23,359,360],{},"By status"," offers the statuses the card can reach in Jira, and ",[23,363,364],{},"By rank"," 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 ",[23,367,360],{}," disabled until you undo or apply that move, while ",[23,370,364],{}," stays available. The statuses are read when you open the menu, so the first open can take a moment and shows ",[23,373,374],{},"Loading statuses"," until they arrive.",[11,377,378,379,382],{},"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. ",[23,380,381],{},"Discard changes"," is the button that asks you to confirm before it clears everything.",[15,384,386],{"id":385},"follow-the-same-standup-in-the-status-table","Follow the same standup in the Status table",[11,388,389,390,393],{},"The ",[23,391,392],{},"Status"," 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,395,396],{},"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.",[39,398],{"alt":399,"caption":400,"stem":401},"The Status table with the same work items and staged moves as the board","The same standup as a compact table","tutorial-standup-order",[403,404,405,413,416,419,426],"ul",{},[406,407,408,409,412],"li",{},"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 ",[23,410,411],{},"M"," on that row.",[406,414,415],{},"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.",[406,417,418],{},"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.",[406,420,421,422,425],{},"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 ",[23,423,424],{},"Assignee"," table.",[406,427,428],{},"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,430,431,433],{},[23,432,194],{}," writes the new order and the staged moves to Jira from here too.",[15,435,437],{"id":436},"see-who-is-in-the-room","See who is in the room",[11,439,389,440,442,443,445,446,449],{},[23,441,424],{}," tab follows ",[23,444,392],{}," 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. ",[23,447,448],{},"Unassigned"," sits last and holds the work items that have no assignee.",[11,451,452,453,455,456,425],{},"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 ",[23,454,392],{}," 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 ",[23,457,392],{},[39,459],{"alt":460,"caption":461,"stem":462},"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",[403,464,465,473,482,485,490,496,502],{},[406,466,467,468,470,471,159],{},"Drag a work item into another person's row to give it to them. The board avatar, the card color, and the ",[23,469,392],{}," row show the new person right away, but Jira changes only when you press ",[23,472,194],{},[406,474,389,475,477,478,481],{},[23,476,331],{}," 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 ",[23,479,480],{},"Participants"," picker, until you raise the cap.",[406,483,484],{},"A moderator can give any work item to another person. A voter can give only their own work items. Guests read the table.",[406,486,389,487,489],{},[23,488,480],{}," 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.",[406,491,492,493,495],{},"When a person is absent, their work items cannot be selected, from this table, from the ",[23,494,392],{}," 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.",[406,497,498,499,501],{},"With the ",[23,500,424],{}," tab open, the countdown forward button walks this table and skips every absent person, so the standup continues with the next teammate.",[406,503,504,506],{},[23,505,448],{}," is always present and has no checkbox.",[15,508,510],{"id":509},"apply-the-changes-to-jira","Apply the changes to Jira",[11,512,513,514,516],{},"This is the step that makes the changes real. Press ",[23,515,194],{}," 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,518,519,520,522,523,525,526,529],{},"A moderator can also archive the standup with ",[23,521,29],{},", which sits before ",[23,524,194],{}," 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 ",[23,527,528],{},"Pending",". Archiving never changes Jira or the staged changes.",[11,531,532,533,535,536,538,539,541,542,545],{},"Without ",[23,534,194],{},", nothing is saved to Jira. Closing the tab or picking another sprint leaves Jira exactly as it was. If you change your mind, press ",[23,537,381],{}," and confirm the dialog instead. Discard removes every staged change and clears every passed check, and it does not touch Jira. ",[23,540,194],{}," clears the passed checks too, because the walkthrough is over. ",[23,543,544],{},"Reload sprints and work items"," reads the sprint from Jira again.",[39,547],{"alt":548,"caption":549,"stem":550},"The action bar with the pending changes and the Apply button","Apply writes the standup to Jira","tutorial-standup-apply",[15,552,554],{"id":553},"keep-everyone-in-step","Keep everyone in step",[11,556,557,558,560,561,563,564,566],{},"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 ",[23,559,424],{}," 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 ",[23,562,33],{}," after ",[23,565,194],{}," when the session is done, and the planning session and its standup are removed.",{"title":86,"searchDepth":87,"depth":87,"links":568},[569,570,571,572,573,574,575,576],{"id":288,"depth":87,"text":289},{"id":318,"depth":87,"text":319},{"id":340,"depth":87,"text":341},{"id":349,"depth":87,"text":350},{"id":385,"depth":87,"text":386},{"id":436,"depth":87,"text":437},{"id":509,"depth":87,"text":510},{"id":553,"depth":87,"text":554},"2026-11-21","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",[583,584,585],"daily standup","standup board","jira standup",{},16,"\u002Ftutorials\u002Fleading-a-standup",{"title":277,"description":579},{"loc":588,"lastmod":577},"leading-a-standup","tutorials\u002Fen\u002Fleading-a-standup","tutorial\u002Fleading-a-standup","G3s5x-Jy40FmGpEPfhchMsjxbL93ImE5ucBaVVLHWXo",{"id":596,"title":597,"body":598,"dateModified":577,"datePublished":931,"description":932,"extension":94,"heading":642,"image":933,"imageAlt":642,"keywords":934,"locale":101,"meta":938,"navigation":103,"order":939,"path":940,"section":941,"seo":942,"sitemap":943,"slug":944,"stem":945,"translationKey":946,"__hash__":947},"guide\u002Fguide\u002Fen\u002Farchiving-to-confluence.md","Archiving to Confluence | Scrumpy Planning Poker",{"type":8,"value":599,"toc":921},[600,603,607,618,624,628,640,644,661,670,676,680,691,695,703,716,719,746,753,756,760,775,778,780,801,814,818,830,835,847,851,854,881,884,888,894,915],[11,601,602],{},"A moderator can archive a planning session to a Confluence page, giving the team a permanent record of the accepted estimates. Archiving is optional and only available after a Confluence space has been configured for the Jira space.",[15,604,606],{"id":605},"configuring-the-confluence-space","Configuring the Confluence Space",[11,608,609,610,613,614,617],{},"In space settings, open the ",[23,611,612],{},"Permissions"," tab and find ",[23,615,616],{},"Confluence space",", below the roles. Use the search box to find a space by name or key and select it; only the space key is stored. Leave it empty to disable archiving. Only a space administrator can change this setting. The search shows only Confluence spaces your account can access.",[11,619,620,621,623],{},"If Scrumpy is not installed on Confluence for your site, the ",[23,622,616],{}," field is disabled and a note explains that Confluence export is available only after the app is installed on Confluence.",[15,625,627],{"id":626},"archiving-a-planning-session","Archiving a Planning Session",[11,629,630,631,633,634,636,637,639],{},"On the ",[23,632,25],{}," tab, the ",[23,635,29],{}," button sits at the end of the action bar below the planning table and appears only when a Confluence space is configured. Clicking ",[23,638,29],{}," opens a dialog that previews exactly what will be written:",[39,641],{"alt":642,"caption":642,"stem":643},"Archiving to Confluence","guide-archive",[403,645,646,649,652,655,658],{},[406,647,648],{},"When the planning session has a timer, the window is shown as a start badge and an end badge",[406,650,651],{},"The preview table lists the work items that have an accepted estimate inside the window, with Type, Work item, Perspective, and Estimate columns, and can be sorted",[406,653,654],{},"A planning session without a timer has no window, so its preview lists every work item with an accepted estimate",[406,656,657],{},"Work items you cannot open in Jira are omitted, including work items hidden by Jira issue-level security",[406,659,660],{},"When nothing is listed, the dialog explains why: no estimates have been accepted for this session yet, or the session has accepted estimates but none fall inside the planning window",[11,662,663,664,666,667,669],{},"Confirm with ",[23,665,29],{},". On success the dialog shows a link to the created page. The ",[23,668,29],{}," button is disabled whenever the preview lists no work items (while it is loading, when none have been accepted, when they all fall outside the planning window, or when the preview fails to load). Only moderators can archive.",[11,671,672,673,675],{},"When Scrumpy is not installed on Confluence, the ",[23,674,29],{}," button is disabled and explains why. The Delete dialogs then do not offer the archive option.",[15,677,679],{"id":678},"archiving-while-deleting","Archiving While Deleting",[11,681,682,683,686,687,690],{},"When a Confluence space is configured, both Delete dialogs offer a ",[23,684,685],{},"Create a Confluence archive page"," checkbox. When checked, the archive runs after any chosen accept or cancel action and before the planning session is removed. The resulting page link, or the failure message, is shown as a banner in the Refinement\u002Fgrooming tab. The banner offers a ",[23,688,689],{},"Dismiss"," action that hides it.",[15,692,694],{"id":693},"archiving-a-capacity-plan","Archiving a Capacity Plan",[11,696,630,697,699,700,702],{},[23,698,55],{}," tab, select an active or future sprint in the combined table, then select ",[23,701,29],{}," in the capacity toolbar. The button is disabled when a closed sprint is selected, because a closed sprint is history only. Only a moderator can archive, and the action is available only after a Confluence space has been configured for the space.",[11,704,705,706,708,709,711,712,715],{},"The dialog previews the sprint, the goal and its votes, the decision, and the velocity summary before anything is written. The team and work item tables are written to the page only. While the preview loads, ",[23,707,29],{}," stays disabled. If the preview cannot load, the dialog says so, and you can close it and try again. Confirm with ",[23,710,29],{}," to create the page, or select ",[23,713,714],{},"Close"," to leave the capacity plan unchanged. When the page is ready, the dialog shows a link to it. If Confluence refuses the page, the dialog shows the reason and the capacity plan is not changed.",[11,717,718],{},"The page records:",[403,720,721,724,727,730,737,740,743],{},[406,722,723],{},"The planning session title, description, start and end time, and timezone, in the same header as the planning archive page, followed by the planning duration",[406,725,726],{},"The selected sprint name, state, start and end dates, and sprint goal",[406,728,729],{},"The up and down votes for the sprint goal",[406,731,732,733,736],{},"A ",[23,734,735],{},"Decision"," section that says whether the remaining estimate is below, within, or above the target capacity range",[406,738,739],{},"A velocity summary with the velocity per member, team velocity, team size, effective team size, team capacity, target capacity, healthy range, planned estimate, remaining estimate, and deviation from target",[406,741,742],{},"A team table with every member of the selected sprint, their utilization, and their hours of work out of the sprint working hours",[406,744,745],{},"The planned work items in their saved order, with their status and estimate. An estimate is shown in green while the running total stays below the healthy range, in yellow inside the range, and in red above it, matching the capacity table.",[11,747,748,749,752],{},"The header is the same one the planning archive page uses: the planning title and description, then the start and end on separate lines, with each date shown as a Confluence date chip and each time highlighted in a blue badge, and the timezone the dates are valid in. The planning duration follows the header as a plain line. The sprint goal and its up and down votes appear centered directly below the sprint name, and the sprint goal is shown without a label. The sprint start and end dates share one line and are separated by a dash, for example ",[23,750,751],{},"Oct 7, 2026 - Oct 15, 2026",". The team and work item tables use a wider layout, and the Work item column leaves room for a longer summary.",[11,754,755],{},"The page reflects the capacity plan as it currently appears, including changes that are still saved as a draft and have not been applied to Jira. Story point boards show story points, and time boards show work-day durations.",[15,757,759],{"id":758},"archiving-a-retrospective","Archiving a Retrospective",[11,761,630,762,633,765,767,768,770,771,774],{},[23,763,764],{},"Retrospective",[23,766,29],{}," button sits before ",[23,769,194],{},". It is available to moderators in the ",[23,772,773],{},"Actions"," stage. In Feedback and Vote it stays disabled with an explanation, because the notes of other participants are still hidden until the team reveals them. Archiving creates or updates the Confluence page and does not close the planning session.",[11,776,777],{},"The dialog previews the archive for the selected sprint before anything is written. It shows the planning window, the board and sprint name, the sprint goal, the sprint state, how many notes each column contributes, and the action items with their work item type icon, their linked Jira work item or summary, and their hearts. The confirmation button stays disabled while the preview loads, when the preview cannot load, and when the sprint has neither notes nor action items. Only a moderator can archive.",[11,779,718],{},[403,781,782,785,788,791,794],{},[406,783,784],{},"The planning title, description, start and end time, and timezone",[406,786,787],{},"The board name, sprint name, sprint goal, sprint dates, and sprint state",[406,789,790],{},"A notes table with one column per retrospective column, such as Good, Bad, and Ugly. Each note sits in its own cell, and notes that the team grouped together share one cell. Authors, hearts, and votes are not written to the page.",[406,792,793],{},"A participants table with every note author, everyone who gave a heart, and every action item author, showing the number of notes and hearts for each person. The hearts column is headed with a heart icon.",[406,795,796,797,800],{},"An action items table with a ",[23,798,799],{},"Summary"," first column that is twice as wide as before. A linked action item shows its Jira work item link; an action item without a link shows its summary as text. The rows keep the order the moderator set in the retrospective. The narrow last column is headed with a heart icon and shows the number of hearts in a colored badge. The number is the total hearts of the notes the action item came from, the same number the retrospective shows.",[11,802,803,804,807,808,810,811,813],{},"Retrospective archives use their own hierarchy: a root ",[23,805,806],{},"Retrospectives"," parent page, then a child page named after the space with a ",[23,809,806],{}," suffix, then the archive page. The page title carries the planning name, the sprint name, and the word ",[23,812,764],{},", so it never collides with planning or capacity archives. Re-archiving the same sprint updates the existing page.",[15,815,817],{"id":816},"archiving-a-standup","Archiving a Standup",[11,819,630,820,633,822,767,824,826,827,829],{},[23,821,294],{},[23,823,29],{},[23,825,194],{}," and is available to moderators when a Confluence space is configured. Archiving never applies, discards, or completes the standup and never changes Jira. The dialog previews the planning window, the scope and space name, the participants with their presentation time, and the work items with their changes. Confirm with ",[23,828,29],{}," to create or update the page.",[11,831,832,833,159],{},"The page records the planning header, the sprint, board, or filter name, the space name, the sprint goal and state, every assignee with presence, item count, and presentation time, and every work item with its status, presentation time, and changes. Presentation time is the countdown time the work item spent on screen, credited to its assignee. A staged change is marked ",[23,834,528],{},[11,836,837,838,840,841,843,844,846],{},"Standup archives use the ",[23,839,83],{}," root. The child page is named after the space with a ",[23,842,294],{}," suffix, and the page title carries the planning name, the scope name, the word ",[23,845,294],{},", and the planning start time.",[15,848,850],{"id":849},"the-archive-page","The Archive Page",[11,852,853],{},"Planning, capacity, retrospective, and standup archives all start with the same planning session header. The generated planning page contains:",[403,855,856,863,866,869,874],{},[406,857,858,859,862],{},"The planning title, followed by the start date, time, and timezone (for example ",[23,860,861],{},"Sprint 42 - 2025-06-01 09:00 (Europe\u002FBerlin)",")",[406,864,865],{},"The description, then the start and end on separate lines, with each date shown as a Confluence date chip and each time highlighted in a blue badge",[406,867,868],{},"The timezone the dates are valid in",[406,870,732,871,873],{},[23,872,480],{}," section listing every voter who actually voted, with their number of votes, as a small table with a Votes column and a Participant column (each voter is one row)",[406,875,876,877,880],{},"An ",[23,878,879],{},"Estimated work items"," table of the accepted estimates, with columns Work item, Perspective, Duration, Votes (each given vote as a badge), Participants (the voters shown as a group of users), Estimate (a badge that is green when the computed average was chosen and yellow when the moderator set a different value), and Moderated by (the user who started the voting session)",[11,882,883],{},"The page includes only the accepted estimates that fall between the planning session's start and end. A planning session without a timer has no window, so its page includes every accepted estimate, has no start, end, or timezone line, and its title carries only the planning name. All dates and times are rendered in the archiver's preferred timezone.",[15,885,887],{"id":886},"page-hierarchy-and-re-archiving","Page Hierarchy and Re-Archiving",[11,889,890,891,893],{},"Planning-session archives are written under a fixed hierarchy: a root ",[23,892,79],{}," parent page, then a child page named after the Jira space, then the archive page.",[11,895,896,897,899,900,904,905,907,908,911,912,914],{},"Capacity-plan archives use a separate hierarchy at the same level: a root ",[23,898,83],{}," parent page, then a child page named ",[901,902,903],"code",{},"\u003Cspace name> - Capacity planning",", then the archive page. Standup archives share the ",[23,906,83],{}," root but use a child page named ",[901,909,910],{},"\u003Cspace name> - Standup",", and their page titles carry the word ",[23,913,294],{},". The distinct page titles keep the four archive kinds apart and stop one from overwriting another.",[11,916,917,918,920],{},"Re-archiving the same sprint updates the existing capacity or standup page (matched by exact title inside the ",[23,919,83],{}," area) instead of creating a duplicate. The created page is a normal Confluence page and is not removed when Scrumpy purges estimation data after its 90-day retention window.",{"title":86,"searchDepth":87,"depth":87,"links":922},[923,924,925,926,927,928,929,930],{"id":605,"depth":87,"text":606},{"id":626,"depth":87,"text":627},{"id":678,"depth":87,"text":679},{"id":693,"depth":87,"text":694},{"id":758,"depth":87,"text":759},{"id":816,"depth":87,"text":817},{"id":849,"depth":87,"text":850},{"id":886,"depth":87,"text":887},"2026-10-11","Archive planning sessions, capacity plans, stand-ups and retrospectives to Confluence pages that stay with your team.","\u002Fog\u002Fguide-archiving-to-confluence.jpg",[935,936,937],"confluence archiving","sprint retrospective archive","jira confluence",{},12,"\u002Fgetting-started\u002Farchiving-to-confluence","guide",{"title":597,"description":932},{"loc":940,"lastmod":577},"archiving-to-confluence","guide\u002Fen\u002Farchiving-to-confluence","guide\u002Farchiving-to-confluence","frifiz6pWms7zEA57HRYz7R6D-Pf8PEpSyY6kbkapIc",1795345575961]