Tickets
The common types the Tickets plugin adds, to track work and questions from backlog to done, with epics, features, spikes and tasks.
Tickets is a plugin WithMarfa publishes in withmarfa/plugins, with the mark lucide:ticket. It needs Marfa 0.0.92 or later.
marfa plugins install ticketsTypes
Each type comes with guidance an agent reads before it writes one. Write a ticket as one of the four kinds, never as a plain common.ticket.
| Type | Mark | Parent | What it holds |
|---|---|---|---|
common.ticket | lucide:ticket | core.task | Groups the kinds: work someone wants done, or a question they want answered. Ask for it to read every ticket at once. |
common.ticket.epic | lucide:flag | common.ticket | An outcome that needs several tickets, completed when it's reached. |
common.ticket.feature | lucide:sparkles | common.ticket | A change people using a product or service would notice. |
common.ticket.spike | lucide:flask-conical | common.ticket | A question to answer before deciding or building. description holds the question and body the answer. |
common.ticket.task | lucide:wrench | common.ticket | Other work, such as upkeep, setup, cleanup or a fix. |
Fields
A ticket has the fields of Task and adds none: title, description (the line a board shows), body, status, priority, assignees, due_at, starts_at, completed_at, place, precision, url, notes and recurrence.
status takes one word more than a task's:
| Word | Group | Meaning |
|---|---|---|
backlog | not_started | Wanted, but not yet committed to. |
Edges
| Edge type | From | To | Meaning |
|---|---|---|---|
parent-of | An epic | Each of its tickets | Read from a ticket as child-of. A ticket has at most one parent, and moving an epic to the bin moves its tickets too. |
derived-from | A ticket | What it was made from | Such as a note, a message, or the spike that led to it. |