Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Should an IN_PROGRESS case still receive automated outreach? (the two readers left on OPEN-only by #551)

Cerrado
  • ¿Algo no está bien?
#552 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
typescript
Área
backend

Línea de trabajo

Start with backend-ts/src/case/outreach-campaign.ts and backend-ts/src/mcp/tools.ts, then read docs/DATA_MODEL_CONTRACTS.md §4 and the context from #551. Resolve whether IN_PROGRESS cases should receive outreach and be attached to compliance answers, including the future-appointment option if considered. Done means the product decision is implemented consistently and recorded in §4.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

backend owner-ops question

The question

Should a case an operator has already picked up (IN_PROGRESS) still be targeted by automated outreach, and still be the case attached to an MCP compliance answer?

This is a product decision, not a bug. It is filed so the inconsistency is tracked rather than left in a journal entry.

Why it comes up now

#551 widened the open-case readers to ACTIVE_CASE_STATUSES (OPEN + IN_PROGRESS), because the work list, its CSV export and the MCP list tools disagreed with each other: a case moved to IN_PROGRESS stayed on screen and vanished from the CSV taken off that screen.

Two readers were deliberately left on OPEN only, because neither is the work list and widening them would change behaviour nobody asked for:

  • backend-ts/src/case/outreach-campaign.ts — campaign targeting
  • backend-ts/src/mcp/tools.ts — the open case attached to a get_compliance_status answer

Recorded in docs/DATA_MODEL_CONTRACTS.md §4.

The two readings

Leave as-is (OPEN only). Someone has already started work on the case — a scheduled appointment is the usual reason it is IN_PROGRESS. Sending an automated letter on top of that is duplicate contact, and the patient hears from the practice twice about the same gap.

Widen to ACTIVE. ACTIVE_CASE_STATUSES is the contract's own definition of an active case, and every other surface now uses it. A case sitting IN_PROGRESS for six weeks because an appointment was booked and missed receives nothing at all under the current behaviour.

A third option: widen, but exclude cases with a future appointment — which is a real distinction the appointment store can already answer, and more work than either of the above.

Deciding it

Whichever way it goes, the outcome belongs in DATA_MODEL_CONTRACTS §4 next to the note that records the current split, so the next person to widen a status set knows these two were considered rather than missed.

Context: #551, docs/JOURNAL.md 2026-09-12.

Lenguaje dominante
TypeScript
Estrellas
0
Forks
0
Merge medio
4 h 5 min
PR fusionados (30 d)
126

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de Taleef7/workwell

Todos los issues de Taleef7/workwell

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.