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

@@ -19,6 +19,32 @@ fragment ProjectFields on Project {
...UserRefFields
}
}
settings {
statuses {
id
name
category
color
requiresReason
archived
}
transitions {
from
to
}
issueTypes {
id
name
icon
color
archived
}
areas {
id
name
archived
}
}
}
fragment IssueSummaryFields on Issue {
@@ -29,6 +55,7 @@ fragment IssueSummaryFields on Issue {
area
title
status
statusCategory
priority
labels
commentCount

File diff suppressed because it is too large Load Diff

View File

@@ -1,9 +1,4 @@
query Board(
$idOrKey: String!
$releaseId: ID
$assigneeId: ID
$area: IssueArea
) {
query Board($idOrKey: String!, $releaseId: ID, $assigneeId: ID, $area: String) {
project(idOrKey: $idOrKey) {
id
board(
@@ -105,3 +100,20 @@ mutation DeleteComment($commentId: ID!) {
...CommandResultFields
}
}
query MyIssues(
$assignedToMe: Boolean!
$categories: [StatusCategory!]
$limit: Int!
) {
myIssues(
assignedToMe: $assignedToMe
categories: $categories
limit: $limit
) {
total
items {
...IssueSummaryFields
}
}
}

View File

@@ -73,3 +73,56 @@ query SearchUsers($search: String!) {
email
}
}
mutation UpdateProjectSettings(
$projectId: ID!
$settings: ProjectSettingsInput!
) {
updateProjectSettings(projectId: $projectId, settings: $settings) {
...CommandResultFields
}
}
query ProjectAnalytics($idOrKey: String!, $days: Int!) {
project(idOrKey: $idOrKey) {
id
analytics(days: $days) {
from
to
createdVsResolved {
week
created
resolved
}
cumulativeFlow {
dates
series {
status
counts
}
}
cycleTime {
count
averageDays
p85Days
}
leadTime {
count
averageDays
p85Days
}
throughput {
week
count
user {
...UserRefFields
}
}
qa {
passed
failed
failureRate
}
}
}
}

View File

@@ -35,3 +35,27 @@ query Activity($projectId: ID!, $issueId: ID) {
...ActivityFields
}
}
query UpcomingReleases($limit: Int!) {
upcomingReleases(limit: $limit) {
...ReleaseFields
progress {
total
finished
percent
}
}
}
query ReleaseBurnup($id: ID!) {
release(id: $id) {
id
burnup {
releaseId
targetDate
dates
scope
done
}
}
}