Project board

One board across every project: tickets, lists and epics for planning work, narrowed to the project you are in, linked to Progress and driven from the chat.

What it is

The board is one board for the whole machine, shared by every project. Lists of tickets, the level above a single plan: where an idea gets parked, where the week's emails and check-ins sit beside the features, and where tracked work shows up as a ticket that moves on its own.

Open it from the dock, press New ticket or N to type one into a list, or tell the chat what to park there. It is stored on this machine, outside any repository, so nothing about it is committed or shared.

Projects and the scope switch

A ticket belongs to one project or to none, never two. A ticket you create in a project is bound to it, and the Project row in the ticket's sheet moves it to another project or sets it to No project.

The switch beside the view buttons decides what you see. On your project's name it shows that project's tickets plus the unbound ones, which is where it starts whenever the board is open inside a project. On All projects it shows everything on the machine. The switch is a scope rather than a filter, so clearing the filters leaves it alone, and each window remembers its own: the board opened from one project and the board opened from another can be looking at different things at the same time.

A ticket bound somewhere else carries a small chip naming that project, so a card is never in doubt about where it lives. If the project has since been removed from PandaOS the chip reads Unknown project, and the sheet still lets you rebind it.

This is what lets one epic span repositories: an epic in this project can hold children bound to others, and its progress counts every child wherever it lives, whatever the switch is set to.

Lists

A new board starts with Backlog, To Do, In Progress, Done and Won't Do, plus an Archive that keeps finished work out of the way without deleting it. Rename, recolour and reorder the lists from the column menu, or add one at the end of the board.

What a list means lives on its role, not its name: renaming Done to Shipped changes nothing else, and "move #3 to done" from the chat still lands in it. Deleting a list asks where its tickets should go, and the last Done or Won't Do list cannot be deleted because epics and tracked work need one of each.

Tickets

A ticket has a number (#12), a title, a markdown description, a type, a priority, tags, a due date and attachments. Click a card to open its sheet and edit any of them; every change lands at once and in every window showing the board.

• Types and priorities are per project. Edit them from the settings icon in the header.
• Due dates turn amber the day before and red once overdue, on the card and in the Table view. Overdue tickets are counted on the dock badge.
• Checklists are ordinary markdown task items in the description. Tick them in the sheet without opening the editor; the card shows how many are done.
• Attachments are references, never copies: a link, a file or an image on this machine. Drop or paste a file onto the strip, choose one, or add a link. Images show a thumbnail; a click opens the file or the link.

Drag cards between lists and within one. On a narrow panel the lists become a switcher, and a card dropped on a segment moves to that list.

Epics

An epic is a ticket with a flag. Flag one from its sheet, or attach a ticket to it and it becomes one. Children carry the epic's chip, and the epic's card shows a bar of how many are done, in flight, or ruled out.

The Epics view lays one row per epic across the lists, with a No epic row for everything else. Drag a card into another row to move it under that epic. The epic's own sheet groups its children by list and lets you drag between the groups or add a child straight into one.

An epic's status is yours to set: when every child is done the card offers Move to Done, and nothing moves until you say so.

Tracked work

The board and Progress are linked both ways.

• Finalizing a plan of standard or epic size creates a ticket in To Do. The build stage moves it to In Progress, completing the work moves it to Done, and archiving the work moves it to Won't Do. Quick fixes create nothing.
• Move a linked ticket by hand and it stays where you put it; the automatic moves stop for that ticket.
• From any ticket, Start tracked work turns it into a plan in the chat beside the board. A linked ticket shows the plan's stage rail and opens Progress on it.

From the chat

The chat sees the board through three actions, on any engine, without a search.

Deleting asks first

A delete from the chat raises an approval card; a create, an update or a move does not. Turn Actions off for the Board under its settings to take the three actions away from the chat entirely.

Park something: the chat creates the ticket with a title and the context from the conversation, and answers with its number.

put this into my backlog

Change one: lists, types and priorities are named the way you name them, and an unknown name is refused with the names that exist rather than invented.

move 14 to in progress and tag it billing

Read it back: by list, tag, type, priority, epic or text, or one ticket with its full description.

what is in my backlog?

Show it: the panel opens, on a ticket or a view if you name one.

show me the board

Keyboard