> 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/production.md).

# Production

- [Production page](https://docs.hesh.app/manuals/production/production-page.md)
- ["Info" pop-up](https://docs.hesh.app/manuals/production/production-page/info-pop-up.md)
- [Production page view options](https://docs.hesh.app/manuals/production/production-page/production-page-view-options.md)
- [Searching, sorting and filtering productions](https://docs.hesh.app/manuals/production/searching-sorting-and-filtering-productions.md): This section covers how to use filters and sorting to easily find the production items you need.
- [Launching productions](https://docs.hesh.app/manuals/production/launching-productions.md)
- [Bulk actions with productions](https://docs.hesh.app/manuals/production/bulk-actions-with-productions.md)
- [Production management](https://docs.hesh.app/manuals/production/production-management.md)
- [Statuses](https://docs.hesh.app/manuals/production/production-management/statuses.md): This page lists all the statuses of the production item and explains how to update the status
- [Progress bar](https://docs.hesh.app/manuals/production/production-management/progress-bar.md): How to understand the overall progress of the product's production cycle
- [Production details editing](https://docs.hesh.app/manuals/production/production-management/production-details-editing.md): This article offers detailed instructions on how to edit key production attributes, including order, product and time details
- [Components management](https://docs.hesh.app/manuals/production/production-management/components-management.md): This page offers a thorough overview of the "Manage Components" feature and provides detailed guidance on managing ongoing production cycles.
- [Tags](https://docs.hesh.app/manuals/production/production-management/tags.md): This page covers how to use tags to organize productions
- [Warnings](https://docs.hesh.app/manuals/production/production-management/warnings.md): This page provides a comprehensive overview of all issue types and offers detailed guidance on how to resolve them
- [Production workflow](https://docs.hesh.app/manuals/production/production-workflow.md)
- [Canvas](https://docs.hesh.app/manuals/production/production-workflow/canvas.md)
- [Task management on canvas](https://docs.hesh.app/manuals/production/production-workflow/task-management-on-canvas.md)
- [Task](https://docs.hesh.app/manuals/production/production-workflow/task.md)
- ["Related tasks" section](https://docs.hesh.app/manuals/production/production-workflow/task/related-tasks-section.md)
- ["Time tracking" section](https://docs.hesh.app/manuals/production/production-workflow/task/time-tracking-section.md)
- ["Performers" section](https://docs.hesh.app/manuals/production/production-workflow/task/performers-section.md)
- ["Rewards" section](https://docs.hesh.app/manuals/production/production-workflow/task/rewards-section.md)
- [Quality control](https://docs.hesh.app/manuals/production/quality-control.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hesh.app/manuals/production.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
