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:
@@ -6,9 +6,11 @@ import {
|
||||
CommandResult,
|
||||
CreateIssueInput,
|
||||
Issue,
|
||||
IssuePage,
|
||||
IssuesGateway,
|
||||
IssueSummary,
|
||||
LinkIssuesInput,
|
||||
MyIssuesFilter,
|
||||
UpdateIssueInput,
|
||||
} from '@task-stream/web/tracker/domain';
|
||||
import { map, Observable } from 'rxjs';
|
||||
@@ -19,6 +21,7 @@ import {
|
||||
CreateIssueDocument,
|
||||
IssueDocument,
|
||||
LinkIssuesDocument,
|
||||
MyIssuesDocument,
|
||||
SearchIssuesDocument,
|
||||
SetIssueReleaseDocument,
|
||||
UnlinkIssuesDocument,
|
||||
@@ -42,7 +45,7 @@ export class GraphqlIssuesGateway extends IssuesGateway {
|
||||
.pipe(
|
||||
map((d) =>
|
||||
d.project.board.map((column) => ({
|
||||
status: column.status as BoardColumn['status'],
|
||||
status: column.status,
|
||||
total: column.total,
|
||||
issues: column.issues.map(toIssueSummary),
|
||||
})),
|
||||
@@ -56,6 +59,21 @@ export class GraphqlIssuesGateway extends IssuesGateway {
|
||||
.pipe(map((d) => toIssue(d.issue)));
|
||||
}
|
||||
|
||||
mine(filter: MyIssuesFilter): Observable<IssuePage> {
|
||||
return this.gql
|
||||
.query(MyIssuesDocument, {
|
||||
assignedToMe: filter.assignedToMe,
|
||||
categories: filter.categories as never,
|
||||
limit: filter.limit,
|
||||
})
|
||||
.pipe(
|
||||
map((d) => ({
|
||||
items: d.myIssues.items.map(toIssueSummary),
|
||||
total: d.myIssues.total,
|
||||
})),
|
||||
);
|
||||
}
|
||||
|
||||
search(projectId: string, text: string): Observable<IssueSummary[]> {
|
||||
return this.gql
|
||||
.query(SearchIssuesDocument, { filter: { projectId, search: text } })
|
||||
|
||||
Reference in New Issue
Block a user