> For the complete documentation index, see [llms.txt](https://wiki.dieagenturverwaltung.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.dieagenturverwaltung.de/die-agenturverwaltung-en/projektverwaltung-1/vorgaenge-1.md).

# Tasks (formerly cases)

### UPDATE OF JOBS/ TASKS

We have rolled out an extensive update. In it, Vorgänge were renamed to Aufgaben, restructured, redesigned and, among other things, our new Kanban boards were introduced. The following video covers all changes:&#x20;

{% embed url="<https://www.loom.com/share/5885e17460794756bff537b93ed0b3e0>" %}

Our tasks can be assigned deadlines and comments. They can be used both for the **organization of one's own workday** as well as in jobs for the **organization of a team** to be used.&#x20;

Tasks also serve to break a job into substeps and can thus be used for job planning. For this they offer the possibility to store start times, due dates and a planned duration for each task.&#x20;

From a task list a timing or a status list can easily be generated.&#x20;

The weekly overview also allows capacity planning for the entire team at a glance.

With the boards (Kanban boards) tasks can be clearly structured and quickly moved.

The individual views and use cases are discussed in detail on the respective subpages. Have fun exploring!

{% content-ref url="/pages/305e1e926119f0a9efc3653e6240d9aa92e00499" %}
[My tasks](https://wiki.dieagenturverwaltung.de/die-agenturverwaltung-en/projektverwaltung-1/vorgaenge-1/meine-vorgaenge.md)
{% endcontent-ref %}

{% content-ref url="/pages/16c18abe457fd753a2bff73ca51ee01effbf312a" %}
[Tasks I am following](https://wiki.dieagenturverwaltung.de/die-agenturverwaltung-en/projektverwaltung-1/vorgaenge-1/vorgaenge-die-ich-beobachte.md)
{% endcontent-ref %}

{% content-ref url="/pages/b903732904ae2fcd34381100bd72dccaa629eae0" %}
[Weekly view of tasks](https://wiki.dieagenturverwaltung.de/die-agenturverwaltung-en/projektverwaltung-1/vorgaenge-1/wochenansicht-der-vorgaenge.md)
{% endcontent-ref %}

{% content-ref url="/pages/158eed926bb4998709cc35ed0a887933ea4560d3" %}
[Task boards](https://wiki.dieagenturverwaltung.de/die-agenturverwaltung-en/projektverwaltung-1/vorgaenge-1/task-boards.md)
{% endcontent-ref %}

### Reply to comments in tasks via e-mail

In every task any user can leave comments. The person responsible and all watchers of the task receive an e-mail when a new comment has been added to a task. The respective user can also **easily reply from their e-mail program**, the reply will then be saved in the task as a new comment and the person responsible as well as all watchers of the task will in turn be notified of the new comment by e-mail.

### Further information

Tasks are an important tool for job planning and execution. How you use them for job planning can be found here:

{% content-ref url="/pages/6cd4ab56074787e2071e385149404a825db3152b" %}
[Use tasks (formerly cases) for job planning](https://wiki.dieagenturverwaltung.de/die-agenturverwaltung-en/projektverwaltung-1/projekte/vorgaenge-zur-projektplanung-verwenden.md)
{% endcontent-ref %}


---

# 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://wiki.dieagenturverwaltung.de/die-agenturverwaltung-en/projektverwaltung-1/vorgaenge-1.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.
