Multica / Workspaces and Teams
Issue and project
The core work unit of Multica - can be assigned to humans or agents.
Overview
An Issue is an independent unit of work in Multica - a bug, a new feature, a to-do. Each issue has a title, description (supports Markdown), status, priority, assignee, and optionally can be classified into a project. If you've used Linear or Jira, they're the same thing.
The biggest feature of Multica is that the assignee of an issue can be a person or an agent - this is the first thing to talk about below.
Assign the issue to the agent
Assigning an issue to an agent is equivalent to giving it the work. The agent will work automatically - starting execution within seconds, reporting progress in the comments, and changing the status to done when completed. The only difference from assigning work to colleagues is that it is not offline, does not need your reminder, and is available 7×24.
For details on the identity, configuration, and running location of the agent, see Agent.
For private agents, only the owner and admin of the workspace can be assigned to issues. For details on role permissions, see Members and Permissions.
Status
Multica offers seven states. Any status can be changed directly to any status - Multica does not impose a workflow and will not stop you just because you jump directly from backlog to done.
| Status | Meaning |
|---|---|
backlog |
Not scheduled yet |
todo |
Scheduled and ready to start |
in_progress |
Doing |
in_review |
Waiting for review |
done |
Completed |
blocked |
stuck by external factors |
cancelled |
Canceled |
After assigning the issue to the agent, the agent will automatically push the status from backlog / todo to in_progress, and push it to done after completion. You can also change it manually at any time.
priority
The priority is divided into five levels, which are used to arrange the issue list in the default order:
| Priority | Purpose |
|---|---|
No priority |
Not decided yet (default) |
Urgent |
Urgent |
High |
High |
Medium |
Medium |
Low |
Low |
Issue number
Each issue has a unique number in the workspace, the format is -, such as MUL-123. The number is automatically assigned by the system when it is created and never changes. See Workspace → Issue Number for details.
Comment
The comment area under Issue is where collaboration takes place - reply to a comment, @-click a celebrity or agent, and add emoticon reactions.
In the comments @ an agent will automatically trigger it to start - this is the second trigger method besides "assigned to". See Comments and Mentions and Summoning Agents in Comments for details.
delete issue
Deleting an issue will immediately clear all comments, emoticons, attachments, and queued agent tasks above it (the tasks being executed will be cancelled). Cannot be restored. If you just want to remove the issue from view, changing the status to
cancelledis safer than deleting it - the data is still there, and you can get it back later if you want.
Project
Project is a container that organizes multiple issues together. An issue can belong to at most one project, or it can belong to no project.
Project has its own person in charge (lead) - Like the issue's assignee, the lead can be a person or an agent.
Deleting a project will not delete the issues below it: these issues are just separated from the project and remain in the workspace.
Next step
- Comments & Mentions - Collaborate under issue
- Agents - Understand how "Assign to Agents" works