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

Ouverte
#2,730 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
35/100
Type d'issue
Fonctionnalité
Clarté
Clairement spécifiée
Activité
Active
Stack technique
postgresql, rust

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
Rust
Étoiles
2
Forks
0
Merge moyen
9 h 48 min
PR mergées (30 j)
151

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de registrystack/registry-stack

Toutes les issues de registrystack/registry-stack

Issues similaires

Plus d'issues Rust

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.