[Tracking] Task details and Tasks page usability

Abierto
  • ¿Algo no está bien?
#427 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
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
28/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
csharp
Área
frontend, web-dev

Línea de trabajo

Read the linked issues #404, #421, #424 and #423, then inspect TaskDetailPage, the journal row in TodosSection, and TaskListRow to understand their shared changes. Start after the pipeline work listed in the issue; all four tasks need grooming, and #421 depends on a decision after #404. Done means each linked issue is closed or closed as not wanted with a one-line reason.

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

Descripción

tech-debt

Groups the web-only usability issues around the task detail page and the Tasks page. They share files (TaskDetailPage, the journal row in TodosSection, TaskListRow), so they are built in one order and rebase onto each other once. None changes the API or the assistant.

Order

Do this group after the monorepo pipeline work (#397: #398, then #411, #399 and #400), so these issues are the first web features built with the merged pipeline. They are not blocked on GitHub: only the order says so.

  1. #404 — Open task details from journal rows and return to the same day (done, PR #462; #408 changes the same journal row and is tracked in #366)
  2. #421 — Click-through edit screen on the Tasks page instead of the inline editor above a long list (needs grooming; decide now that #404 is merged, since it replaces the inline editor with the detail page and shares its back-link rule)
  3. #424 — Change a task's journal day from the task details (needs grooming; the API already accepts journalDate on update, #352; check how it relates to the due date)
  4. #423 — Find a task by ID in every task search (needs grooming; independent, the smallest, can go any time in this group)

Why this order

  • #404, #421 and #424 all change the task detail page. #404 changes its back link, #421 makes editing a click-through to it, and #424 adds the day field to it. Built in this order, each rebases onto the last.
  • #423 edits the search boxes only, so it does not conflict with the others.

Notes

  • #404 moved here from #366 (an issue has one parent). Its link to #408 stays: both change the journal row in TodosSection.
  • #422 (planned subtasks hidden in get_journal) is not here: it is an assistant output change, tracked in #420.
  • All four need grooming first.

Done when

All four are closed or closed as not wanted, each with a one-line reason.

Lenguaje dominante
C#
Estrellas
1
Forks
0
Merge medio
2 h 2 min
PR fusionados (30 d)
98

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 nevridge/TaskFlow

Todos los issues de nevridge/TaskFlow

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.