Product
Follow the work without a status meeting.
The board is the status report
Boards bring together screenshots, recorded test sessions, review notes and release pages. The project page adds tasks, sprints, milestones and progress summaries, so the team can follow work alongside its evidence. Browser controls, the CLI, MCP and the API provide different ways to work with that information.
You can manage tasks and write project pages in vitrinka without another tracker. If your team uses Jira, an administrator can configure a project task mirror through the API. Keep project documentation alongside the tasks and board evidence it describes.
What is in this tab
| Page | What it covers |
|---|---|
| Boards as the status report | How boards carry decisions and proof — annotations, statuses, the audited review judge, and how subgroups keep hundreds of boards findable. |
| Overview | The project's front door: what needs you, the sprint timeline, and the picked sprint's cockpit, readiness and tasks. |
| Product history | The current product snapshot and stable chapters with original versioned evidence. |
| The work loop | The task is the handoff — pickup, spot and hand back: one bounded view to start from, children filed the moment they are seen, one door that ends a session. |
| Tasks | The relational engine agents, the browser and the boards share — what a task carries, how work enters, moves and mirrors. |
| Views and filters | The project hubs and their displays, the one filter document behind them, saved views, and the task panel. |
| Intake | Proposals before tasks — the workspace Intake screen, drafts with a source and a dedupe verdict, accepted, declined or merged, and cleaning a backlog against reality. |
| Rules | Typed automation documents with a dry-run, and the eleven that ship enabled. |
| Sprints and milestones | Starting and completing sprints, carrying unfinished work, and the milestones tasks reference and todos wait on. |
| Projects | A project's settings — routing, repositories, custom fields, review rules — and merging or transferring a whole project. |
| Mirroring Jira | One mirror per project, one side the truth, conflicts settled and recorded. |
| Eve | The run view — where the project's AI lives, how you queue, steer and interrupt it, and how an organization chooses its AI. |
| The release flow | Rolling release notes, phased obligations, exact candidates, verified evidence and recorded shipments. |
| Brainstorming | Decision-led design: you answer batched multiple-choice in the brainstorm studio, the session ends in a decision log and a feature brief the build starts from. |
| Questions | Structured questions in the board's Questions panel, staged picks released together with ↑ send, and the durable answer record. |
Where you live
- The project page —
/p/<project>: Overview, History, Work, Plan and Record, with a task panel that preserves the selected view and scope. Intake is a workspace queue; Eve has its own conversation view. - The Work home —
/projects: every project with its hubs one click away, then your desk across projects: Waiting on you, In flight and the next seven days, with the same panel. The workspace home's All projects → leads there. Todos, reminders and your work time are on your day. - Intake —
/intake, the first row of the Work sidebar with its count: every draft and plan proposal of the workspace waiting for a verdict. - The board — the shared canvas where work, proof and questions appear; a task on it is a live projection of the engine, and clicking its state writes back.
- The module rail — Work · Boards · Library · QA; under Boards, boards fold into their project and subgroup (reviews, testing, sessions and the rest), so the board you need is two clicks away.