scheduling: let a person book, move and cancel their own appointments without a task grant

Ouverte
#2,729 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
25/100
Type d'issue
Fonctionnalité
Clarté
Clairement spécifiée
Activité
Active
Stack technique
openapi, postgresql, rust

Piste de recherche

Start with crates/registry-scheduling/src/store.rs, especially the is_managed_by behavior cited in the issue, and read the linked task grants documentation to understand the current authority model. Then trace the scheduling paths and PostgreSQL suite for booking, rescheduling, cancellation, caps, and managed appointments. Done means both authority paths meet the acceptance criteria, existing suites pass, scoped reads work, and the security page, OpenAPI document, clients, and CLI catalogue are updated.

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

Public-facing services need people to book for themselves with their own sign-in: registration appointments, exam sittings, clinics, information sessions, and activities with limited places. Today a person cannot book directly. Every commitment takes its authority from a task grant alone, and a trusted producer such as Casework mints those grants.

Current evidence

  • Task grants: "Every commitment takes its authority from the grant alone."
  • is_managed_by: a retained source manager replaces the creating actor. When an appointment has a manager, its owner can no longer act on it.

Proposed behaviour

  • A self-service commitment profile. A person's own verified token may hold, book, reschedule and cancel for themselves, within the exact service, location and action permissions the profile declares. No task grant is involved, and the task-grant path is unchanged.
  • The party is always the token subject. This path never books for someone else.
  • A cap per person: at most one active booking per person per window, and a configurable ceiling on active holds and bookings per person per offering. Hold lifetimes stay bounded, so one person cannot park capacity.
  • An appointment may also retain an institutional manager. The owner and that manager may both act on it, and nobody else may.
  • Eligibility stays with the service's source of record. Scheduling does not decide it.

Acceptance criteria

  • A person's token books, reschedules and cancels its own appointment under the profile.
  • The profile refuses, with distinct problem codes, a request for another party, a request outside the declared permissions, and a request above the cap.
  • Concurrent requests from one person cannot exceed the cap (PostgreSQL suite).
  • Task-grant bookings behave as before, and the existing suites pass unchanged.
  • On a managed self-service appointment, the owner and the retained manager can both cancel, and a third principal cannot.
  • Self-service appointments are reachable through scoped operational reads (#2337), so the notification journey proven in #2339 can find whom to notify.
  • The Scheduling security page records the second authority path, its abuse controls and its residuals. The OpenAPI document, clients and CLI catalogue are regenerated.

Delivery

Implemented in one PR with the displacement issue that follows this one, because once people own their bookings an institution needs a way to clear them when supply goes.

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.