Sub-projects
Split a project into sub-projects, for example one per application for the same client, and still see the client’s work in one place.
For owners and admins create and move them
A project can hold sub-projects. Use them when one client or piece of work splits into parts that each need their own tasks, board and GitHub repo, such as a web app and a mobile app for the same client. Each sub-project is a full project of its own, and its parent is where the whole family comes together.
Sub-projects go one level deep: a project is either a parent, a sub-project or a project on its own. A sub-project can’t hold sub-projects of its own.
What a sub-project keeps#
A sub-project works like any other project. It has its own:
- tasks, with keys from its own name;
- outcomes, list, board, Gantt and documents;
- GitHub repo, if you link one (see GitHub);
- support portal and settings.
The parent is a real project too. It can hold work that belongs to the whole client, such as meetings or invoicing, and its own outcomes.
Create a sub-project#
Owners and admins create sub-projects.
- Open the parent project. Under the header, choose + New sub-project.
- Give it a name and choose a type, then choose Create project.
You can also choose New project in the sidebar and pick the parent under Inside. Only projects that aren’t sub-projects themselves are offered.
Move a project into or out of a parent#
Owners and admins can move an existing project.
- Open the project and choose Settings, then General.
- Under Parent project, choose a parent under Inside, or Nothing (a top-level project) to take it out.
- Choose Move…, read what will change, then choose Move.
Moving changes only the grouping. The project’s tasks, keys, bookings, tickets, repo and settings stay as they are.
A project that has sub-projects can’t go inside another project. Its settings list its sub-projects instead.
A sub-project can’t move out of its parent while any of its tasks belong to one of the parent’s outcomes. Move those tasks off the outcome first.
Find your way around a family#
- The sidebar shows a parent with an arrow, and its sub-projects indented under it. Choose the arrow to show or hide them; the sidebar remembers your choice in this browser. With the keyboard, the arrow keys move through the list, and Right and Left open and close a parent.
- A sub-project’s pages start their breadcrumb with the parent’s name.
- A parent’s list, board and Gantt show a Sub-projects strip with each sub-project and how many open tasks it has. The parent’s screens show the whole family’s work (see below).
- The project filter on All work, Calendar, Roadmap, Reports and the support desk shows sub-projects under their parent. Ticking a parent ticks the whole family, and the button then says “(all)” after the parent’s name. A family that’s only partly ticked shows the parent’s box as mixed.
What a parent shows#
A parent’s List, Kanban and Gantt show its own work and all its sub-projects’ work together, so you can see the whole client at once.
- Each task and card from a sub-project carries the sub-project’s name, and a Gantt bar names it when you point at it. The parent’s own work has no label.
- Sub-projects in the toolbar narrows the view to one or more sub-projects. All of them shows the whole family again.
- On the list, choose Sub-project to group tasks by the project they’re in. On the board, Sub-project gives each sub-project its own swimlane, and on the Gantt it groups the bars the same way.
- Moving a card or dragging a bar works exactly as it does on the sub-project’s own board and Gantt, with the same schedule preview.
- Outcomes from the parent and its sub-projects are listed together. A parent’s outcome counts the tasks from every sub-project under it.
A sub-project’s own pages show only its own work.
Add work from a parent#
New task from a parent starts in the parent. If the task belongs to a sub-project, choose it under Project: it then gets that sub-project’s key, board and repo. Projects are listed as “Parent › Sub-project”. When you choose a sub-project, its parent’s outcomes are offered under Outcome too, marked with the parent’s name.
On a parent’s outcome, adding an existing task offers the tasks of every sub-project as well.
Across projects#
Wherever a screen names a task’s project, such as All work, My Work, the Roadmap, the Dashboard and the calendar’s New task, a sub-project is shown as “Parent › Sub-project”. All work lists a parent’s sub-projects straight after it.
In Reports, Throughput by project has Sub-projects in their parent, which adds each sub-project’s tasks to its parent’s total, so a client’s work reads as one figure.
Who sees a sub-project#
When you limit someone to some projects (see Choose who sees a project):
- Choosing a parent gives them all its sub-projects, including ones added later. The list shows them ticked with “(with its parent)”.
- You can choose a sub-project on its own. Then they see only that sub-project, as a project of its own. They don’t see the parent or its other sub-projects, and nothing tells them there is a parent.
A sub-project added to a parent reaches the people who have the parent within a few minutes.
Outcomes across a family#
A task in a sub-project can belong to one of its parent’s outcomes, so an outcome like “Launch v2” can hold work from every application. A task can’t belong to another sub-project’s outcome, or to any other project’s.
Teams#
A team whose focus projects include a parent covers its sub-projects’ work too. In a team’s focus list, ticking a parent shows its sub-projects ticked with “(with its parent)”. See Teams.
Repositories, support portals and the knowledge base#
- GitHub. Each sub-project links its own repository, and the parent can link one too. Issues, pull requests and AI workers on GitHub always use the repository of the task’s own project. See GitHub.
- Support portals stay per project: each sub-project can have its own portal, and a parent’s portal doesn’t take tickets for its sub-projects. Under Dev tasks go to in a portal’s settings you can send dev tasks to any project, such as a sibling sub-project.
- Knowledge base. A source for the parent is for its sub-projects too, including articles on a sub-project’s portal. A sub-project’s source is never used for its siblings. See Sources.
- Data sources for AI workers stay with the project they’re added to; a parent’s aren’t offered on its sub-projects’ tasks.
Archive and delete#
- Archiving a parent archives its sub-projects with it. If any sub-project still has its support portal on, the parent isn’t archived until that portal is turned off.
- A sub-project can’t be unarchived while its parent is archived. Unarchive the parent first.
- Unarchiving a parent from Archived projects asks whether to bring its sub-projects back too: choose With its sub-projects or Only and the parent’s name.
- Archived projects lists archived sub-projects under their parent.
- A parent can’t be deleted while it has sub-projects. Move them out or delete them first.
See Archive a project.
Plans#
Every sub-project counts as a project toward your plan’s limit on live projects, the same as any other project.