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

# Create or edit a task

Create a task of the action plan, assign it, edit it, move it to the recycle bin or delete it.

In Dastra, a task is a piece of work to be done. It has an assignee, a due date and a tracking step. This page explains how to create, assign, edit and delete a task.

## Create a task

You can create a task in three ways:

* from the **Tasks** page of the planning module;
* from the record of another item in the application;
* from an email received at a collection address.

### From the planning module

1. In the side menu, click **Tasks**, then choose **Tasks** in the submenu.
2. Click **Create task**. The **Create task** panel opens on the right of the screen.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-abfeb38603280c5f942196afdb5bfbd27bfb1a54%2Ftasks-create-1.png?alt=media" alt="The toolbar of the Tasks page with the Create task button and its drop-down menu open"><figcaption><p>The Create task button and the actions of its menu</p></figcaption></figure>

3. Fill in the **Title of the task** (120 characters maximum) and the **Organizational unit**, which are required. Complete the other fields as needed.
4. Click **Save changes**. To create several tasks in a row, click **Save and add another**.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-7619111bddc92cad1b74b3fcbbdc3e61dfa7add5%2Ftasks-create-2.png?alt=media" alt="The Create task panel with the title, organizational unit, assignee, dates and associated elements"><figcaption><p>The task creation panel</p></figcaption></figure>

The panel includes:

* **Organizational unit**: prefilled with the unit selected in the workspace, or the first available unit;
* **Project**, **Sprint** and **Tags** to classify the task;
* **Assigned to**, **Start date** and **Due date**;
* **Priority** and **Internal reference**, in the expandable part of the panel;
* the custom fields you added to tasks.

### Link a task to items

A task can be linked to one or more items of the application. In the panel, click **Associate element**, choose the type of item, then one or more items of that type. The linked items are listed under **Associated elements**.

The available types are:

* **Processing activity**;
* **Request**;
* **Data breach**;
* **Responding to a questionnaire**;
* **Stakeholder**;
* **Asset**;
* **Dataset**;
* **Risk assessment**;
* **Control point**;
* **Security measure**;
* **AI system**;
* **Contract**;
* **Datafield**;
* **Category of data subjects**;
* **Compliance project**;
* **Compliance Audit**.

You then find the task in the record of each of these items (see below). The **Associated with** filter of the **Tasks** page lists the tasks linked to a given type of item.

### From the record of another item

The records of processing activities, data subject requests, data breaches, stakeholders, assets, datasets, security measures, contracts, AI systems, control points and risk assessments have a task button: a list icon with a check mark and the number of linked tasks.

1. Open the record of the item.
2. Click the task button. The **Related tasks** panel lists the tasks linked to this item, with filters by step and by tag.
3. Click **Create task**. The task is linked to the item and takes its organizational unit.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-e17ad458938794b5bd43cd00cf3968924800a412%2Ftasks-create-3.png?alt=media" alt="The record of a processing activity with the Related tasks panel open"><figcaption><p>The Related tasks panel on the record of a processing activity</p></figcaption></figure>

The **Show in planning** button of the panel opens the **Tasks** page with the tasks of the item.

{% hint style="info" %}
An action plan can also be generated from a validated questionnaire. See [Monitor questionnaires](https://doc.dastra.eu/en/features/questionnaires/monitor.md).
{% endhint %}

### From an email

Dastra can turn each email received at a collection address into a task, with its attachments. To set up the address, click the arrow of the **Create task** button, then **Transform emails into tasks**. The setup page opens in **Workspace settings** > **Integrations**. See [Incoming mail data collection](https://doc.dastra.eu/en/features/settings/mailboxes.md). This entry requires the permission to manage integrations.

### Create sub-tasks

A task can contain a list of sub-tasks. Save the task first: the **Add sub-tasks** button stays inactive until the task exists. Then edit the task and click **Add sub-tasks**.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-bca538b21727722291baa0521cf8b279b461a1d1%2Ftasks-create-4.png?alt=media" alt="An open task with its list of sub-tasks and the Add sub-tasks button"><figcaption><p>The sub-tasks of a task</p></figcaption></figure>

When all the sub-tasks are closed, Dastra offers to close the main task.

## Assign a task

Two fields identify the people involved:

* **Assigned to**: the person who carries out the task. By default, it is you when you create the task;
* **Task owner**: the person responsible for the task. They are notified when the step changes.

The **Task owner** field is in the expandable part of the panel. Each user receives notifications according to their preferences: see [Notifications](https://doc.dastra.eu/en/features/settings/notifications.md). To follow up with someone, mention them in the discussion of the task (see the [FAQ](https://doc.dastra.eu/en/features/tasks/faq.md)).

## Edit a task

To edit a task, click it: the **Task edition** panel opens. In the **Table** view, you can also click the three dots at the right of the row, then **Edit**.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-a73d59ba6724668ffba5f08248d997e95cac8759%2Ftasks-create-5.png?alt=media" alt="The Table view with the three-dot menu of a task open"><figcaption><p>The menu of a task in the Table view</p></figcaption></figure>

This menu also offers **Copy link**, **Create a copy**, **Merge** and **Move to recycle bin**. **Create a copy** duplicates the task and its sub-tasks: the title of the copy ends with " - copy".

{% hint style="info" %}
To change the step of a task, drag and drop it in the **Columns** view. The default steps are **New**, **Info needed**, **In progress** and **Done**. To change them, click the arrow of the **Create task** button, then **Configure columns**: see [Customize the task workflow](https://doc.dastra.eu/en/features/tasks/workflow.md).
{% endhint %}

### Send a task to Jira

When the Jira integration is active for tasks, the actions menu of the task offers **Send to Jira**. See [Jira](https://doc.dastra.eu/en/features/integrations/jira.md).

## Move a task to the recycle bin or delete it

A task moved to the recycle bin is not deleted: it shows the **Into recycle bin** mention and disappears from the lists. You can restore it at any time.

1. In the three-dot menu of the task, or in the actions menu of the panel, click **Move to recycle bin**, then confirm.
2. To find the tasks of the recycle bin, open **Filters** and select **View recycle bin**.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-d191cfadabee3899bd1d2d23b127ddc7715b2ba6%2Ftasks-create-6.png?alt=media" alt="The Filters panel with the View recycle bin box selected"><figcaption><p>The View recycle bin filter</p></figcaption></figure>

3. In the menu of the task, click **Restore** to put it back in the list, or **Delete**, then confirm, to delete it.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-45aeb05828faa2aca6fdb529b94420740f6edf62%2Ftasks-create-7.png?alt=media" alt="The menu of a task in the recycle bin with the Restore and Delete actions"><figcaption><p>The actions of a task in the recycle bin</p></figcaption></figure>

{% hint style="danger" %}
Deleting a task is permanent. Its sub-tasks are deleted with it.
{% endhint %}

To delete tasks without going through the recycle bin, see the [FAQ](https://doc.dastra.eu/en/features/tasks/faq.md).

## Go further

{% content-ref url="/pages/D025SDOk7aTmNrNenMmR" %}
[Create or edit a project or a sprint](https://doc.dastra.eu/en/features/tasks/projects.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/create.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.
