> For the complete documentation index, see [llms.txt](https://doc.dastra.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.dastra.eu/en/features/tasks.md).

# Planning

Discover the Dastra planning module: your organization's action plan, its tasks, projects and sprints.

The planning module gathers the tasks of your workspace's action plan. You create tasks, assign them, track their progress and export them. It is meant for data protection officers (DPOs) and compliance teams who need to show what they have done.

## Why keep an action plan

Article 24 of the GDPR sets out the principle of accountability:

> (...) the controller implements appropriate technical and organizational measures to ensure and to be able to demonstrate that processing is performed in accordance with this Regulation.

Once an organization has mapped and assessed its processing activities, it must put technical and organizational measures in place to protect them. The regulation requires you to demonstrate compliance without giving precise indicators. A clear, shared and traceable action plan provides concrete evidence: each task has an assignee, a due date, a step and a history.

## Open the module

In the side menu, click **Tasks**. The menu expands to five pages:

* **Tasks**: the list of tasks, with the Columns, Table, Tree and Calendar views;
* **Stats**: indicators and progress charts;
* **Current sprint**: the tasks of the sprint in progress;
* **Projects**: the projects that group tasks;
* **Sprints**: the work periods.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-939f837e79d0e1f4c3ce3651aa3f33a6080ff9fe%2Ftasks-readme-1.png?alt=media" alt="The side menu with the Tasks entry expanded to its five pages"><figcaption><p>The pages of the planning module in the side menu</p></figcaption></figure>

The **Tasks** page opens by default in the **Columns** view, where tasks are laid out by step.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-042657fe16038c06aa9acbd16538e20351b350a9%2Ftasks-readme-2.png?alt=media" alt="The Tasks page in the Columns view, with tasks laid out in four steps"><figcaption><p>The Tasks page in the Columns view</p></figcaption></figure>

{% hint style="info" %}
The **Tasks** entry only appears if your role gives access to tasks and the module is enabled for your organization.
{% endhint %}

## Go further

{% content-ref url="/pages/-Lw3vLXGuGVgeBPgD8o4" %}
[Create or edit a task](https://doc.dastra.eu/en/features/tasks/create.md)
{% endcontent-ref %}

{% content-ref url="/pages/D025SDOk7aTmNrNenMmR" %}
[Create or edit a project or a sprint](https://doc.dastra.eu/en/features/tasks/projects.md)
{% endcontent-ref %}

{% content-ref url="/pages/-M4IsZv5LlnhFy3FVybO" %}
[Monitor, filter or export tasks](https://doc.dastra.eu/en/features/tasks/export.md)
{% endcontent-ref %}

{% content-ref url="/pages/KyRgvqeAt04DH2pnQyOQ" %}
[Customize the task workflow](https://doc.dastra.eu/en/features/tasks/workflow.md)
{% endcontent-ref %}

{% content-ref url="/pages/xdLPrYI64RdQcWWFsWaP" %}
[Share as calendar](https://doc.dastra.eu/en/features/tasks/calendar-sync.md)
{% endcontent-ref %}

{% content-ref url="/pages/i1eLkTlWYdu8ZZBZxmeU" %}
[FAQ](https://doc.dastra.eu/en/features/tasks/faq.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://doc.dastra.eu/en/features/tasks.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.
