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

# Customize the task workflow

Customize the tracking steps of Dastra tasks and their internal status, and classify your tasks with tags.

Each task follows a workflow: it moves from one step to the next until it is closed. The steps are the columns of the **Columns** view. You can adapt them to your organization's tracking rules.

## The default steps

A new workspace comes with four steps. Each one is linked to an internal status, **New**, **Active** or **Closed**, which does not depend on the name of the step:

| Step            | Internal status |
| --------------- | --------------- |
| **New**         | **New**         |
| **Info needed** | **Active**      |
| **In progress** | **Active**      |
| **Done**        | **Closed**      |

The last step, **Done**, is the final step: a task that reaches it is considered finished.

## Edit the steps

1. In the side menu, click **Workspace settings**, then, in the **Process** section, **Workflow stages**. You can also click, on the **Tasks** page, the arrow of the **Create task** button, then **Configure columns**.
2. In the list at the top of the **Workflow management** page, choose the **Tasks** object type.
3. Add, rename or reorder the steps, choose their internal status, then click **Save changes**.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-173822e39ee969fa5c3ee3808267ca528faddc5a%2Ftasks-workflow-1.png?alt=media" alt="The Workflow management page with the four steps of the task workflow and their internal status"><figcaption><p>The steps of the task workflow</p></figcaption></figure>

This page is reserved for users who are allowed to manage advanced settings. The detailed procedure (adding, ordering and deleting a step) is described in [Workflow stages](https://doc.dastra.eu/en/features/settings/workflow-stages.md). You can also rename a step directly in the header of its column, in the **Columns** view.

## Classify tasks with tags

The **Tags** field of the task panel lets you classify tasks to find them faster: the **Filter by tags** filter uses them in every view. Tags are managed in **Workspace settings**, **Process** section, **Tags** entry.

## Go further

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