Projects

A project is the workspace’s work container: it groups issues, milestones, cycles, docs and templates, with an identity of its own (icon, color, lead and dates). Every issue lives in a project.

What it is

Projects live at the workspace level and can span the work of several teams. Each one has:

• Name, description (markdown), icon and color to identify it.
• A project status: backlog, planned, started, paused, completed or canceled.
• A lead (by default, whoever creates it).
• Start and target dates, which feed the Roadmap.

The «General» project

Every workspace is born with a General project that acts as the default home for issues. It’s identified by an internal flag (not by its name, so it survives renames). There’s only one per workspace.

If you don’t want it, you can archive or delete it like any other project. Without General (or with it archived) there’s no default home: every new issue has to be created in a specific project, and a workspace can end up with no projects at all. In that case the sidebar suggests creating the first one.

What it’s for

• Organize issues into containers with shared context.
• Plan with milestones (with progress) and Cycles.
• Document with project docs and standardize tasks with templates.
• See an executive panel per project (progress, date risk, upcoming milestones) and an activity feed.
• Export the project’s issues to CSV.

A project’s tabs

Each project opens in tabs, with keyboard shortcuts:

1. Overview: identity, progress panel, description, milestones and issues with no milestone. This is also where you generate the AI-written project report and the status updates (with an AI draft), and where time spent shows if you have time tracking.
2. Issues: the issue list filtered to the project; you create issues here, including from a template.
3. Board: the project’s Kanban view.
4. Cycles: the project’s cycles (Cycle 1, 2, 3…).
5. Versions: the milestones grouped into versions, each with its AI-written changelog.
6. Graph: the project’s issues and their relations drawn as a graph, to see at a glance what blocks what.
7. Docs: the project documentation in markdown.
8. Templates: the reusable issue templates.
9. Team: what each person closed each day, how much is in review and how each group of tasks is moving, with a date filter.

How to use it

• Create: from the sidebar, with the «+» button next to «Projects». It’s born in backlog status with you as lead; the rest of the fields are edited on its page.
• Pin: pinned projects rise to the top of the sidebar.
• Archive ≠ delete:
  • Archiving only hides it from the sidebar and pickers; it deletes nothing and is reversible (unarchive). It stays visible on the Projects page.
  • Deleting removes the project. By default, its issues aren’t lost: they move to the project you choose (General is preselected if it exists; optionally you can delete them too). If there’s no other project, they’re deleted with it. Its milestones, cycles, docs and templates are removed.

Rules worth knowing

• Every issue lives in a project: removing the project moves it to General, it’s never left orphaned; without General, you have to pick another one. Moving to another project resets its milestone.
• The General project doesn’t count toward your plan’s project limit (see Billing & plans).

Related: Issues · Cycles · Roadmap.