Issues and projects
Statica's core unit of work — assignable to a person or to an agent.
An issue is a self-contained piece of work in Statica. It has a title, a description (Markdown supported), a status, a priority, an assignee, and may optionally belong to a project. If you've used Linear, Jira, or GitHub Issues, the shape will feel familiar.
What's different about Statica is that the assignee can be a person or an agent — which is the most important thing to understand first.
Assigning an issue to an agent
When you assign an issue to an agent, the work is handed over immediately. The agent starts on its own, usually within a few seconds — it picks up the description, executes against your runtime, posts progress as comments, and moves the status to done when it's finished.
The experience is almost identical to handing work to a teammate. The differences are that the agent doesn't sleep, doesn't need a nudge, and is available around the clock.
Private agents are restricted to workspace owners and admins. Role permissions are described in Members and roles.
Status
Statica ships with seven statuses. Any status can transition directly to any other — there is no enforced workflow, so jumping straight from backlog to done is allowed if that's what you actually want.
| Status | Meaning |
|---|---|
backlog | Not scheduled yet |
todo | Scheduled and ready to start |
in_progress | Currently being worked on |
in_review | Awaiting review |
done | Completed |
blocked | Stuck on something external |
cancelled | No longer being worked on |
Once an agent takes an issue, it will move the status from backlog or todo to in_progress automatically, then to done on completion. You can override the status manually at any time.
Priority
Priority has five levels and drives the default ordering of the issue list.
| Priority | Use |
|---|---|
No priority | Default — not yet decided |
Urgent | Drop everything |
High | Important, do soon |
Medium | Normal |
Low | When there's time |
Issue numbers
Every issue is given a workspace-unique identifier in the form <prefix>-<number> — e.g. STA-128. The identifier is assigned on creation and never changes, even if the issue moves between projects.
Deleting an issue
Deleting an issue is immediate and irreversible. Every comment, reaction, and attachment is removed, and any queued agent tasks are dropped (running tasks are cancelled).
If you just want the issue off your list, setting the status to cancelled is safer — the history stays, and you can resurrect it later.
Projects
A project groups related issues together. Each issue belongs to at most one project, or to no project at all.
Projects have a lead, and — just like an issue's assignee — that lead can be a person or an agent.
Deleting a project does not delete its issues. They detach from the project and remain in the workspace.
Next
- Comments and mentions — collaborating under an issue
- Agents — what "assign to an agent" really does under the hood
Comments
The comment thread under an issue is where collaboration happens. Reply, react, or
@a teammate or agent.@-mentioning an agent starts it automatically — this is the second way to kick off an agent, alongside assigning the issue. See Comments and mentions.