35 lines
985 B
Markdown
35 lines
985 B
Markdown
# 06 Ticket Creation and Backlog
|
|
|
|
## Goal
|
|
|
|
Implement the first ticket creation flow and establish backlog as the default intake for all new work.
|
|
|
|
## Requirements
|
|
|
|
- Tickets must belong to exactly one project.
|
|
- A ticket stores at least:
|
|
- immutable ticket key
|
|
- title
|
|
- description
|
|
- acceptance criteria
|
|
- type
|
|
- priority
|
|
- New tickets always start in backlog.
|
|
- Ticket keys must follow the format `PROJECTKEY-INDEX`.
|
|
- The sequence index is project-local, increasing, and immutable.
|
|
- Ticket titles are not unique and must not be used as identifiers.
|
|
- Provide backlog listing for a project.
|
|
|
|
## Acceptance Criteria
|
|
|
|
- Creating a ticket in project `AUTH` produces keys like `AUTH-1`, `AUTH-2`, and so on.
|
|
- Newly created tickets appear in backlog, not in a board column.
|
|
- Duplicate titles are allowed.
|
|
- Ticket creation is guarded by the project's `create` permission.
|
|
|
|
## Out of Scope
|
|
|
|
- Bulk ticket creation
|
|
- Attachments
|
|
- Comments as a discussion system
|