scheduling: withdrawing supply cancels the bookings it displaces, with a reason, and notifies their owners

Aperta
#2,730 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
35/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
postgresql, rust

Direzione di ricerca

Read the scheduling guide at docs/site/src/content/docs/operate/scheduling.mdx and the authorization and cancellation paths in crates/registry-scheduling/src/store.rs. Then trace records apply, preview impacts, capacity transactions, cancellation intents, observer events, and audit handling to understand the scope. Done means meeting the acceptance criteria, including idempotency and the security page update; the issue requires delivery in the same PR as #2729.

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

Descrizione

area:scheduling criticality:p2 enhancement triage:needs-implementation

Use case

Offices close, staff fall ill, and sessions or activities are cancelled. When supply goes, the bookings on it must end in a way the person hears about. Today nobody can clear them reliably, and once people book for themselves (#2729) an institution has no path at all.

Current evidence

  • Absences and closures block new admissions, but "Existing bookings and holds are not cancelled or reassigned." The operator is told to arrange an authorised cancellation.
  • Only the booking's owner, or its retained manager, may cancel (is_managed_by), and nobody may once the cancellation cutoff has passed (cancel_appointment).
  • records apply refuses to move, remove or shrink a window below its live holds and appointments. That stops silent loss, but leaves no supported way to withdraw the window.

Proposed behaviour

  • The authority that publishes supply may withdraw it explicitly. An operator does so through records apply with a named option, never as a side effect. A source system does so through its source profile (a later issue).
  • Withdrawal cancels each affected appointment and releases each affected hold in the same capacity transaction, with a reason, whatever the cancellation cutoff. It records which authority displaced them.
  • Each displaced appointment produces the ordinary cancellation intent, which carries the reason, and the appointment.cancelled observer event. The existing notification journey (#2339) then tells the owner.
  • Without the explicit option, today's refusal stays.
  • Preview lists the bookings a withdrawal would displace, with counts and identifiers and no owner identity, in the style of resourceImpacts.

Acceptance criteria

  • An operator withdraws a window, or adds a closure, over live bookings inside the cutoff. The affected appointments are cancelled with the reason, and each emits one cancellation intent and one observer event.
  • The same apply without the option is refused as today.
  • Preview reports what would be displaced and changes nothing.
  • Replaying the same withdrawal is idempotent.
  • The audit records the displacing authority and the number of bookings displaced.
  • The Scheduling security page records the displacement power and who holds it.

Delivery

Implemented in the same PR as #2729.

Lingua principale
Rust
Stelle
2
Fork
0
Merge medio
9h 48m
PR unite (30g)
151

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 registrystack/registry-stack

Tutte le issue di registrystack/registry-stack

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.