Files

Josep Piguillem 79b8094011 feat(web): project health as a traffic light, with its causes

The project dashboard opens with «Salud del proyecto»: good, attention or
at risk, the worst of its signals, each with the cause and the tickets
behind it: stuck work, overdue and blocked tickets, critical or several
high bugs, QA sending back 30 % or more (with enough verdicts), releases
late or at risk by the forecast, columns over their WIP limit. Worked
out in the web from the insights it already reads (projectHealth). The
portfolio shows each project's light too, with its causes on hover.

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

2026-10-20 21:08:21 +02:00

01-vision-general.md

feat(web): project health as a traffic light, with its causes

2026-10-20 21:08:21 +02:00

02-arquitectura.md

fix(api): a read-side failure waits for its event instead of losing it

2026-10-16 22:24:19 +02:00

03-api.md

feat: a public notes page per release, for clients

2026-10-20 20:57:40 +02:00

04-cliente-web.md

feat(web): project health as a traffic light, with its causes

2026-10-20 21:08:21 +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

fix(api): a read-side failure waits for its event instead of losing it

2026-10-16 22:24:19 +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: quick polls in comments that end in a decision

2026-10-20 20:48:12 +02:00

10-futuro.md

fix(api): a read-side failure waits for its event instead of losing it

2026-10-16 22:24:19 +02:00

README.md

docs: what is left (chapter 10)

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

TaskStream-Documentacion.docx

fix(api): a read-side failure waits for its event instead of losing it

2026-10-16 22:24:19 +02:00

TaskStream-Documentacion.pdf

fix(api): a read-side failure waits for its event instead of losing it

2026-10-16 22:24:19 +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).