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:
@@ -7,6 +7,7 @@ import {
|
||||
CommentsGateway,
|
||||
CreateReleaseInput,
|
||||
Release,
|
||||
ReleaseBurnup,
|
||||
ReleasesGateway,
|
||||
UserDirectoryEntry,
|
||||
UsersGateway,
|
||||
@@ -21,7 +22,9 @@ import {
|
||||
EditCommentDocument,
|
||||
IssueCommentsDocument,
|
||||
PublishReleaseDocument,
|
||||
ReleaseBurnupDocument,
|
||||
ReleasesDocument,
|
||||
UpcomingReleasesDocument,
|
||||
SearchUsersDocument,
|
||||
} from '../graphql/generated';
|
||||
import { GraphqlOperations } from './graphql-operations';
|
||||
@@ -66,6 +69,12 @@ export class GraphqlReleasesGateway extends ReleasesGateway {
|
||||
.pipe(map((d) => d.project.releases.map(toRelease)));
|
||||
}
|
||||
|
||||
upcoming(limit: number): Observable<Release[]> {
|
||||
return this.gql
|
||||
.query(UpcomingReleasesDocument, { limit })
|
||||
.pipe(map((d) => d.upcomingReleases.map(toRelease)));
|
||||
}
|
||||
|
||||
create(input: CreateReleaseInput): Observable<CommandResult> {
|
||||
return this.gql
|
||||
.mutate(CreateReleaseDocument, { input })
|
||||
@@ -83,6 +92,12 @@ export class GraphqlReleasesGateway extends ReleasesGateway {
|
||||
.mutate(ArchiveReleaseDocument, { releaseId })
|
||||
.pipe(map((d) => toCommandResult(d.archiveRelease)));
|
||||
}
|
||||
|
||||
burnup(releaseId: string): Observable<ReleaseBurnup> {
|
||||
return this.gql
|
||||
.query(ReleaseBurnupDocument, { id: releaseId })
|
||||
.pipe(map((d) => d.release.burnup));
|
||||
}
|
||||
}
|
||||
|
||||
@Injectable()
|
||||
|
||||
Reference in New Issue
Block a user