Update custom RSVP closure logic: Enable cancellations and waitlist progression until 3.5h before event
维护者通常 1 天内回复
评估
调研方向
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.
由索引模型根据 Issue 内容生成。
描述
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.
- 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.
- 主要语言
- Ruby
- 星标
- 105
- 派生
- 206
- 平均合并
- 17 小时 2 分钟
- 30 天内合并 PR
- 69
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
codebar/planner 的其他 Issue
-
DashboardQuery eager-loads workshop_host with :sponsors in one join (same host-loss trap as #2975)未关闭
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
enhancement
难度 2/5 1-3 小时 新手友好度 76/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复
-
404 link in footer可能已有人在做 @SourindraNathBasak 于 2 天前认领。 未关闭good first issue sponsoring
难度 1/5 1 小时以内 新手友好度 18/100
codebar/planner#3004 · 2 条评论 ·
维护者通常 1 天内回复
-
Homepage shows deactivated chapters (sidebar fragment invalidation deletes the wrong key)可能已有人在做 @mroderick 于 4 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 30/100
codebar/planner#2993 · 1 条评论 ·
维护者通常 1 天内回复
相似的 Issue
-
area/web interface
难度 2/5 1-3 小时 新手友好度 62/100
mastodon/mastodon#41009 · 2 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
yegor256/ellipsized#131 ·
-
难度 2/5 1-3 小时 新手友好度 85/100
-
难度 2/5 1-3 小时 新手友好度 78/100