mars
MARS-281
Unify JTP and Ayudante: identical roles app-wide (caps + UI)
Done high
unassigned
⛔ awaiting elazar
Questions
UI labels: keep 'JTP / Ayudante' visible distinction, or single 'Docente' label?
keep JTP/Ayudante
/administrar/docentes detail: keep slot label distinguishing JTP vs Ayudante (informational), or collapse to 'Docente'?
Distinguish
studentAssignments.ayudanteUserId existing rows: leave as legacy (UI stops writing new), or one-time migrate ayudanteUserId→jtpUserId where jtpUserId is null?
students should be able to select jtp and ayudante in practica still
schema long-term: keep both jtpUserId+ayudanteUserId FK columns, or future migration to one column?
keep separate same caps and all that.
report-export-scope.ts 'jtp' filter param: drop, rename to 'docente', or keep for saved-URL backwards-compat?
yes, do not rename to docente, use JTP/Ayudante
Activity
-
wi cli
-
q#4 to=elazar: UI labels: keep 'JTP / Ayudante' visible distinction, or single 'Docente' label?
-
awaiting elazar
-
q#5 to=elazar: /administrar/docentes detail: keep slot label distinguishing JTP vs Ayudante (informational), or collapse to 'Docente'?
-
awaiting elazar
-
q#6 to=elazar: studentAssignments.ayudanteUserId existing rows: leave as legacy (UI stops writing new), or one-time migrate ayudanteUserId→jtpUserId where jtpUserId is null?
-
awaiting elazar
-
q#7 to=elazar: schema long-term: keep both jtpUserId+ayudanteUserId FK columns, or future migration to one column?
-
awaiting elazar
-
q#8 to=elazar: report-export-scope.ts 'jtp' filter param: drop, rename to 'docente', or keep for saved-URL backwards-compat?
-
awaiting elazar
-
q#4: keep JTP/Ayudante
-
q#5: Distinguish
-
q#6: students should be able to select jtp and ayudante in practica still
-
q#7: keep separate same caps and all that.
-
q#8: yes, do not rename to docente, use JTP/Ayudante
-
JTP and Ayudante unified app-wide: caps + UI revert + 4 view eq's + orphan dedup. audit-ca PASS
feat
2026-05-08
6w ago
2026-05-08 10:09