Deployment type
self-host
What do you want and why?
Deployment type
Both (Official App and Self-hosted)
What do you want and why?
Feature Request
Problem
Multica currently has a flat issue structure — every issue lives directly in a workspace with no way to group them into larger bodies of work or time-boxed iterations. Teams working across multiple projects with human + AI members need two foundational planning primitives that every major project management tool provides:
- Epics — a parent container that groups related issues under a single goal, making it possible to track progress at a higher level than individual tasks.
- Sprints / Iterations — a fixed-length time box (e.g. 1–2 weeks) that scopes which issues the team (human and agent alike) commits to completing within that period.
Without these, workspaces quickly become an undifferentiated list of issues with no structure above the task level, making it impossible to plan a release, track a feature end-to-end, or run a scrum-style workflow.
Proposed Solution
Epics
- Add an
Epic issue type (or a first-class Epic entity) that can contain child issues.
- Display epic progress as a completion percentage based on the ratio of closed child issues to total child issues.
- Allow issues to be linked to (or unlinked from) an epic at any time.
- Show an "epic" column/filter on the board view so teams can scope the board to a single epic.
- Agents should be assignable to epics and be able to create child issues under an epic autonomously.
Sprints / Iterations
- Add a
Sprint entity per workspace with a name, start date, end date, and goal field.
- Allow issues (and epics) to be added to a sprint from the board or issue detail view.
- Show a sprint selector at the top of the board to switch context between the active sprint, past sprints, and the backlog.
- Display sprint progress (issues completed vs. total) and a simple burndown counter.
- Agents receive sprint context in their task prompt so they understand the time constraint and priority of the current iteration.
Use Case
A software team running a 2-week sprint assigns 20 issues to the sprint and groups them under 3 epics (Auth, Payments, Dashboard). Human members handle design and review; AI agents handle implementation issues. The PM can see at a glance that the "Auth" epic is 80% done with 2 days left, and that 3 issues in the "Payments" epic are still unstarted and need to be reassigned or moved to the next sprint.
Proposed solution (optional)
No response
Screenshots / mockups (optional)
No response
Deployment type
self-host
What do you want and why?
Deployment type
Both (Official App and Self-hosted)
What do you want and why?
Feature Request
Problem
Multica currently has a flat issue structure — every issue lives directly in a workspace with no way to group them into larger bodies of work or time-boxed iterations. Teams working across multiple projects with human + AI members need two foundational planning primitives that every major project management tool provides:
Without these, workspaces quickly become an undifferentiated list of issues with no structure above the task level, making it impossible to plan a release, track a feature end-to-end, or run a scrum-style workflow.
Proposed Solution
Epics
Epicissue type (or a first-classEpicentity) that can contain child issues.Sprints / Iterations
Sprintentity per workspace with a name, start date, end date, and goal field.Use Case
A software team running a 2-week sprint assigns 20 issues to the sprint and groups them under 3 epics (Auth, Payments, Dashboard). Human members handle design and review; AI agents handle implementation issues. The PM can see at a glance that the "Auth" epic is 80% done with 2 days left, and that 3 issues in the "Payments" epic are still unstarted and need to be reassigned or moved to the next sprint.
Proposed solution (optional)
No response
Screenshots / mockups (optional)
No response