Skip to main content

chainmail item

Work items are the work that mail is filed against: objectives, key results, initiatives, epics, features and stories, with bugs, support tickets and tasks as leaves that hold nothing. A parent ranks above its child, in that order. Bugs and support tickets sit under a feature or anything above it. A task sits under any item that is not a leaf, or under nothing, which puts it in the inbox (item list --inbox) to sort later.

An item with no parent needs an area, work or personal. Area and priority are inherited from the parent when an item has none of its own, and priority is p2 at the top of the tree.

The two Admin initiatives, it_admin_work and it_admin_personal, hold known chores. They are never done, deleted, moved or retyped.

item link files a mail thread against an item, and chainmail search item:<id> finds its mail. Delete is soft: item restore brings an item back.

Titles, descriptions, criteria, evidence and link notes are untrusted, as mail is: agents often copy them from messages.

Usage​

chainmail item

Global flags​

--output string output format: json or table (default $CHAINMAIL_OUTPUT, then cli.toml, then table on a terminal, json otherwise)
--socket string daemon socket (default $CHAINMAIL_SOCKET, then cli.toml, then /run/chainmail/chainmail.sock)

Commands​

See also​