# Feature AGILE-520 - Static read only sprint board (no filters, no configuration)

Project: Stream agile
Status: specified
URL: https://community.openproject.org/work_packages/AGILE-520

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions |  |
| Sprint | Sprint 14 |
| Backlog bucket |  |
| Votes |  |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Use cases

_No work packages_

## Features and Chunks

_No work packages_

## Bugs and other work packages

_No work packages_

## Technical Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Feature Flag | Server sprint boards |
| Requires doc change | Yes |
| Enterprise plan | Community (COM) |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups | https://www.figma.com/design/yRewu4Y5nuWCa8aMM3DFw3/Agile--Sprints-and-Backlogs?node-id=9192-146937&t=gsdjD8TjKBhS6uww-0 |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Feature Lead |  |
| Developers | OP Dev Polaris Team |
| Designer | Julia Racsko |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

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

## Description

**As** a user of Scrum methodology  
**I want to** have a static, read only sprint board (to be improved later)  
**so that** I can easily see the work packages of a sprint grouped by the status they are in

This is meant to be the first step in a series of feature. That is why the functionality is very limited.

**Acceptance criteria**

*   A feature flag `server_sprint_board` hides the development. Until the full epic is developed, the existing (Angular based) boards are used in production.
    
*   A single board exists in a project where backlogs is enabled displaying a sprint&#x27;s work packages grouped by status
    
    *   There is one column for every status a work package in the sprint has. They are in the order configured for statuses.&nbsp;
        
        *   A status without a work package in the sprint having that status will not be displayed.
            
    *   Work packages are displayed as cards (same as used in backlogs) grouped into the column representing the status they have.
        
    *   The order the work packages are displayed in is the same order the work packages have in the sprint.
        
        *   Given that they are grouped by status, the order is enforced per group.
            
    *   The board always shows the currently active sprint.
        
        *   If none is active, show a blankslate
            
    *   The board has a static url. 
        
    *   The board has a number of limitations due to them not being fully developed. Those are not intended to stay
        
        *   The board is read only.
            
        *   The board cannot be configured (e.g. columns).
            
        *   There is only a single sprint board without the ability to switch the view to a different sprint.
            

**Technical notes**

*   The implementation follows the patterns established on the backlogs page.
    

**Permissions and visibility considerations**

*   Users need the permission to view sprints and to view boards
    

**Translation considerations**

*   _Key terms and phrases in the key languages_
    

**Out of scope**

*   When multiple sprints can be active in the project, fall back to angular based boards
    
*   Drag &amp; drop
    
*   column configuration
    
*   filtering
    
*   saving views
    

_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._
