# Project View

A **project** is the primary way to organize tasks in Super Productivity. Every task belongs to exactly one project, making projects the main organizational structure for your work.

## What Projects Are

Projects are self-contained workspaces. Each project has:

- **Task lists** — Active tasks and an optional backlog
- **Notes** — Project-specific notes
- **Theme settings** — Custom colors and appearance
- **Integration settings** — Connections to external issue trackers (like Jira or GitHub)

When you switch to a project view, you see only the tasks that belong to that project, along with the project's notes and settings.

## Projects Vs Tags

Projects and tags serve different organizational purposes:

| Aspect                    | Projects                                                         | Tags                                                |
| ------------------------- | ---------------------------------------------------------------- | --------------------------------------------------- |
| **Relationship to tasks** | Each task belongs to exactly **one** project (required)          | Each task can have **zero or more** tags (optional) |
| **Purpose**               | Primary organizational structure — every task has a home project | Secondary labels for cross-cutting categorization   |
| **Features**              | Backlog, notes, theme, integrations                              | Simple labels for filtering and grouping            |

A task must always belong to a project. Tags are optional labels you can add to tasks across different projects to create cross-cutting categories.

## Project Features

**Backlog**: Projects can have a separate backlog list for tasks you're not actively working on. You can move tasks between the active list and the backlog.

**Notes**: Each project can have its own notes, separate from task notes.

**Theme**: Projects can have custom colors and appearance settings to help you visually distinguish them.

**Integrations**: Projects can connect to external issue trackers (like Jira, GitHub, GitLab) to sync tasks and track work.

## Organizing Projects

Projects themselves are **flat** — there are no parent projects or subprojects. A project cannot contain other projects.

However, you can **organize projects into folders** in the navigation menu. Folders can be nested (folders within folders) to create a hierarchy for navigation, but this is purely for organization — it doesn't change how projects work or how tasks are stored.

You can move projects between folders without affecting the tasks or any other project data.

## Hiding Projects

When a project is active but you do not want it in the sidebar project list, enable **Hide project from sidebar** in the project settings or use the Projects visibility menu in the sidebar.

Hiding a project changes navigation only. The project stays active, and its tasks can still appear in cross-project task views such as Today, Planner, Schedule, Boards, and Search. Project navigation helpers, including project short syntax, do not match hidden projects.

## How Tasks Belong to Projects

Every task has a project assignment. When you create a task, it's assigned to the current project (or the Inbox if you're in a tag context without a default project). You can change a task's project by:

- Dragging and dropping the task to another project in the navigation
- Editing the task and selecting a different project

When you view a project, you see all tasks that belong to it. When you view a tag, you see tasks from multiple projects that have that tag, and each task shows its project as a badge.

## Completing Projects

When you finish with a project, you **complete** it to retire it from your active workflow and celebrate the result. Right-click the project in the sidebar (or click the `⋮` button) and choose **Complete project**.

If the project still has **unfinished tasks**, you're asked what to do with them first: **Move to Inbox** (the default — they stay actionable), **Mark as done**, or **Cancel**. Before the project is completed, a final confirmation asks you to confirm the action.

On completion you get a full-screen **celebration** with a short summary — tasks done, time tracked, days worked, and how many days the project ran from its first worked day to completion (time-based stats are hidden when you don't track time).

A completed project becomes fully **dormant** — all its data is preserved, but it stops generating noise across the app. Specifically, it:

- Is removed from the sidebar project list and the main visibility checklist
- Has its tasks hidden from Today, Tags, Boards, Overdue, Deadline, and Scheduled views
- Has its repeating tasks suspended — no new instances are generated
- Has its reminders suppressed — no notifications fire for its tasks

**Finding and reopening** completed projects: click the eye icon in the Projects section header to open the visibility menu, then navigate to **Archived projects**, where completed projects appear with a trophy badge and their completion date. Use the **Reopen** action there to clear the completed state and bring the project back to the sidebar with all tasks, repeating configs, and reminders active again.

## Related

- [[4.02-Inbox-View]] — The default project for uncategorized tasks
- [[4.07-Tag-View]] — How tags provide cross-cutting categorization
- [[4.05-Board-View]] — Visual column-based organization
- [[4.01-The-Today-View]] — Today's task list
- [[4.03-Planner-View]] — Day-level planning across projects
- [[4.04-Schedule-View]] — Time-based scheduling