Managing tasks

Tasks in belsimple are organised as a tree (or more precisely, a forest — multiple root tasks are allowed). Every user can create tasks, but as a manager you’ll typically set up the initial structure.

Creating tasks

1. Go to the Tasks page.
2. Click New task.
3. Enter a title and optional description.
4. Optionally select a parent task to nest it under.
5. Click Save.

The task tree

Tasks can be nested to any depth. For example:

Project Alpha
  ├── Work package 1
  │   ├── Literature review
  │   └── Experimental setup
  └── Work package 2
      └── Data analysis

Team members can log time against any task in the tree, whether it’s a top-level project or a leaf task.

Task time totals

Any team member — manager or employee — can view the aggregated time logged against a task by clicking the Time totals (clock) icon on a task row. The dialog shows a breakdown of hours by team member; click Compute to populate the results.

By default, it shows only the time logged directly against that specific task. You can toggle Include subtasks to see the aggregated total for the task and all of its descendants, giving you a complete picture of the work package or project. You can also filter the totals by date range.

Reassigning time entries

If time was accidentally logged against the wrong task, you can bulk-move those entries.

1. Select the task that currently holds the entries.
2. Click the Reassign time entries (arrows) icon.
3. Choose the target task where the entries should be moved.
4. Optionally specify a date range to only move entries within a certain period.
5. Confirm the reassignment.

The target must be a different, active task — to reassign into an archived task, unarchive it first.

This action updates the task association for all matching historical entries and is permanently recorded in the audit log.

Re-parenting tasks

To move a task under a different parent:

1. Select the task in the tree.
2. Click the up-down arrow icon (↕) to move it.
3. Choose the new parent (or move it to the root level).

The system prevents circular references — you can’t move a task under one of its own descendants. You also can’t move a task under an archived parent; unarchive the target parent first.

Archiving and unarchiving

• Archive a task when it’s no longer active. Archiving cascades to all descendants (you’ll be asked to confirm).
• Unarchive a task to make it active again. Unarchiving cascades up to all ancestors, because a child can’t be active while its parent is archived.
• Archived tasks are hidden by default but can be shown.
• Archiving doesn’t delete data — existing time entries against archived tasks are retained.