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 tickets

Types

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.

TypeMarkParentWhat it holds
common.ticketlucide:ticketcore.taskGroups the kinds: work someone wants done, or a question they want answered. Ask for it to read every ticket at once.
common.ticket.epiclucide:flagcommon.ticketAn outcome that needs several tickets, completed when it's reached.
common.ticket.featurelucide:sparklescommon.ticketA change people using a product or service would notice.
common.ticket.spikelucide:flask-conicalcommon.ticketA question to answer before deciding or building. description holds the question and body the answer.
common.ticket.tasklucide:wrenchcommon.ticketOther 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:

WordGroupMeaning
backlognot_startedWanted, but not yet committed to.

Edges

Edge typeFromToMeaning
parent-ofAn epicEach of its ticketsRead 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-fromA ticketWhat it was made fromSuch as a note, a message, or the spike that led to it.

On this page