# Feature AGILE-22 - Create boards on Sprint start

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

## Planning

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

## OPEN POINTS / FEEDBACK

_No work packages_

## Features and Chunks

| ID | Subject | Type | Status | Assignee | Target versions | Spent time |
| --- | --- | --- | --- | --- | --- | --- |
| AGILE-122 | Add active sprint per project database constraint | Implementation | closed |  | 17.3.0 |  |

## Bugs and other work packages

| ID | Type | Subject | Status | Assignee | Target versions | Spent time | Module |
| --- | --- | --- | --- | --- | --- | --- | --- |
| AGILE-137 | Code maintenance | Clean up controllers and routing constraints | rejected | OP Dev Polaris Team | 17.4.0 |  |  |

## Technical Details

| Attribute | Value |
| --- | --- |
| Module | Frontend components and Primer design system, Modules and project features / Boards |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan |  |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview | https://pr-22086-69139-sprint-task-b-ip-23-88-121-1.my.opf.run:443 |
| Mockups |  |
| Accessibility | No |

## People

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

## Estimates and progress

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

## Description

## Status quo

Users can currently create "status boards", which are kanban boards. Once created, there is only the "new" column there.

## Acceptance Criteria

### Automatic Board Creation

  - When user clicks "Start Sprint" from the backlog, system automatically creates a dedicated sprint board (based on status boards within OpenProject)

  - User is automatically forwarded to the active sprint board

  - Board is named using convention: "\[Project name\]: \[Sprint name\]" (e.g., "ABC: Sprint 23")

  - Board is immediately accessible via the project's board section

  - Board creation happens seamlessly without additional user prompts or configuration steps

### Default Board Configuration

  - Columns map to appropriate workflow statuses from the project work packages' workflows. All statuses are shown automatically in columns. No status mapping at this stage (will follow in future Epic - see <mention class="mention" data-id="71104" data-type="work_package" data-text="#71104">\#71104</mention> ).

  - Board filter automatically includes:
    
      - All work packages assigned to the active sprint
    
      - All work packages types enabled for the project

  - ~~Board shows sprint goal prominently at the top (if defined)~~

### Board Visibility & Access

  - Board inherits project permissions automatically

  - All project members can view the board immediately