Josep Piguillem
f2001aca88
Formatted text
- Descriptions, comments, replies and release notes render Markdown,
sanitised with DOMPurify (tested against scripts, handlers and
javascript: links). A pasted image is uploaded and written as
; the web fetches it with the reader's session,
so it works on private projects. Every text box has a preview. The
attachment upload now answers its attachmentId.
List view
- /p/:key/list: every ticket as rows, sortable by any column, filtered by
text, open/closed, type, priority and assignee; status, priority and
assignee change in place; bulk edit (the backlog's bar, now shared).
Ticket details
- Reactions on comments (GitHub's eight), for members and viewers.
- Duplicate a ticket: what it says, not where it stands.
- blockedBy: open tickets it waits for (BLOCKS / DEPENDS_ON), worked out
when reading with one query per board or page; shown on cards, list
rows and the ticket.
Public proposals
- A public project can take bug reports and ideas from anyone
(acceptsProposals): POST /api/explore/projects/{project}/proposals and
the form at /p/:key/proponer. They become tickets labelled «propuesta»,
opened by TaskStream; a honeypot field and 5 per address every 15
minutes keep spam out. No e-mail is asked: it would be public.
Votes
- Anyone signed in votes on a public project's tickets, members on a
private one (voteIssue, PUT/DELETE /api/issues/{issue}/vote): votes and
voted on each ticket, buttons on the ticket and the roadmap, a column
in the list. The showcase carries votes and the open proposals.
MCP: vote_issue, duplicate_issue, react_to_comment; listings show
blockers and votes. Docs, Word and PDF updated; chat notifications
(Discord, Slack, Telegram) noted for later.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Documentación de TaskStream
TaskStream es una alternativa a Jira para equipos de desarrollo: proyectos, tickets (bugs, features, cambios de UI, tareas, QA), releases, comentarios y relaciones entre tickets, todo en tiempo real.
| Documento | Para qué |
|---|---|
| 1. Visión general | Qué hace el producto, stack y estructura del monorepo |
| 2. Arquitectura | Hexagonal, CQRS, event sourcing, flujo escritura → lectura y tiempo real |
| 3. API | Dominio (agregados, workflow, eventos) y la API GraphQL |
| 4. Cliente web | Angular, NgRx Signals con eventos, GraphQL y @pi/ui |
| 5. Autenticación | Pireon: tokens, login en el navegador, sesiones y webhooks |
| 6. Desarrollo | Puesta en marcha, comandos, tests y cómo añadir una funcionalidad |
| 7. Despliegue | Docker, variables de entorno y escalado |
| 8. Decisiones | Por qué está hecho así (y qué alternativas se descartaron) |
| 9. Servidor MCP | Usar TaskStream desde asistentes de IA (Claude…): herramientas y conexión |
Cada librería de libs/ tiene además su propio README.md con su responsabilidad y su contenido.
Ideas para más adelante
- Avisos a Discord, Slack o Telegram: los webhooks salientes mandan JSON en bruto, que esos chats no muestran bien. Una integración por canal (o un formato por destino en los webhooks) mandaría mensajes ya legibles: «Ana movió WEB-12 a En revisión», con enlace.
Empezar rápido
docker compose up -d --build # web en http://localhost:8080
Para entrar hacen falta dos clientes OAuth de Pireon en .env (authorization_code y password, ver
Autenticación).