> 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/mobile-app/production-task-list/view.md).

# View

## Overview

The view option allows you to customize tasks in the production task list. Try all available options and choose the most convenient way for you to see the tasks of the entire production.&#x20;

After reading this article, learn more details about the view and learn how to customize the production task list to suit your needs.

### **Basics**

The Production Tasks List has **three view modes**:

1. **Hierarchy with components**
2. **Task group**
3. **Plane** (default option)

<figure><img src="/files/drBFytzI9doHQUQXl99N" alt="" width="282"><figcaption></figcaption></figure>

### **Plane**&#x20;

1. Open the **Production Task List** screen
2. Click on the **“More actions”** menu (three dots in the top-right corner)
3. Select **“Views”** from the dropdown menu
   1. The system opens the **“Viewing”** bottom sheet, displaying the currently selected view mode with a checkmark
4. On the **“Viewing”** bottom sheet, click on **“Plane”**
   1. The system closes the bottom sheet and updates the Production Task List screen
   2. Tasks are now displayed as a flat list, sorted according to the Task Sorting Rules

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

### **Hierarchy with components**

1. Open the **Production Task List** screen
2. Click on the **“More actions”** menu (three dots in the top-right corner)
3. Select **“Views”** from the dropdown menu
   1. The system opens the **“Viewing”** bottom sheet, displaying the currently selected view mode with a checkmark
4. On the **“Viewing”** bottom sheet, click on **“Hierarchy with Components”**
   1. The system closes the bottom sheet and updates the Production Task List screen
   2. Tasks are now displayed in a structured hierarchy with the following groups:
      * **Component Productions** – List of component cards showing:
        * Product Name
        * Variant
        * Configuration
        * Deadline Date
        * Production Status
        * Production Progress
      * **Additional Components Productions** – List of additional component cards with the same details as above
      * **Tasks** – General production tasks, sorted accordingly
      * **Additional Tasks** – Additional production tasks, sorted accordingly

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

### **Task group**

1. Open the **Production Task List** screen
2. Click on the **“More actions”** menu (three dots in the top-right corner)
3. Select **“Views”** from the dropdown menu
   1. The system opens the **“Viewing”** bottom sheet, displaying the currently selected view mode with a checkmark
4. On the **“Viewing”** bottom sheet, click on **“Task Group”**
   1. The system closes the bottom sheet and updates the Production Task List screen.
   2. Tasks are now displayed in the following groups:
      * **Tasks in Components** – List of tasks in production components, sorted according to the Task Sorting Rules
      * **Tasks in Additional Components** – Tasks in additional production components, sorted accordingly
      * **Tasks** – General production tasks, sorted accordingly
      * **Additional Tasks** – Additional tasks related to production, sorted accordingly

{% embed url="<https://app.arcade.software/share/9Si9RLbbbXq9Vju6XCT8>" %}

### Notes

* **Task Sorting Rules** are applied consistently across all views.
* The selected view mode remains active until the user changes it again.


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.hesh.app/manuals/mobile-app/production-task-list/view.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
