30 lines
932 B
Markdown
30 lines
932 B
Markdown
# 07 Board View and Ticket Status Movement
|
|
|
|
## Goal
|
|
|
|
Expose the Kanban board UI and allow tickets to move between backlog and project-defined board columns.
|
|
|
|
## Requirements
|
|
|
|
- Provide a board view per project.
|
|
- Only tickets assigned to board columns appear on the board.
|
|
- Backlog tickets stay out of board columns until moved.
|
|
- Users with the correct permission can move tickets:
|
|
- from backlog to a board column
|
|
- between board columns
|
|
- from a board column back to backlog
|
|
- The UI must reflect the project's configured board column order.
|
|
|
|
## Acceptance Criteria
|
|
|
|
- Moving a ticket to a board column makes it visible on the board.
|
|
- Moving a ticket back to backlog removes it from the board.
|
|
- Invalid status moves to columns belonging to another project are rejected.
|
|
- Status changes are captured in the ticket worklog.
|
|
|
|
## Out of Scope
|
|
|
|
- Real-time multi-user board updates
|
|
- Board filtering
|
|
- Board swimlanes
|