Projects
{"content":"The Projects workspace is where you keep delivery aligned: one place to see project health, ownership, and cross-links into plans, sprints, and tasks. Use it as your starting point before jumping into deeper task or planning flows.\n\n## Projects list\n\n{{\u003c thumbcard src=\"/images/ui/projects/projects-list.png\" alt=\"Projects list table with status, owners, and last updated\" caption=\"Projects workspace list\" \u003e}}\n\nThe list shows every project with the fields leaders use to keep delivery on track:\n- **Project + key:** canonical handle used across plans, tasks, and MCP commands.\n- **Status:** Planned / In Progress / Paused so you can spot stalled initiatives quickly.\n- **Owners:** who to page for decisions; add more in the project detail view.\n- **Updated:** quick freshness check before a standup or review.\n\n{{% steps %}}\n\n### Step 1 - Filter or sort\nUse the search box to find projects by name, owner, or status. This is the fastest way to jump to a single initiative during triage.\n\n### Step 2 - Open a project\nClick a row to open the detail view. This is where you'll see description, current state, related services, and tabs for sprints/tasks/metadata.\n\n### Step 3 - Add a project\nSelect **New Project** to create via MCP. Keep keys short and slug-friendly so they work in CLI and UI contexts.\n\n{{% /steps %}}\n\n\u003e [!TIP]\n\u003e Keep “Paused” projects to a minimum; if a project sits with an old updated date, assign an owner and move it to **In Progress** or archive it.\n\n## Project detail\n\n{{\u003c thumbcard src=\"/images/ui/projects/project-detail-overview.png\" alt=\"Project detail overview tab with description, status, owners, and related services\" caption=\"Project detail — Overview tab\" \u003e}}\n\nEvery project opens with tabs across the delivery lifecycle:\n- **Overview:** description, related services, current state bullets, and the status badge (click to change). Owners live here—keep at least one owner set.\n- **Planning:** links into planner artifacts for the project key.\n- **Sprints:** sprint cadence and current/previous sprint snapshots.\n- **Tasks:** project-scoped backlog entry point (UI work noted below).\n- **Collaboration:** contacts and coordination notes.\n- **Metadata:** project key, handles, and integration fields.\n- **Audit / Docs:** change history and references to supporting docs.\n\n### Tasks tab (in progress)\n\n{{\u003c thumbcard src=\"/images/ui/projects/project-detail-tasks-tab.png\" alt=\"Tasks tab showing work in progress notice and link back to tasks view\" caption=\"Tasks tab — current state\" \u003e}}\n\nThe Tasks tab currently routes you to the global Tasks view while inline creation/editor work (UI-007 / UI-012) lands. Use it to keep context but do edits in Tasks until the inline experience ships.\n\n## Navigation tips\n\n- Use the breadcrumb (`PROJECTS`) to return to the list without losing filter context.\n- Tabs deep-link (e.g., `?tab=tasks`) so you can bookmark specific views.\n- Keep descriptions concise and service references current; they’re used by MCP for quick lookups.\n\n## Next steps\n\n- Pair this view with the [Dashboard](/valdr/docs/ui/dashboard/) to identify projects that need attention.\n- Use [Tasks](/valdr/docs/ui/tasks/) to assign work before moving a project to **In Progress**.","description":"Browse and inspect projects, keys, and status.","title":"Projects"}
The Projects workspace is where you keep delivery aligned: one place to see project health, ownership, and cross-links into plans, sprints, and tasks. Use it as your starting point before jumping into deeper task or planning flows.
Projects list
Projects workspace list
The list shows every project with the fields leaders use to keep delivery on track:
- Project + key: canonical handle used across plans, tasks, and MCP commands.
- Status: Planned / In Progress / Paused so you can spot stalled initiatives quickly.
- Owners: who to page for decisions; add more in the project detail view.
- Updated: quick freshness check before a standup or review.
Step 1 - Filter or sort
Use the search box to find projects by name, owner, or status. This is the fastest way to jump to a single initiative during triage.
Step 2 - Open a project
Click a row to open the detail view. This is where you’ll see description, current state, related services, and tabs for sprints/tasks/metadata.
Step 3 - Add a project
Select New Project to create via MCP. Keep keys short and slug-friendly so they work in CLI and UI contexts.
Tip
Keep “Paused” projects to a minimum; if a project sits with an old updated date, assign an owner and move it to In Progress or archive it.
Project detail
Project detail — Overview tab
Every project opens with tabs across the delivery lifecycle:
- Overview: description, related services, current state bullets, and the status badge (click to change). Owners live here—keep at least one owner set.
- Planning: links into planner artifacts for the project key.
- Sprints: sprint cadence and current/previous sprint snapshots.
- Tasks: project-scoped backlog entry point (UI work noted below).
- Collaboration: contacts and coordination notes.
- Metadata: project key, handles, and integration fields.
- Audit / Docs: change history and references to supporting docs.
Tasks tab (in progress)
Tasks tab — current state
The Tasks tab currently routes you to the global Tasks view while inline creation/editor work (UI-007 / UI-012) lands. Use it to keep context but do edits in Tasks until the inline experience ships.
Navigation tips
- Use the breadcrumb (
PROJECTS) to return to the list without losing filter context. - Tabs deep-link (e.g.,
?tab=tasks) so you can bookmark specific views. - Keep descriptions concise and service references current; they’re used by MCP for quick lookups.