# Feature AGILE-47 - "Sprint Planning" view

Project: Stream agile
Status: closed
URL: https://community.openproject.org/work_packages/AGILE-47

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | High |
| Target versions | 17.3.0 |
| Sprint |  |
| Backlog bucket |  |
| Votes |  |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

| ID | Subject | Status | Decision |
| --- | --- | --- | --- |
| AGILE-77 | Will we continue to display the version based backlogs in 17.3 | decided | Yes |
| AGILE-78 | Is a filter on the sprints required in 17.3 on the sprint planning page | decided | Not required, since there are likely not very many sprints in planning or active at the same time |

## Features and Chunks

| ID | Subject | Type | Status | Assignee | Target versions | Spent time |
| --- | --- | --- | --- | --- | --- | --- |
| AGILE-100 | Add makeshift start sprint button | Implementation | closed |  | 17.3.0 |  |
| AGILE-101 | Page overhaul: swap backlogs and sprint position around | Implementation | closed |  | 17.3.0 |  |
| AGILE-104 | Implement most WorkPackage menu items | Implementation | closed |  | 17.3.0 |  |

## Bugs and other work packages

| ID | Type | Subject | Status | Assignee | Target versions | Spent time | Module |
| --- | --- | --- | --- | --- | --- | --- | --- |
| AGILE-162 | Bug | Backlogs: Sprint can be edited from projects that receive sprints | rejected |  | 17.3.0 |  | Modules and project features / Backlogs |
| AGILE-161 | Bug | Backlogs: Success message is missing when url copied to clipboard | rejected | Tobias Dillmann | 17.3.0 |  | Modules and project features / Backlogs |

## Technical Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan |  |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups | https://www.figma.com/design/yRewu4Y5nuWCa8aMM3DFw3/Agile--Sprints-and-Backlogs?node-id=1062-25614&p=f&t=rMB9teFPE9tB6rqf-0 |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Developers |  |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| PD (min) |  |
| PD (max) |  |
| Work |  |
| Labor costs |  |

## Description

**As** an agile user  
**I want to** have a central page for planning my sprints  
**so that** I know where to do it and have the means to efficiently plan my sprints

**Acceptance criteria**

  - Add a menu item "Sprint planning" to the "Backlog" menu
    
      - This menu item is the default menu item for Backlog. It opens when Backlog is clicked

  - This replaces the existing Backlogs page

  - The backlogs are displayed to the left
    
      - <mention class="mention" data-id="72198" data-type="work_package" data-text="###72198">###72198</mention> is displayed by default
    
      - ~~The version backed backlogs are selectable from a drop down above~~
        
          - This is probably no longer necessary as in 17.3 the "Inbox" backlog will be developed (<mention class="mention" data-id="72198" data-type="work_package" data-text="###72198">\#\#\#72198</mention> )
        
          - ~~In the version settings, the "Column in backlogs" select is switched to a checkbox. It reads "Use as backlog".~~
            
              - ~~Existing versions having "Column in backlogs" set to "right", have the checkbox checked.~~
            
              - ~~Since there is a feature flag in place, the database cannot be changed yet.~~
    
      - The backlog is restyled. See Figma. (done in 17.4 -> <mention class="mention" data-id="72944" data-type="work_package" data-text="###72944">###72944</mention>)

  - The sprints are displayed to the right
    
      - Only sprints that are "In planning" or "Active" are displayed
    
      - The sprints are ordered by dates first and then by name (ascending)
    
      - The sprints are restyled. See Figma. (done in 17.4 -> <mention class="mention" data-id="72945" data-type="work_package" data-text="###72945">###72945</mention>)

  - Work packages displayed in either sprint or backlog
    
      - restyling will be done 17.4 in <mention class="mention" data-id="73089" data-type="work_package" data-text="###73089">\#\#\#73089</mention>
    
      - have a menu
        
          - Open details view (opens split screen)
        
          - Open fullscreen view
        
          - Copy url to clipboard
        
          - Copy work package id
        
          - Create new below (done in 17.4 -> <mention class="mention" data-id="73088" data-type="work_package" data-text="###73088">###73088</mention>)
        
          - Move
            
              - options to move
                
                  - top
                
                  - up
                
                  - down
                
                  - bottom
            
              - to a sprint -> (done in 17.4 -> <mention class="mention" data-id="73087" data-type="work_package" data-text="###73087">###73087</mention>)

  - No filter header in the initial phase.

  - There is a "+ Sprint" button that opens the sprint creation modal.

**Technical notes**

  - 
    <br>

**Permissions and visibility considerations**

  - "View sprints" required to access the page

  - "Create sprints" to see the "+ Sprint" page and use it
    
      - It will only be displayed if the project is configured to have own sprints (not receiving)

  - "Manage sprint items" required to add/remove items to/from a sprint and to reorder the sprint.

  - "Start/complete sprint" required to change the status of the sprint.

  - Sprints that are shared with the project, can be edited. The user is checked to have the "Create sprints" permission in the project the sprint is defined in. 

**Translation considerations**

  - *Key terms and phrases in the key languages* 

**Out of scope**

  - In the version settings, the "Column in backlogs" select is switched to a checkbox. It reads "Use as backlog". Handled in <mention class="mention" data-id="71250" data-type="work_package" data-text="##71250">\#\#71250</mention>

*Set the* **To be informed/consulted teams** *field to include all teams necessary to be informed of the changes.*