How to use Trackbook to plan features, releases, and projects.
Getting started
Trackbook tracks the features you're building, the releases they ship in, and the projects they belong to.
Signing in. You'll be sent to the sign-in page; after signing in you land on the Features list.
Getting around. The top navigation switches between Features, Roadmap, Releases, and this Help page.
Who you are. Your name and the current build version appear in the footer. Sign out is in the top-right of the header.
Finding features
The Features page (the default view) lists every feature in a sortable table.
Search. Type in the search box to filter instantly. It matches across all fields — title, description, ROI, status, owner, project, and release.
Filter. Click Status and Project chips to narrow the list. You can select several of each; selecting none is the same as selecting all. Project chips are top-level projects and include their sub-projects.
Sort. Click a column heading to sort by it; click again to reverse. The arrow marks the active column.
Open. Click any row to open that feature.
The roadmap
The Roadmap shows upcoming (not-yet-shipped) releases and the features planned for each.
Use the List / Timeline toggle at the top.
The Timeline plots releases on a real date axis with month markers and a “today” line, so the spacing reflects actual timing. Click a release to reveal its features. Releases with no target date appear as chips beneath the axis.
Releases
The Releases page is the archive of shipped releases, newest first, with summary statistics (features shipped, cadence, and most recent ship date).
Working on a feature
Open a feature to see its details. The tabs — Description, ROI, Attachments, GitHub, Discussion — keep everything on one screen.
Edit in place. Click the title, Description, or ROI to edit. Press Enter (or click away) to save, Esc to cancel.
Sidebar fields — click any to change:
Status — Planned, TBD, In progress, Done, or Cancelled.
Owner — anyone in the directory; you can assign someone who hasn't signed into Trackbook yet.
Project — any project or sub-project, shown as a colored pill.
Target release — a release, or “No release”.
Attachments. Add files with the button or by dragging onto the panel; click a file to download, or ✕ to remove it.
GitHub. Link a pull request or issue by repository (owner/name) and number; its state is fetched and shown.
Discussion. Post comments; you can delete your own.
Delete. The Delete feature button in the sidebar asks you to confirm in a dialog first.
Creating features & releases
New feature (button on the Roadmap and the Features page): set a title, and optionally a description, ROI, status, project, and target release.
New release (button on the Roadmap): give it a version or label and an optional target date. Leave the date blank for a backlog-style release (for example, name it “Backlog”). Dated releases sort by date; undated ones sort last.
Projects
Projects group features and give them a color. They have two levels: top-level projects, and sub-projects beneath them.
Color is set on the top-level project; sub-projects inherit it. Features are tagged with a colored pill (the leaf name, in the top-level's color — hover for the full “Parent / Child” path).
Manage projects with the Projects button on the Roadmap:
Add a top-level project — it's given a distinct color you can change via its swatch.
Add a sub-project with + sub under a top-level project.
Rename by clicking a name; recolor a top-level via its swatch.
Remove with the ✕ button.
Default project. The Default project can't be deleted. When you delete a top-level project, its features — and its sub-projects' features — move to Default. When you delete a sub-project, its features move up to its parent.
Statuses
○Planned — scheduled work.
◇TBD — undecided or not yet triaged.
◐In progress — being worked on.
●Done — completed.
✕Cancelled — dropped.
Tips
Dialogs close only with their Cancel / Close button — an accidental click outside won't discard what you've typed.
The footer shows your name and the current build version (e.g. v12 (abc1234) · 2026-05-26) — handy when reporting an issue.