Task bundles (from a template)

A task bundle is a reusable set of tasks — for example “Winterization” — that groups several task definitions together. Applying a bundle to one plant creates all of its tasks at once, as drafts. So a recurring to-do list need not be entered by hand over and over.

A bundle is not a separate module — it creates ordinary diary tasks

The applied tasks are ordinary diary tasks, just created in bulk. The bundle is a template; it has no status of its own and no site — the “where it came from” stays the diary task.

Before you start

• Permission: the task-issuing right — task:issue. The same right as issuing a single task.
• Where to find it: the Tasks tab in the management area (shift-log), in the Bundles panel.

Steps

1. Open the Tasks tab, and in the Bundles panel click + New bundle.
2. Give it a name (e.g. Winterization) and an optional description, then Create bundle.
3. Open the bundle (Edit bundle) and use Add task to enter its items — title, kind (one-time / recurring / scheduled), frequency, priority, target shift, category.
4. When ready, click Apply and choose the plant the bundle should target.
5. Confirm: Apply bundle. Every task in the bundle is created as a draft for the chosen plant.

You still have to ACTIVATE the drafts

Applying does not activate — the created tasks are inactive (drafts). Until you activate them, they do not roll into the diary. Activate them in the Tasks table, one by one or in bulk (this also needs task:issue). This is deliberate: you review the bulk-created items before they go live.

If it worked

The action states the actual result: “‘Winterization’ applied: 3 draft tasks created.” The tasks appear in the Tasks table marked Not activated, and also show in the common Tasks view.

Common problems

What you see	Why	What to do
“Empty bundle — add a task in the editor first”	The bundle has no items yet.	Open the editor and add at least one task.
The tasks do not show in the diary	The bundle creates drafts — they must be activated.	Activate the drafts in the Tasks table.
No “Bundles” panel / “+ New bundle”	You do not have task:issue.	Ask your admin — without it you cannot create a bundle.
Applied to the wrong plant	You chose the wrong plant when applying.	Delete/deactivate the wrong drafts and apply again to the right plant.

Worth knowing

• The bundle is tenant-wide, the application is plant-level. The bundle itself is a template available across every site/plant; the tasks created from it belong to one specific plant.
• Archiving is not deleting. If you archive a bundle it leaves the list, but the tasks previously created from it are kept.
• Applying is one step, all-or-nothing. Every item in the bundle is created in a single transaction — either all of them, or none.

Related

Issue a taskIssuing a single task by hand — the bundle multiplies this.

The common Tasks viewWhere you also track the tasks created from a bundle.