> For the complete documentation index, see [llms.txt](https://docs.hesh.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hesh.app/manuals/task-table/view.md).

# View

## Overview

The Tasks page is designed to customise the display of tasks to ensure effective management and analysis. 

Tasks can be grouped by **orders, productions, products,** or **performers**, depending on the selected view. Switching between different views makes it possible to adapt the page to the user's needs, simplifying workflows. The information is presented in such a way that it is convenient to find the necessary tasks, analyse data, and manage their implementation. 

This article describes the functions of changing the appearance of the tasks page, grouping by various criteria, and applying sorting to quickly access important information.

<figure><img src="/files/gox0VJ5gWbGZNpN1sKSQ" alt=""><figcaption></figcaption></figure>

## Basics

The tasks page has a customisable view that allows you to adapt the display of tasks for convenience and optimisation. Users can change the Tasks page view using the **View** drop-down.

#### Available views:

* **Default** - tasks are displayed as a regular table and organised by *task status* (more urgent → less urgent ⬆️), *task priority* (highest first ⬇️), *due date* (earliest first ⬆️), and *production deadline* (earliest first ⬆️)
* **Order** - tasks are grouped by order number.
* **Root production name** - tasks are grouped by root production name.
* **Product** - tasks are grouped by product ID.
* **Product + Configuration + Variant** - tasks are grouped using a combined key:
  * product ID;
  * configuration name;
  * variant name.
* **Assignee** - tasks are grouped by assigned user.

{% hint style="info" %}
The system remembers the selected view when the user refreshes or reopens the page.
{% endhint %}

## Grouped views

The Tasks page supports grouped views that help organise tasks by different business entities. Grouping allows users to quickly navigate large amounts of data, analyse workload, and focus on related tasks.

To change the task view:

1. Open the Tasks page.
2. Click the “**Page view**” button on the top panel.
3. Select the required grouping option from the drop-down list.

Depending on the selected view, the system automatically groups tasks into collapsible sections.

{% @arcade/embed flowId="LY3YfJv2TGC1paBj9WxU" url="<https://app.arcade.software/share/LY3YfJv2TGC1paBj9WxU>" %}

### Assignee view

In this view, tasks are grouped by assigned users.

Additional behaviour:

* tasks without assigned performers appear in the “**Unassigned**” group;
* tasks with multiple assigned users may appear in multiple groups.

Each group header displays performer information, including profile photo and user name.

<figure><img src="/files/G1MSoJRUeoay3GiIK1iM" alt=""><figcaption></figcaption></figure>

### Order view

In this view, tasks are grouped by order. Each group contains tasks related to the same order.

The collapsed group header may display:

* Order name
* External order number
* Marketplace order number
* Client information

<figure><img src="/files/4vwVH2xB51oNWmC3jv4i" alt=""><figcaption></figcaption></figure>

### Root production name view

This view groups tasks by root production.

Groups may include:

* tasks from the main production;
* tasks from nested productions;
* tasks from sub-nested productions.

This structure helps users understand the full production hierarchy and related workflow.

<figure><img src="/files/b75FqCwY4rGykJfby1lw" alt=""><figcaption></figcaption></figure>

### Product (only) view

In this view, tasks are grouped only by product.

Each group contains tasks directly related to the selected product without including nested production components.

<figure><img src="/files/IKzvagZ3ZkHAxW8yMjQG" alt=""><figcaption></figcaption></figure>

### Product (with details) view

This view groups tasks using a combination of:

* Product
* Configuration
* Variant

Each group represents a unique product setup and helps separate similar products with different configurations or variants.

<figure><img src="/files/TodLioJXYTlBL72kFhiw" alt=""><figcaption></figcaption></figure>

## Additional features in grouped views

Grouped views include additional tools that help users navigate, filter, and manage tasks more efficiently.

### Counters

Grouped views display counters that help analyse the current dataset.

* **Tasks counter** - displays the total number of tasks currently visible according to applied filters.
* **Groups counter** - displays the total number of currently visible groups for the selected grouping type.

Both counters update automatically when:

* filters are applied or removed;
* grouping changes;
* task results change.

<figure><img src="/files/4Qa7SWqZVdqMk2oU4G0O" alt="" width="563"><figcaption></figcaption></figure>

### Filtering in grouped views

Each grouped view has its own filter based on the selected grouping type.

For example:

* Assignee view → Assignee filter
* Product view → Product filter

<figure><img src="/files/Av9zCzfSdNYFwZol3l4u" alt=""><figcaption></figcaption></figure>

### Group sorting

You can organize groups in ascending or descending order depending on the selected grouping type.

Available sorting options may include:

* **Order view** - tasks can be sorted by:
  * order key (A → Z / Z → A);
  * order deadline (earliest first / latest first);
  * start date (earliest first / latest first).
* **Root production name view** - tasks can be sorted by root production name (A → Z / Z → A).
* **Product view** - tasks can be sorted by product name (A → Z / Z → A).
* **Product + Configuration + Variant view** - tasks can be sorted by:
  * product name (A → Z / Z → A);
  * configuration name (A → Z / Z → A);
  * variant name (A → Z / Z → A).
* **Assignee view** - tasks can be sorted by user's name (A → Z / Z → A).

Sorting is applied only to groups order and does not affect task sorting inside the groups.

<figure><img src="/files/6h2cjXtxEcJUYJESH7ih" alt=""><figcaption></figcaption></figure>

### Bulk selection in grouped views

Grouped views support bulk task selection.

Users can:

* select all tasks inside a group;
* deselect all tasks inside a group;
* use partial selection states for groups with partially selected tasks.

{% hint style="info" %}
Bulk selection is available only for expanded groups.
{% endhint %}

## Task display range

Users can configure how completed and cancelled tasks are displayed.

Available time ranges:

* 1 day;
* 3 days;
* 7 days;
* 30 days;
* 90 days.

{% hint style="warning" %}
Completed or cancelled tasks with deadlines outside the selected time range will be excluded from the list.
{% endhint %}

#### To change tasks display range:

1. Open the task page .
2. On the top panel of the tabs, find and click the “**Page view**” button.
3. Configure the range of tasks to be displayed (available options: 1 day, 3 days, 7 days, 30 days, 90 days).
4. The system automatically hides all completed (**Done**) and cancelled (**Cancelled**) tasks.
5. If tasks are completed or cancelled within the selected time range, they will be displayed in the list
6. To view details of the selected settings, hover over the ℹ️ Information icon

<figure><img src="/files/IKrimJhuXQD58uLrWLmG" alt=""><figcaption></figcaption></figure>

These steps allow you to optimize the display of tasks according to your current needs and focus on the tasks that matter most.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.hesh.app/manuals/task-table/view.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.