> 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/projekte/vorgaenge-zur-projektplanung-verwenden.md).
# Use tasks (formerly cases) for job planning
The use of tasks for job planning is a common use case among users of Die Agenturverwaltung and can be used for planning and controlling jobs.
{% hint style="info" %}
Would you like to learn more about tasks in general? Then follow [this link.](/die-agenturverwaltung-en/vorgaenge-1.md)
{% endhint %}
A common approach is to convert the line items of an estimate into tasks after it has been approved by the customer.
To do this, we navigate to the corresponding job of an estimate and open the "Tasks" tab (formerly Issues) in that job.
In this tab, tasks can now be created via the quick-entry form for tasks, which can be accessed via the New Task button. By creating the tasks directly in the job, the tasks are automatically associated with it.
> Depending on the granularity of the estimate line items, the items are either taken over 1:1 or broken down into sensible work packages for implementation at this step.
>
> What a sensible breakdown looks like depends on the type of job, the established way of working of the team, and the question of whether, in addition to Die Agenturverwaltung, another project management or issue-tracking tool is used.
To take dependencies between the individual work packages into account, the two date fields "Starts on" for the earliest start date and "Due on" for the latest end date can be used.
Once the tasks are created in the job, the "Tasks" tab can henceforth be used to control the work packages.
### Communication in jobs with comments
A lot of communication takes place during the execution of jobs. If there is a question or a remark in the context of a work package and it should not be lost in a chat or messenger thread, the comment function is suitable.
Comments can be added via the button in the task detail view. To read the comments we navigate to the "Comments and Activities" tab in the task detail view.
Whether and how many comments there are for a task is already visible on the task overview pages by the comment icon and the number inside it.
{% hint style="info" %}
**Reply to comments directly from the email program**\
All participants of a task (assignee and watchers) also receive comments by email and can reply to them directly from their email program without logging into Die Agenturverwaltung. The reply is then saved as a new comment and delivered again by email to all other participants.
{% endhint %}
### Watch tasks to keep an overview
Especially as a project manager it is necessary to keep an eye on the current degree of completion and adherence to milestones to ensure project success. A sensible way is to regularly watch the job tasks. This can be done either in the "Tasks" tab in the job or by me, as a user of Die Agenturverwaltung, watching all tasks that are relevant to me. You can learn how the watch function works in detail here:
{% content-ref url="/pages/16c18abe457fd753a2bff73ca51ee01effbf312a" %}
[Tasks I am watching](/die-agenturverwaltung-en/vorgaenge-1/vorgaenge-die-ich-beobachte.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 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://wiki.dieagenturverwaltung.de/die-agenturverwaltung-en/projektverwaltung-1/projekte/vorgaenge-zur-projektplanung-verwenden.md?ask=&goal=
```
`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.