# Flujos

{% hint style="info" %}
Un flujo de trabajo es un “recorrido” que siguen tus tareas, desde que nacen hasta que las das por terminadas.
{% endhint %}

### Flujos Pre configurados en Dinaup

| Flujo         | ¿Cuándo elegirlo?                       | Lo que ofrece                                                                                                                                                       |
| ------------- | --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **To Do**     | Listas simples de tareas                | <p>Solo dos pasos:<br><em><code>Por hacer</code></em>y <em><code>Hecho</code></em>.</p>                                                                             |
| **To Do Pro** | Seguimiento detallado del avance        | <p><em><code>Por hacer</code></em><br>Porcentajes <code>1 %</code>, <code>25 %</code>, <code>50 %</code>, <code>75 %</code><br><em><code>Hecho</code></em>.<br></p> |
| **Agile**     | Equipos que usan métodos Scrum o Kanban | Epics, Stories, Tasks, Sub-tasks y registro de Bugs.                                                                                                                |

#### 1. To Do (flujo básico)

El flujo más sencillo: perfecto para tomar nota de algo y marcarlo cuando se termina.

| Tipo | Estado | Clave | Padres compatibles |
| ---- | ------ | ----- | ------------------ |
| Task | To Do  | T1    | @                  |
| Task | Done   | T2    | @                  |

***

#### 2. To Do Pro (flujo extendido)

| Tipo         | Estado | Clave | Padres compatibles |
| ------------ | ------ | ----- | ------------------ |
| **Task**     | To Do  | T1    | @                  |
| Task         | 1 %    | T2    | @                  |
| Task         | 25 %   | T3    | @                  |
| Task         | 50 %   | T4    | @                  |
| Task         | 75 %   | T5    | @                  |
| Task         | Done   | T6    | @                  |
| **Sub-task** | To Do  | ST1   | T1,T2,T3,T4,T5,T6  |
| Sub-task     | 1 %    | ST2   | T1,T2,T3,T4,T5,T6  |
| Sub-task     | 25 %   | ST3   | T1,T2,T3,T4,T5,T6  |
| Sub-task     | 50 %   | ST4   | T1,T2,T3,T4,T5,T6  |
| Sub-task     | 75 %   | ST5   | T1,T2,T3,T4,T5,T6  |
| Sub-task     | Done   | ST6   | T1,T2,T3,T4,T5,T6  |

> Mismo flujo que el básico, pero con porcentajes de avance y la posibilidad de desglosar cada tarea en sub-tareas medibles.

***

#### 3. Agile (flujo completo)

| Tipo         | Estado      | Clave | Padres compatibles   |
| ------------ | ----------- | ----- | -------------------- |
| **Epic**     | Backlog     | E1    | @                    |
| Epic         | To Do       | E2    | @                    |
| Epic         | In Progress | E3    | @                    |
| Epic         | Done        | E4    | @                    |
| **Story**    | Backlog     | S1    | E1,E2,E3,E4          |
| Story        | To Do       | S2    | E1,E2,E3,E4          |
| Story        | In Progress | S3    | E1,E2,E3,E4          |
| Story        | Done        | S4    | E1,E2,E3,E4          |
| **Task**     | Backlog     | T1    | S1,S2,S3,S4          |
| Task         | In Progress | T3    | S1,S2,S3,S4          |
| Task         | 25 %        | T4    | S1,S2,S3,S4          |
| Task         | 50 %        | T5    | S1,S2,S3,S4          |
| Task         | 75 %        | T6    | S1,S2,S3,S4          |
| Task         | Done        | T7    | S1,S2,S3,S4          |
| **Sub-task** | Backlog     | ST1   | T1,T2,T3,T4,T5,T6,T7 |
| Sub-task     | To Do       | ST2   | T1,T2,T3,T4,T5,T6,T7 |
| Sub-task     | In Progress | ST3   | T1,T2,T3,T4,T5,T6,T7 |
| Sub-task     | Done        | ST4   | T1,T2,T3,T4,T5,T6,T7 |
| **Bug**      | To Do       | B2    | E1,E2,E3,E4          |
| Bug          | In Progress | B3    | E1,E2,E3,E4          |
| Bug          | Done        | B4    | E1,E2,E3,E4          |

> Flujo pensado para equipos Scrum/Kanban: epics agrupan stories, stories agrupan tasks y cada task puede desglosarse en sub-tareas. Además, tienes bugs independientes que reportan contra los epics.

***


---

# Agent Instructions: 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:

```
GET https://doc.dinaup.com/producto/proyectos/flujos.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.