AletheiaFact / AletheiaFact/aletheia

Enhancement: Add history creation for Triage steps

Abierto
#2,244 0 comentarios 0 reacciones 0 asignados Ver en GitHub
tech
Lenguaje dominante
TypeScript
Estrellas
55
Forks
20
Merge medio
2 d 6 h
PR fusionados (30 d)
2

Descripción

### Background Information
We already have a functional tracking page that renders all steps correctly. The only current limitation is the "In Triage" step, which does not display a date because we are not creating histories for that step yet.

Because of this, the tracking page cannot retrieve the timestamp for when the verification request entered "In Triage" and falls back to rendering a feedback message informing the user that the date could not be found.

We need to ensure that all important Triage actions generate histories so the tracking flow behaves consistently and relies on real data instead of UI fallbacks.

The following actions should create histories:
- Define personality → create history
- Define topic → create history
- Define impact area → create history
- Define severity → create history
- Verification request status change to "In Triage" → create history

### How
To implement and validate this:

- Run the automated triage system to trigger the Triage flow
OR
- Manually execute the required requests using Insomnia/Postman

After performing the actions, confirm that the corresponding histories are created for each step listed above.

For testing via the tracking page, it is required that at least the status history from **"In Triage" → "Pre Triage"** is created, since the tracking page depends on these histories to render the timeline correctly.

### Expected Behavior
All relevant Triage actions generate histories consistently.

The tracking page should receive proper history data for the "In Triage" step, including the correct date, and render the timeline based on real status/history events instead of displaying fallback feedback messages to the user.

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.