KanbanGit/docs/releases/0.1-kanban-foundation/02-projects-and-project-keys.md

02 Projects and Project Keys

Goal

Introduce the core project entity and the immutable project key system that future ticket keys depend on.

Requirements

• Create project management for authenticated users with the proper permission checks in place.
• A project must store at least:
  • name
  • key
• Project key rules:
  • maximum length 5
  • automatically normalized to uppercase
  • unique across the entire application
  • treated as immutable after creation
• Provide project creation and project listing in the UI.
• The project detail area should become the entry point for backlog, board, and project settings.

Acceptance Criteria

• A project can be created with a valid uppercase key of at most 5 characters.
• Duplicate project keys are rejected.
• Once created, the project key is not editable through the UI or standard update flow.
• Project detail navigation leaves clear room for board, backlog, and settings sections.

Out of Scope

• Roadmap UI
• Repository connections
• Advanced project metadata beyond name and key