Files

Josep Piguillem 1550332d41 refactor(api): buses only in services, atomic commands, @Prop schemas

- Mongo read models are @Schema/@Prop classes (SchemaFactory), still
  loose: the props declared are the indexed or shaped ones.
- CommandBus and QueryBus are used by the application services alone.
  Duplicating a ticket, bulk updates, CSV imports, proposals and
  emptying the trash chain several commands, so they are service
  methods now and their composite commands are gone; every command
  handler is atomic. No forwardRef is needed.
- The due-date and trash timers are entry points: they live in the
  presenters and call the services. The automations event handler has
  its own file and calls AutomationsService.
- The tracker's user directory asks IdentityService; the composition
  root hands the identity application module to the tracker
  infrastructure (withIdentity), with no global module.

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

2026-10-14 19:56:59 +02:00

01-vision-general.md

feat(web): write descriptions and comments with a visual editor

2026-10-13 23:00:41 +02:00

02-arquitectura.md

refactor(api): buses only in services, atomic commands, @Prop schemas

2026-10-14 19:56:59 +02:00

03-api.md

feat(web): write descriptions and comments with a visual editor

2026-10-13 23:00:41 +02:00

04-cliente-web.md

feat(web): write descriptions and comments with a visual editor

2026-10-13 23:00:41 +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): accept Pireon webhooks from the password client too

2026-10-09 13:29:27 +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: formatted text, a list view, ticket details, public proposals and votes

2026-10-09 21:36:11 +02:00

10-futuro.md

feat: uuid ids everywhere, pickers for linked tickets, @pi/ui checkboxes

2026-10-14 19:16:43 +02:00

README.md

docs: what is left (chapter 10)

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

TaskStream-Documentacion.docx

refactor(api): buses only in services, atomic commands, @Prop schemas

2026-10-14 19:56:59 +02:00

TaskStream-Documentacion.pdf

refactor(api): buses only in services, atomic commands, @Prop schemas

2026-10-14 19:56:59 +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).