Files

Josep Piguillem 1101b6e926 feat: dashboard maps the activity, follows a ticket's way and the proposals

Three more blocks on the project dashboard, also by REST, GraphQL and
MCP:
- Activity: what moved each day of the last 12 weeks, in a heatmap,
  with the busiest weekday and the longest lull.
- A ticket's way: for the tickets done in the last 90 days, where the
  time from created to done went, status by status (waiting included),
  and how much of it was work (flow efficiency).
- The public's proposals: received, waiting, under way, done and
  discarded, and the most voted still unanswered.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-16 09:29:38 +02:00

01-vision-general.md

feat(web): dependencies between epics on the roadmap

2026-10-15 10:00:14 +02:00

02-arquitectura.md

refactor(web): page state with its page, the root keeps the shell's

2026-10-16 08:34:17 +02:00

03-api.md

feat: dashboard maps the activity, follows a ticket's way and the proposals

2026-10-16 09:29:38 +02:00

04-cliente-web.md

feat: dashboard maps the activity, follows a ticket's way and the proposals

2026-10-16 09:29:38 +02:00

05-autenticacion.md

fix(api): accept Pireon webhooks from the password client too

2026-10-09 13:29:27 +02:00

06-desarrollo.md

feat: attachments on tickets and comments

2026-10-08 08:35:33 +02:00

07-despliegue.md

feat: push notifications on each device (Web Push)

2026-10-15 08:38:07 +02:00

08-decisiones.md

feat: notifications in the app and, optionally, by e-mail

2026-10-08 09:19:59 +02:00

09-mcp.md

feat: dashboard maps the activity, follows a ticket's way and the proposals

2026-10-16 09:29:38 +02:00

10-futuro.md

feat: dashboard maps the activity, follows a ticket's way and the proposals

2026-10-16 09:29:38 +02:00

README.md

docs: what is left (chapter 10)

2026-10-09 21:42:54 +02:00

TaskStream-Documentacion.docx

feat: dashboard maps the activity, follows a ticket's way and the proposals

2026-10-16 09:29:38 +02:00

TaskStream-Documentacion.pdf

feat: dashboard maps the activity, follows a ticket's way and the proposals

2026-10-16 09:29:38 +02:00

README.md

Documentación de TaskStream

TaskStream es una alternativa a Jira para equipos de desarrollo: proyectos, tickets (bugs, features, cambios de UI, tareas, QA), releases, comentarios y relaciones entre tickets, todo en tiempo real.

Documento	Para qué
1. Visión general	Qué hace el producto, stack y estructura del monorepo
2. Arquitectura	Hexagonal, CQRS, event sourcing, flujo escritura → lectura y tiempo real
3. API	Dominio (agregados, workflow, eventos) y la API GraphQL
4. Cliente web	Angular, NgRx Signals con eventos, GraphQL y `@pi/ui`
5. Autenticación	Pireon: tokens, login en el navegador, sesiones y webhooks
6. Desarrollo	Puesta en marcha, comandos, tests y cómo añadir una funcionalidad
7. Despliegue	Docker, variables de entorno y escalado
8. Decisiones	Por qué está hecho así (y qué alternativas se descartaron)
9. Servidor MCP	Usar TaskStream desde asistentes de IA (Claude…): herramientas y conexión
10. Lo que queda	Pendiente para cerrar, fallos conocidos, siguientes funcionalidades y lo descartado

Cada librería de libs/ tiene además su propio README.md con su responsabilidad y su contenido.

Empezar rápido

docker compose up -d --build     # web en http://localhost:8080

Para entrar hacen falta dos clientes OAuth de Pireon en .env (authorization_code y password, ver Autenticación).