Skip to content

Add Project model — TODO/tasks belong to Project, not Channel #33

@kagura-agent

Description

@kagura-agent

Feature

Introduce a Project entity as a first-class concept. TODO/tasks belong to Project, Channel is just a communication surface.

Design

  • Project has: name, purpose, status, tasks/TODO list
  • Channel can be linked to a Project (many channels → one project)
  • Creating a channel auto-creates a same-name Project and links them (default 1:1)
  • Users can later: link multiple channels to one project, switch project, or have project-only (no channel)
  • TODO/Kanban views show the linked Project's tasks, regardless of which channel you're in

Why

From our Discord experience: one project can span multiple channels, but tasks belong to the project not the channel. project ≠ channel ≠ repo.

Migration

Current per-channel TODO items should migrate to auto-created projects (one per existing channel).

Related to the Workshop v2 product direction: Workshop as a project-centric workspace.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions