Josep Piguillem
0e301ad545
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>
65 lines
1.7 KiB
TypeScript
65 lines
1.7 KiB
TypeScript
import { BoardColumn, IssueSummary } from '@task-stream/web/tracker/domain';
|
|
import { applyIssueChange, moveIssue } from './board.reducers';
|
|
|
|
const issue = (
|
|
id: string,
|
|
status: string,
|
|
version = 1,
|
|
assignee: string | null = null,
|
|
): IssueSummary =>
|
|
({
|
|
id,
|
|
status,
|
|
version,
|
|
key: id,
|
|
projectId: 'p',
|
|
title: id,
|
|
assignee: assignee ? { id: assignee, name: assignee } : null,
|
|
release: null,
|
|
area: null,
|
|
labels: [],
|
|
commentCount: 0,
|
|
}) as unknown as IssueSummary;
|
|
|
|
const board = (): BoardColumn[] => [
|
|
{
|
|
status: 'TODO',
|
|
total: 1,
|
|
issues: [issue('a', 'TODO')],
|
|
},
|
|
{ status: 'IN_PROGRESS', total: 0, issues: [] },
|
|
];
|
|
|
|
describe('board reducers', () => {
|
|
it('moves a card optimistically', () => {
|
|
const next = moveIssue(board(), 'a', 'IN_PROGRESS');
|
|
expect(next[0]).toMatchObject({ total: 0, issues: [] });
|
|
expect(next[1].issues[0]).toMatchObject({
|
|
id: 'a',
|
|
status: 'IN_PROGRESS',
|
|
});
|
|
expect(next[1].total).toBe(1);
|
|
});
|
|
|
|
it('applies newer realtime versions and ignores stale ones', () => {
|
|
const moved = applyIssueChange(board(), issue('a', 'IN_PROGRESS', 2), null);
|
|
expect(moved[1].issues.map((i) => i.id)).toEqual(['a']);
|
|
|
|
const stale = applyIssueChange(moved, issue('a', 'TODO', 1), null);
|
|
expect(stale).toBe(moved);
|
|
});
|
|
|
|
it('drops issues that no longer match the filter', () => {
|
|
const next = applyIssueChange(board(), issue('a', 'TODO', 2, 'bob'), {
|
|
projectId: 'p',
|
|
assigneeId: 'ana',
|
|
});
|
|
expect(next[0].issues).toEqual([]);
|
|
});
|
|
|
|
it('adds new issues from other users', () => {
|
|
const next = applyIssueChange(board(), issue('b', 'TODO', 1), null);
|
|
expect(next[0].issues.map((i) => i.id)).toEqual(['b', 'a']);
|
|
});
|
|
});
|