Task groups – or task containers – are to tasks what roles are to user actions: they group tasks together into a single logical unit, allowing the application to treat the container as a proxy for all the tasks that are linked to it. Instead of manipulating the tasks one by one, containers can be leveraged to achieve the same thing in bulk.
This concept is put into action in the open tasks grid and affects the map and planning board.
When tasks (across jobs) are selected in the open tasks grid, they will be processed by the map component.
If the task is backed by a geocoded job, a pin will be added to the map. When a task is connected to other tasks through one of its containers, the linked tasks will be embedded automatically on the map. Users that require the map to plan trips for their resources will benefit from this feature in a major way. It is easy to see how much easier it is to determine the most efficient route when all related tasks are put on the map immediately. Automated mechanisms like this will reduce human errors and will reduce the time of planning as well.
Assuming a task container is defined and tasks are assigned to it, planning a task – by dragging it on the planning board - will automatically plan all the other tasks that belong to the same container. This makes a lot of sense in industries such as the logistics industry. For example, when you need to plan a task which corresponds to loading a lorry, chances are the next step will be to schedule the unloading task at the customer's site.