Skip to content

Edit bulk payment attendees until connected to a registrant#2007

Draft
maebeale wants to merge 3 commits into
mainfrom
maebeale/editable-bulk-payment-members
Draft

Edit bulk payment attendees until connected to a registrant#2007
maebeale wants to merge 3 commits into
mainfrom
maebeale/editable-bulk-payment-members

Conversation

@maebeale

@maebeale maebeale commented Jul 22, 2026

Copy link
Copy Markdown
Collaborator

🤖 suggested review level: 3 Read 📖 contained new edit/update flow on the public bulk-payment surface plus email variants

What is the goal of this PR and why is this important?

  • Bulk-payment attendees ("members") could never be edited after submission — a typo'd name meant the attendee never matched a registrant and couldn't be allocated to.
  • Payers (and admins) can now edit the attendee list from a single public edit page, and both the payer and staff are notified of the change.

How did you approach the change?

  • New public, slug-based edit/update actions on Events::BulkPaymentsController, reusing the existing bulk-payment-attendees Stimulus controller.
  • Attendees already connected to an active registrant (via the existing matched_attendees fuzzy match) render read-only but stay removable; unmatched rows are editable and new rows can always be added.
  • "Edit attendees" entry points added everywhere the list shows: the ticket, the submission page, and the admin dashboard card (admins land on the same public page).
  • On save:
    • the payer gets an updated confirmation email — distinct subject/heading + an "Updated on " line — so it reads as a change, not a duplicate;
    • staff get an updated FYI ("Pay for Other(s) data changed").
  • Both FYI emails (new submission + updated) now link to the payer's payment ticket instead of the submission page.

Anything else to add?

  • New notification kinds: bulk_payment_confirmation_updated, bulk_payment_confirmation_updated_fyi.
  • Model, request, and mailer specs added; mailer previews added; page_bg_class mapping registered.

Payers (and admins, routed to the same public page) can edit the attendee
list on a bulk payment submission. Attendees already matched to an active
registrant render read-only but stay removable; new attendees can always be
added. Saving re-sends the payer an "updated" confirmation email that reads
as a change, not a duplicate of the original.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings July 22, 2026 11:57

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings July 22, 2026 11:59

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

@maebeale
maebeale marked this pull request as ready for review July 22, 2026 12:36
@maebeale
maebeale marked this pull request as draft July 22, 2026 12:36
Editing the attendee list now also sends staff an "updated" FYI so they know
the Pay for Other(s) data changed. Both the new-submission and updated FYI
emails now link to the payer's payment ticket instead of the submission page.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings July 22, 2026 12:42

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants