Files

Josep Piguillem 034704e46f feat: alerts open bugs, and repeats of the same problem go to that bug

Owners and admins turn on a secret URL per project (Settings →
Integrations), POST /api/webhooks/alerts/{project}/{token}, that Sentry,
Uptime Kuma, Prometheus Alertmanager, Grafana or any tool sending JSON
with a title can call. A new problem opens a bug as TaskStream (label
«alerta», chosen type and priority); while that bug is open, the same
fingerprint goes to it (a comment at most every 30 minutes) and
«resolved» is said on it; once it is closed, a new bug names the old
one. Alerts of a project are handled one at a time, so two at once open
one bug, and a bug not yet projected still counts as open. Unknown
project, alerts off or a bad token all answer 403.

TaskStream may now comment as the system actor, like it already opened
tickets for public proposals. Stored in Mongo (alert_integrations,
alert_traces), not in the event store.

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

2026-10-17 12:36:55 +02:00

src

feat: alerts open bugs, and repeats of the same problem go to that bug

2026-10-17 12:36:55 +02:00

eslint.config.mjs

first commit

2026-10-03 13:40:26 +02:00

jest.config.cts

first commit

2026-10-03 13:40:26 +02:00

project.json

feat: per-project workflow settings, statistics and "my work" home

2026-10-06 20:53:45 +02:00

README.md

feat: public projects, project deletion and sagas

2026-10-07 07:04:20 +02:00

tsconfig.json

first commit

2026-10-03 13:40:26 +02:00

tsconfig.lib.json

first commit

2026-10-03 13:40:26 +02:00

tsconfig.spec.json

first commit

2026-10-03 13:40:26 +02:00

README.md

api-tracker-infrastructure

Adaptadores de salida del tracker.

Import: @task-stream/api/tracker/infrastructure
Capa: infrastructure · Tags: scope:api-tracker, type:infrastructure

Contenido

postgres/: lookups de escritura (project_keys, issue_sequences, release_names), ReleaseIssuesRepository y TrackerStreamsRepository (consultan el event store: tickets y releases de un proyecto, comentarios y enlaces de un ticket).
mongo/: esquemas del read model (incluida la línea temporal issue_timeline), repositorios Find* y UpsertMaterialized* (upsert idempotente por versión) y StatusCategoryBackfill (al arrancar, rellena la categoría del estado en los tickets proyectados antes de existir).
realtime/: RedisChangeFeed (canales de Redis pub/sub por proyecto, ticket y usuario).
identity/: IdentityUserDirectory, capa anticorrupción hacia el contexto de identidad.

Comandos

npx nx lint api-tracker-infrastructure
npx nx test api-tracker-infrastructure    # Jest

Reglas de dependencia entre capas: Arquitectura.