Josep Piguillem
034704e46f
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>
web-tracker-domain
Modelo del tracker en el cliente.
- Import:
@task-stream/web/tracker/domain - Capa:
domain· Tags:scope:web-tracker,type:domain
Contenido
- Modelos (
Project,IssueSummary,Issue,Release…), enums e inputs. - Configuración por proyecto (
ProjectSettings,StatusCategory) yWorkflow: nombres, colores, iconos, categorías, transiciones permitidas y estados que piden motivo, con un nombre legible para ids que ya no están configurados. - Estadísticas (
ProjectAnalytics,ReleaseBurnup). - Puertos:
ProjectsGateway,IssuesGateway,CommentsGateway,ReleasesGateway,ActivityGateway,UsersGateway,TrackerRealtimeGateway.
Comandos
npx nx lint web-tracker-domain
npx nx test web-tracker-domain # Jest
Reglas de dependencia entre capas: Arquitectura.