> 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/wochenansicht-der-vorgaenge.md).

# Weekly view of tasks

Die Agenturverwaltung weekly view is used for the **capacity planning** for a team or the entire Die Agenturverwaltung. It provides a quick overview of employees' workload and makes it possible to move tasks quickly and easily if free times or overloads become apparent.\
Creating new tasks for a specific user on a selected day is also possible in a few steps.

You can reach the weekly view via the navigation by clicking "Weekly view" in the main menu item "Tasks".

The weekly view shows - as its name suggests - only the tasks *of a* week, whereby the desired period can be selected via the week filter at the top left.

Each row represents an employee/user. This selection can also be restricted via a filter at the top right ("Show all users").

The columns display the individual weekdays.

<figure><img src="https://4063991107-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-La4YdZ1Gw5iHapqZfIo%2Fuploads%2FUplPiwXrvBn5fYthLP9b%2FBildschirmfoto%202025-11-26%20um%2014.25.06.png?alt=media&amp;token=3d1c2e82-9b6d-4401-b30f-51a3d2510e2e" alt=""><figcaption></figcaption></figure>

A new task can be created in a field by double-clicking.&#x20;

To move tasks, click on a task and drag it with the mouse while holding down the mouse button to another row (drag & drop).\
A task can be moved to a different day or to a different user.

At the bottom of each cell the scheduled and the available working time of an employee/user on that day are presented side by side, provided that this employee is permanently employed and a daily working time is stored for them. An exclamation mark and a red shading indicate that the scheduled time exceeds the available time.

![](https://4063991107-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-La4YdZ1Gw5iHapqZfIo%2F-LvLDiick3mAm18v_DF_%2F-LvLL6XhmDP-C1iaIHpB%2FBildschirmfoto%202019-12-05%20um%2014.53.41.png?alt=media\&token=1ccb2201-c3b9-4a72-bdc7-bef0e89cbb90)

### Missing tasks in the weekly view?

In this view only tasks are displayed that have a **start date** (and thus also have an end date and **are not closed** .


---

# 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/wochenansicht-der-vorgaenge.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.
