Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Registration Instance - Reminder Sent flag persists #6088

Open
2 tasks done
stevelipinski opened this issue Nov 16, 2024 · 0 comments
Open
2 tasks done

Registration Instance - Reminder Sent flag persists #6088

stevelipinski opened this issue Nov 16, 2024 · 0 comments
Labels
Status: Confirmed It's clear what the subject of the issue is about, and what the resolution should be. Type: Bug Confirmed bugs or reports that are very likely to be bugs.

Comments

@stevelipinski
Copy link

Description

The Reminder Sent flag on a Registration Instance persists when a Registration Instance is copied.

This is somewhat unexpected behavior because if you are creating a new Instance (the copy), and the source Instance has the Reminder Sent flag set, the flag remains set on the new Instance. However, the reminders haven't been sent for that new Instance.
Users can easily miss this setting.

Actual Behavior

Copy a Registration Instance where Reminder Sent flag is true - the Reminder Sent flag remains true on the new instance/copy.

Expected Behavior

One of two things would make this a better experience:

  • Preferably, if the Send Reminder Date is changed on a Registration Instance to be a date/time in the future (ahead of "current time"), either unset the Reminder Sent flag automatically, or pop-up a dialog to the user asking if they want to uncheck it.
  • Alternately, simply uncheck the Reminder Sent flag during a copy of a Registration Instance.

(The first option covers some additional use-cases that may be useful)

Steps to Reproduce

  • Go to Tools -> Event Registration
  • Select a Registration Instance where Reminders have already been sent - Reminders Sent flag is visible and checked. (Alternately make it appear so by setting the flag via SQL).
  • Copy the Registration Instance
  • See the flag is still set on the copy.
  • Change the Send Reminder Date to something in the future
  • See the flag is still set.

Issue Confirmation

  • Perform a search on the Github Issues to see if your bug or enhancement is already reported.
  • Reproduced the problem on a fresh install or on the demo site.

Rock Version

16.6

Client Culture Setting

en-US

@sparkdevnetwork-service sparkdevnetwork-service added Status: Confirmed It's clear what the subject of the issue is about, and what the resolution should be. Type: Bug Confirmed bugs or reports that are very likely to be bugs. labels Nov 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Confirmed It's clear what the subject of the issue is about, and what the resolution should be. Type: Bug Confirmed bugs or reports that are very likely to be bugs.
Projects
None yet
Development

No branches or pull requests

2 participants