What it does
A project groups related threads. It owns a ref prefix — a short code used to number every thread in it (e.g. PLAT-1, PLAT-2) — and a workflow: the ordered set of stages a thread passes through, such as Backlog → To Do → In Progress → In Review → Done.
Where to find it
Open a workspace from Structures (the Organisation structure), then create or open a project. A project board lives at /dashboard/projects/<id>.
Step by step
Create a project
- Open a workspace and click New project.
- Enter a name. Leave Prefix blank to have one generated (e.g. "Back-End" →
BE), or set your own (1–8 letters/numbers). - Choose a workflow and a visibility, then click Create project.
Use the board
- Open a project to see its Board view, with one column per workflow stage.
- Add work with New thread.
- Move a thread between stages from the ⋯ menu on its card, or from the thread page.
- Click the 🔗 link button in the header to copy the project's URL and share it with a teammate.
Edit project settings
- Owners and admins see a gear button in the project header. Click it to update the project's name,
description and colour, then Save changes.
What each screen shows
- Project card (in a workspace) — the ref prefix badge, open-thread count and total threads.
- Workspace roll-up — above the project grid, a compact summary shows the total open threads across the
workspace's active projects, with a clickable per-project chip (colour dot + open count) for each project that has open work.
- Project board — columns for each workflow stage, with thread cards you can move and open. A Board / List toggle switches the layout.
- Filter chips — above the board, rows of chips narrow what's shown: by tag, by assignee (plus
an Unassigned chip), and by priority (Urgent / High / Medium / Low, each with a count). The rows compose — pick a tag and a priority to see just that slice — and each row has its own Clear. When any filter is active, a single ✕ Clear all filters resets the tag, assignee and priority filters at once.
Tips
- Your team starts with a sensible Default workflow — you can attach it to every project.
- Moving a thread into the final (terminal) stage automatically marks it resolved.
- A sequential workflow only lets a thread move to the next or previous stage — this is enforced
everywhere (on the board and via the API), so work can't skip steps.
Troubleshooting
- Prefix already taken? Threadwork makes prefixes unique per team by appending a number — pick a distinct one if you'd rather.