codex - added docu
This commit is contained in:
@@ -0,0 +1,30 @@
|
||||
# 04 Board Columns and Project Workflow Settings
|
||||
|
||||
## Goal
|
||||
|
||||
Allow each project to configure its own Kanban board structure through project settings.
|
||||
|
||||
## Requirements
|
||||
|
||||
- Each project must have exactly one board configuration context.
|
||||
- Board columns are project-specific and ordered.
|
||||
- A project admin or otherwise authorized user can:
|
||||
- create columns
|
||||
- rename columns
|
||||
- reorder columns
|
||||
- delete columns
|
||||
- Board columns define the valid in-board statuses for tickets.
|
||||
- The backlog remains separate from board columns and is not just another normal board column.
|
||||
|
||||
## Acceptance Criteria
|
||||
|
||||
- A project can have any number of board columns.
|
||||
- Column order is reflected consistently in project settings and the board UI.
|
||||
- Deleting or changing columns is protected by project-level permissions.
|
||||
- Ticket status validation only allows backlog or one of the project's configured board columns.
|
||||
|
||||
## Out of Scope
|
||||
|
||||
- Swimlanes
|
||||
- WIP limits
|
||||
- Board automation rules
|
||||
Reference in New Issue
Block a user