Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/LucPinheiro/gestor-tarea-django/llms.txt

Use this file to discover all available pages before exploring further.

Gestor de Tareas Django organises work around a single core model called Tarea. Each task carries a title, description, workflow state, numeric priority, and an optional deadline. Every operation — from first creation to final deletion — flows through a consistent set of views and URLs, so you always know exactly where to go and what to expect.

Creating a Task

Any user (authenticated or not) can open the task creation form at /crear/. The crear_tarea view does not carry the @login_required decorator, so unauthenticated visitors may also submit new tasks. On a successful POST, the new Tarea is saved and the browser is redirected to its detail page at /detalle/<id>/.
1

Navigate to the creation form

Open your browser and go to:
http://127.0.0.1:8000/crear/
The form is also reachable by clicking the Nuevo button in the top toolbar from any page.
2

Fill in the task fields

The form is backed by TareaForm, which exposes the following fields:
titulo
string
required
Short title for the task (maximum 100 characters). Maps to Tarea.titulo.
descripcion
string
required
Full description of the work to be done. Maps to Tarea.descripcion.
estado
dropdown
Current workflow state. Choose one of:
ValueMeaning
BorradorDraft — not yet ready for work (default)
PendienteQueued and waiting to be started
En procesoActively being worked on
CompletadaFinished
prioridad
dropdown
Numeric priority level. Choose one of:
ValueLabel
1Baja (Low)
2Media (Medium)
3Alta (High)
Defaults to 1 (Baja).
fecha_limite
date
Optional deadline. Use the native date picker or type a date in YYYY-MM-DD format. Leave blank if there is no fixed deadline.
fecha_creada is set automatically by the database (auto_now_add=True) and is not included in TareaForm. You cannot set or change it through the create or edit form.
3

Submit and confirm

Click the ☁ (save) button. If the form is valid, the app saves the record and redirects you to /detalle/<id>/ where you can immediately review the new task.

Viewing Task Detail

Every task has a dedicated detail page at /detalle/<id>/. This page shows all stored data, lets you move through the full task list without returning to the list view, and provides one-click controls for changing state and priority.
http://127.0.0.1:8000/detalle/42/
The detail view renders the following data from the Tarea model:
FieldDescription
tituloTask title displayed as a heading
descripcionFull description text
estadoCurrent state shown as a colour-coded badge
prioridadPriority shown as one, two, or three filled stars (★)
fecha_limiteDeadline badge (only shown when a date is set)
fecha_creadaCreation timestamp shown below the title
A position counter in the top-right corner shows where this task sits in the ordered list — for example 3 / 24 means task number 3 out of 24 total.

Editing a Task

The edit view reuses the same TareaForm and the same detalle.html template as the create flow, but loads an existing Tarea instance so all fields are pre-populated.
http://127.0.0.1:8000/editar/42/
1

Open the edit form

Navigate to /editar/<id>/ directly, or click the ✎ (edit) button in the task detail toolbar. A GET request renders the form with the current field values already filled in.
2

Make your changes

All five editable fields — titulo, descripcion, estado, prioridad, and fecha_limite — are available and work exactly as they do on the creation form.
3

Save

Click ☁ (save) to submit the form via POST. On success:
  • Django saves the updated record.
  • A green “Tarea actualizada correctamente.” success message is displayed at the top of the page.
  • The browser redirects to /detalle/<id>/.
If any validation errors exist, the form re-renders with inline error messages and no data is saved.

Deleting a Task

The application supports both single-task deletion with a confirmation step and bulk deletion of multiple tasks selected from the list view.

Single deletion

1

Open the confirmation page

Send a GET request to /eliminar/<id>/ — for example, by clicking the 🗑 (trash) icon in the task detail toolbar:
http://127.0.0.1:8000/eliminar/42/
The confirmar_eliminar.html template displays the task title and asks you to confirm.
2

Confirm deletion

Click Confirmar to send a POST to the same URL. The Tarea record is deleted from the database, a success message is shown, and you are redirected to the list view in list mode:
/tareas/?vista=lista
Click Cancelar to return to /detalle/<id>/ without making any changes.

Bulk deletion

1

Switch to list view

Navigate to /tareas/?vista=lista to see the tabular task list with checkboxes.
2

Select tasks

Tick the checkbox next to each task you want to delete. Use the Select All checkbox in the table header to select every task on the current page at once.
3

Delete selected

Open the ⚙ Acciones dropdown and click 🗑 Eliminar. A confirmation modal appears. Click Eliminar in the modal to confirm.The form submits via POST to /eliminar-seleccionadas/ with the selected IDs as tareas_seleccionadas values. All matching records are deleted in a single database query:
Tarea.objects.filter(id__in=ids).delete()
A success message confirms how many tasks were removed.
To quickly remove a large batch of tasks, use the list view checkboxes and the ⚙ Acciones → 🗑 Eliminar flow. If no checkboxes are ticked when you click Eliminar, a yellow “No hay tareas seleccionadas” warning appears automatically and no deletion occurs.

Build docs developers (and LLMs) love