Update custom RSVP closure logic: Enable cancellations and waitlist progression until 3.5h before event
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 45/100
Línea de trabajo
Start by locating the custom RSVP closing-time logic and the cancellation, waitlist progression, and notification paths; the issue does not name specific files or tests. Read those entry points and their existing tests first. Done means new joins remain blocked after RSVP closure, cancellations and automatic waitlist promotion with email continue until 3.5 hours before the event, and all these changes stop at that cutoff.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Description of the issue 📄
Because of strict Centralised Security rules at our London corporate hosts, we must send a final guest list in advance for ID checks. To handle last-minute cancellations without extra manual work, we now send both the main list and the waiting list to security. This way, everyone on either list is already approved to enter.
We are using the new Customised RSVP closing date and time feature to help with this process, but we need to adjust how it works. Once RSVPs close, the system should stop new people from joining, but still let the pre-cleared waitlist automatically fill any cancellations until a final cutoff 3.5 hours before the event.
Current Behavior
When the custom RSVP closing date/time is reached, the system successfully blocks new users from joining the main list or waiting list. (This must be maintained).
New Requirements
- Maintain Current Block: Keep blocking new users from joining the main list or waiting list once the custom RSVP closing time has passed.
- Enable Post-Deadline Cancellations (New): Allow users already on the main list to cancel their spot even after the RSVP deadline has passed.
- Enable Post-Deadline Auto-Progression (New): If someone cancels their spot after RSVP closure, the system should automatically move the next person on the waiting list to the main list. The person moved to the waiting list should receive an email.
- Hard Lockdown at T-Minus 3.5 Hours (New): Exactly 3.5 hours before the workshop starts, the system should freeze. No more cancellations or waitlist changes are allowed, so the attendee list is final.
- Lenguaje dominante
- Ruby
- Estrellas
- 105
- Forks
- 206
- Merge medio
- 1 d 1 h
- PR fusionados (30 d)
- 78
Preparar el entorno
- Incluye un Dockerfile o un archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de codebar/planner
-
DashboardQuery eager-loads workshop_host with :sponsors in one join (same host-loss trap as #2975)Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
Los mantenedores suelen responder en 1 día
-
Homepage shows deactivated chapters (sidebar fragment invalidation deletes the wrong key)Posiblemente ocupada @mroderick la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 30/100
codebar/planner#2993 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Dificultad 4/5 3-5 días Aptitud para principiantes 30/100
Los mantenedores suelen responder en 1 día
Todos los issues de codebar/planner
Issues similares
-
[KLayout][DRC] Gat.b1 only checks gate regions, misses facing 3.3 V poly end caps (Figure 5.6)Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
IHP-GmbH/IHP-Open-PDK#1266 ·
Los mantenedores suelen responder en 2 días
-
Add ZammadPosiblemente ocupada @Arslan-TR la tomó hoy. Abiertorequest
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
endoflife-date/endoflife.date#11298 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
performance v/6
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
WITCodingClub/calendar-backend#689 ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 1/5 Menos de una hora Aptitud para principiantes 86/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
rubys/roundhouse#571 ·
Los mantenedores suelen responder en 1 día