Give a Blocked parent with open subtasks a way to unblock

Aperta
  • Qualcosa non va?
#405 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
csharp, openapi
Ambito
api, backend-api-design, full-stack

Direzione di ricerca

Read the linked issues #385, #387, #366, and #397, then bring the status rules to grooming: the issue leaves the behavior undecided. Once a rule is chosen, trace the parent status handling in the API, web app, and MCP assistant. Done means the chosen rule and the Blocked display behavior are consistent across all three, including the derived-status rule and #387 AC 18.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement

Follow-up to #385 and #387. Part of #366.

Problem

Since #385, a parent with open subtasks cannot have its status edited (TASK_PARENT_STATUS_DERIVED), and #387 AC 18 also removes Block and Unblock from such parents in the web app. A parent that is already Blocked when it gets an open child, or that has a Blocked state and open children, therefore has no unblock path on either the Tasks page or the journal.

Found while reviewing the #387 spec. #387 records it as a consequence of #385 and does not fix it.

Workaround

Complete or remove the open children, then unblock the parent.

To decide in grooming

Pick one rule, then apply it in the API, the web app and the assistant:

  • Allow Unblock (only) on a parent with open subtasks.
  • Clear the stored block when an open child is attached to a Blocked parent.
  • Something else, if grooming finds a better fit with the derived-status model.

Also decide what a Blocked parent shows while it has open children, and how this interacts with TASK_PARENT_STATUS_DERIVED and #387 AC 18.

Notes

  • API, web and MCP change. After the monorepo move (#397) so the change ships in one PR with the matching MCP change.
  • Do it before #243 changes the parent rules again.
  • Needs grooming first.
Lingua principale
C#
Stelle
1
Fork
0
Merge medio
2h 2m
PR unite (30g)
98

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di nevridge/TaskFlow

Tutte le issue di nevridge/TaskFlow

Issue simili

Altre issue su C#

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.