scheduling: withdrawing supply cancels the bookings it displaces, with a reason, and notifies their owners
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
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
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 applyrefuses 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 applywith 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.cancelledobserver 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
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di registrystack/registry-stack
-
area:breg enhancement
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
registrystack/registry-stack#2765 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 62/100
registrystack/registry-stack#2761 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
registrystack/registry-stack#2743 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
registrystack/registry-stack#2706 ·
I maintainer di solito rispondono entro 1 giorno
-
macOS contributor gates: Messaging config tests fail under the symlinked macOS temporary directoryAperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 83/100
registrystack/registry-stack#2704 ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di registrystack/registry-stack
Issue simili
-
[Bug] 建议把黑白主题设置同步到启动页面Apertabug
Difficoltà 2/5 1-3 ore Idoneità per principianti 66/100
AstrBotDevs/AstrBot-desktop#197 ·
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 75/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 82/100
stackabletech/airflow-operator#898 ·
I maintainer di solito rispondono entro 1 giorno
-
2 advisory ignore entries no longer match anything (`bytes`, `time` already patched in `Cargo.lock`)Forse già presa @zyl71 l’ha presa oggi. Aperta
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 88/100