Josep Piguillem
93d028e870
«Pedir revisión» on a ticket asks a member (with an optional note): they
are notified and see it under «Te piden revisión» in my work until they
answer «Todo bien» or «Pedir cambios» (with what to change) from the
ticket's Revisiones box; whoever asked hears the answer and can withdraw
an open request. Events of the ticket (requested, answered, cancelled),
so they show in its history and the activity feed. Viewers can be asked
and answer; not oneself, nor twice the same person with one pending.
API: requestReview / answerReview / cancelReview, Issue.reviews,
myIssues(reviewing); POST /api/issues/{issue}/reviews,
POST …/reviews/{id}/answer, DELETE …/reviews/{id}. MCP: request_review,
answer_review, my_issues reviewing.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
web-tracker-domain
Modelo del tracker en el cliente.
- Import:
@task-stream/web/tracker/domain - Capa:
domain· Tags:scope:web-tracker,type:domain
Contenido
- Modelos (
Project,IssueSummary,Issue,Release…), enums e inputs. - Configuración por proyecto (
ProjectSettings,StatusCategory) yWorkflow: nombres, colores, iconos, categorías, transiciones permitidas y estados que piden motivo, con un nombre legible para ids que ya no están configurados. - Estadísticas (
ProjectAnalytics,ReleaseBurnup). - Puertos:
ProjectsGateway,IssuesGateway,CommentsGateway,ReleasesGateway,ActivityGateway,UsersGateway,TrackerRealtimeGateway.
Comandos
npx nx lint web-tracker-domain
npx nx test web-tracker-domain # Jest
Reglas de dependencia entre capas: Arquitectura.