Files

Josep Piguillem 0e301ad545 feat: per-project workflow settings, statistics and "my work" home

Per-project settings (owners/admins, «Configuración» tab):
- Statuses with category (TODO, IN_PROGRESS, QA, DONE, CANCELLED), colour and
  "requires reason"; configurable transitions; ticket types (icon, colour) and
  areas. Defaults are the previous fixed values; projects created before keep
  them without migration.
- Values are archived, never deleted: tickets, history and statistics keep
  referring to them. Validated in the domain (ProjectSettingsChangedEvent).
- Releases, board, tracking and "my work" use categories, so custom statuses
  keep working. Status changes carry name/category metadata for history.
- GraphQL: status/type/area are strings (breaking for clients sending enum
  literals); Project.settings, updateProjectSettings, statusCategory,
  myIssues(categories). REST: PUT /projects/{project}/settings, category filters.
- Read model: statusCategory on issues (backfilled at startup).

Statistics («Estadísticas» tab):
- New issue_timeline projection; pure functions compute created vs resolved,
  cumulative flow, cycle/lead time (avg + p85), throughput per person, QA
  pass/fail and release burnup. GraphQL Project.analytics(days),
  Release.burnup; REST /projects/{project}/analytics, /releases/{id}/burnup.
- Web: SVG charts with validated light/dark palette, crosshair tooltip,
  keyboard navigation, legend and data table.

Home "Mi trabajo": my open tickets across projects grouped by category (QA
failures first), tickets waiting for QA, upcoming releases and "Ir a…".

Tests: domain/application specs, e2e scenario for settings and analytics,
facade tests. Docs, READMEs, schema.gql/openapi.json and Word/PDF updated.

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

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

822 B

Raw Blame History

web-tracker-presenters

Pantallas del tracker con @pi/ui.

Import: @task-stream/web/tracker/presenters
Capa: presenters · Tags: scope:web-tracker, type:presenters

Contenido

Rutas trackerRoutes: inicio (proyectos + «Mi trabajo», pages/my-work.ts), tablero kanban (drag & drop), ticket, releases, seguimiento, estadísticas, actividad, miembros y configuración.
ui/: IssueCardComponent, AvatarsComponent, GoToComponent («Ir a… WEB-12»), SeriesChartComponent (gráficas SVG de líneas y áreas apiladas) y copy.ts (textos y tonos; estados, tipos y áreas salen del Workflow del proyecto).

Comandos

npx nx lint web-tracker-presenters

Reglas de dependencia entre capas: Arquitectura.

822 B Raw Blame History

web-tracker-presenters

Contenido

Comandos

822 B

Raw Blame History