Content
View differences
Updated by Alexander Coles 11 days ago
## 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" "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\]" "[Project ID] [Sprint Name]" (e.g., "ABC: "ABC Sprint 23")
* 23")
- Board is immediately accessible via the project's 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' packages' workflows. All statuses are shown automatically in columns. No status
mapping at this stage (will follow in future Epic next iterations).
- see <mention class="mention" data-id="71104" data-type="work_package" data-text="#71104">#71104</mention> ).
* Board filter automatically includes:
*
- All work packages issues assigned to the active sprint
*
- All work packages issue types enabled for the project
* ~~Board
- Board shows sprint goal prominently at the top (if defined)~~
defined)
### Board Visibility & & Access
*
- Board inherits project permissions automatically
*
- All project members can view the board immediately
Users can currently create "status boards", which are kanban boards. Once created, there is only the "new" column there.
## Acceptance Criteria
*
-
*
-
*
-
*
-
*
-
*
-
* Board filter automatically includes:
*
-
*
-
* ~~Board
- Board
*
-
*
-