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>
This commit is contained in:
2026-10-06 20:53:45 +02:00
parent 240ea9a539
commit 0e301ad545
143 changed files with 10291 additions and 1052 deletions

View File

@@ -0,0 +1,58 @@
import { StatusCategory } from '../project/project-settings';
import { UserRefReadModel } from './user-ref.read-model';
/**
* One step in a ticket's life (projected from its events): the raw material
* of the statistics. `status` entries record where the ticket went (with the
* category it had then), `release` entries which release it joined or left.
*/
export class IssueTimelineEntry {
/** Id of the event that produced it (projection is idempotent). */
id!: string;
issueId!: string;
projectId!: string;
at!: string;
kind!: 'status' | 'release';
status?: string;
category?: StatusCategory;
/** Assignee when the status changed (throughput per person). */
assigneeId?: string | null;
releaseId?: string | null;
}
export class DurationStats {
count!: number;
averageDays!: number | null;
/** 85th percentile: "85% of tickets take at most this long". */
p85Days!: number | null;
}
/** Statistics of a project over a period. */
export class ProjectAnalyticsReadModel {
from!: string;
to!: string;
/** Per week (Monday): tickets created and tickets finished. */
createdVsResolved!: { week: string; created: number; resolved: number }[];
/** Tickets in each status at the end of every day (cumulative flow). */
cumulativeFlow!: {
dates: string[];
series: { status: string; counts: number[] }[];
};
/** From starting work to done. */
cycleTime!: DurationStats;
/** From creation to done. */
leadTime!: DurationStats;
/** Tickets finished per person and week. */
throughput!: { week: string; user: UserRefReadModel | null; count: number }[];
/** Tickets leaving QA: to done (passed) or back to work (failed). */
qa!: { passed: number; failed: number; failureRate: number | null };
}
/** Scope vs finished tickets of a release, day by day. */
export class ReleaseBurnupReadModel {
releaseId!: string;
targetDate!: string | null;
dates!: string[];
scope!: number[];
done!: number[];
}

View File

@@ -5,3 +5,4 @@ export * from './comment.read-model';
export * from './release.read-model';
export * from './activity.read-model';
export * from './project-stats.read-model';
export * from './analytics.read-model';

View File

@@ -1,10 +1,5 @@
import {
IssueArea,
IssueLinkType,
IssuePriority,
IssueStatus,
IssueType,
} from '../issue/issue.enums';
import { IssueLinkType, IssuePriority } from '../issue/issue.enums';
import { StatusCategory } from '../project/project-settings';
import { UserRefReadModel } from './user-ref.read-model';
export type LinkDirection = 'OUTWARD' | 'INWARD';
@@ -23,11 +18,14 @@ export class IssueReadModel {
projectKey!: string;
number!: number;
key!: string;
type!: IssueType;
area!: IssueArea | null;
/** Ids from the project's settings. */
type!: string;
area!: string | null;
title!: string;
description!: string | null;
status!: IssueStatus;
status!: string;
/** Category of `status` (kept in sync when the project's settings change). */
statusCategory!: StatusCategory;
priority!: IssuePriority;
reporter!: UserRefReadModel;
assignee!: UserRefReadModel | null;

View File

@@ -1,4 +1,4 @@
import { IssuePriority, IssueStatus, IssueType } from '../issue/issue.enums';
import { IssuePriority } from '../issue/issue.enums';
import { UserRefReadModel } from './user-ref.read-model';
export class CountBy<TKey = string> {
@@ -10,8 +10,9 @@ export class CountBy<TKey = string> {
export class ProjectStatsReadModel {
total!: number;
open!: number;
byStatus!: CountBy<IssueStatus>[];
byType!: CountBy<IssueType>[];
/** Keys are status / type ids of the project's settings. */
byStatus!: CountBy<string>[];
byType!: CountBy<string>[];
byPriority!: CountBy<IssuePriority>[];
byArea!: CountBy<string>[];
/** Open tickets per person (user null = unassigned). */

View File

@@ -1,4 +1,5 @@
import { ProjectRole } from '../project/project-role';
import { ProjectSettings } from '../project/project-settings';
import { UserRefReadModel } from './user-ref.read-model';
export class ProjectMemberReadModel {
@@ -13,6 +14,8 @@ export class ProjectReadModel {
description!: string | null;
owner!: UserRefReadModel;
members!: ProjectMemberReadModel[];
/** Statuses, transitions, ticket types and areas. */
settings!: ProjectSettings;
createdAt!: string;
updatedAt!: string;
/** Position of the last projected event. */

View File

@@ -1,4 +1,3 @@
import { IssueStatus } from '../issue/issue.enums';
import { ReleaseStatus } from '../release/release-status';
export class ReleaseReadModel {
@@ -17,5 +16,5 @@ export class ReleaseProgressReadModel {
total!: number;
finished!: number;
percent!: number;
byStatus!: { key: IssueStatus; count: number }[];
byStatus!: { key: string; count: number }[];
}