Updated
Issues
An issue is work to do with a status. A note says how something works and a log says what happened; an issue says what is left. Any AI connected through MCP can search, create and advance them, so the task Claude left yesterday can be picked up today by another AI.
Statuses and priorities
| Status | Meaning |
|---|---|
open |
Open |
in_progress |
In progress |
test |
In testing: done, needs checking that it works |
done |
Completed and verified |
Priorities: low, medium (default), high and critical. Listings return them ordered with critical and high first.
Rules for agents
The MCP server tells the AI how to work with them:
- Search before creating, to avoid duplicates.
- When starting work on one, set it to
in_progress; when finished, totest. - Do not set it to
doneunless you ask or it has verified it works (tests, verified deployment…), explaining how. - If it fails when tested, go back to
in_progress. - Record what was done in a log.
To pick up an issue in another session or with another AI, see the guide How to continue AI work in a new session.
Organize and share
Issues are grouped in folders and do not belong to any note; you link them with chips like $[issue:7:Migrate the database]. If a folder is shared, each status change is emailed to the people with access.