Task bundles
Overview
A task bundle is a reusable kit loaded into an existing project. It brings lists, hierarchy, dependencies and relative dates with it.
The difference from a project template is the moment: a template creates a new project, a bundle adds to a running one. That is the more frequent case — "we still need the sign-off stretch" or "this time there is a migration as well".
Core tasks
Create a bundle. New bundle requires a name; description and brand are optional. The list shows bundle, brand, content as a count of lists and tasks, and the active state. Left empty, the brand makes the bundle apply everywhere.
Think of ownership as a role. Ownership within a bundle is a project role, not a name. It resolves against the target project's members only when the bundle is loaded.
That is why a bundle is reusable at all: a bundle with fixed people in it would be waste paper after the first change of staff.
Lists of the same name are reused. If a list of the same name already exists in the target project, the tasks go into it rather than creating a second list with the same name. Loading the same bundle twice therefore produces no duplicate lists.
Fields in detail
The What it does column answers what changes in the system — not what the field is called. The grey name behind the label is the API field: the same thing runs under that name through automation, import and AI tools.
Task bundle
A bundle is a recurring sequence of tasks inserted into an existing project as a whole — unlike the project template, which creates a new project.
| Field | Required | Values / format | What it does |
|---|---|---|---|
Name name | yes | text, max. 255 characters | The name the bundle is offered under when inserting. |
Description description | no | text | What the bundle is for. |
Lists lists | no | list of lists | The lists created along with it if the project does not have them yet. |
Tasks tasks | no | list of tasks | The content: title, list, priority, estimate and the offset from the reference date. |
Brand brandId | no | one of your brands | Limits the bundle to one brand. |
Active active | no | yes/no | Off means it can no longer be inserted. |
On insertion
| Field | Values / format | What it does |
|---|---|---|
Project projectUlid | an existing project | Where the bundle is inserted. |
Reference date referenceDate | date | The zero point the tasks' due dates are calculated from. This is exactly why the bundle stores offsets and not fixed dates — the same bundle then fits any date. |
Settings & permissions
- Module
module.projects. - Permission
projects.config.manageto maintain bundles; loading one into a project requires the
permission on that project.
- Relative dates are calculated against the target project on loading.
- Deactivate rather than delete — tasks already loaded are untouched.
FAQ & troubleshooting
After loading, nobody owns the tasks. Then the target project has no member in the project role the bundle resolves against. Complete the team and assign the tasks.
Duplicate lists appeared. Reuse happens on an identical name. Even a different spelling creates a second list.
The bundle does not appear for selection. Check the active state and the brand.
I want to prepare a whole project, not just tasks. Then the project template is the right tool — it additionally brings milestones and budget.