Skip to content

🐛Attendees placing an order for multiple tickets under their own name only recieve one ticket email #883

@phtaylor

Description

@phtaylor

Describe the bug
We recently hosted an event using Hi.Events, and this bug was a plague.
I have reproed this several times on various deployments of Hi.Events, so I am sure its current.

Let me explain...
An attendee may be purchasing tickets for themselves and several friends. They go through the ticket purchase process, but they use thier own email for all the different tickets. They probably plan to forward the tickets to friends later... This happens all the time. People are in a hurry, maybe have been delegated the task of aquiring tickets for a group and don't have the details for the group members.

I just reproed again the issue.

I ordered 7 tickets for myself.
See the emails I recieved.
Image

The order cofirmation email. *Note: there is a link in that email to view all the tickets.
Image

There is an email for the first ticket, but no other tickets. The only way to get to the other 6 tickets is via the link in the 'Order Confirmation' email.

Image

guests were constantly mailing us to ask where the other tickets were, and if I manually resent the ticket emails, they were recieved.

To Reproduce
Steps to reproduce the behavior:

  1. Purchase multiple tickets under the same email address
  2. See only 1 ticket email revieved.

Expected behavior
A clear and concise description of what you expected to happen.

I would expect one email for each ticket, that can then be manually forwarded to other people.

Hi.Events Version and platform
Please state the version of Hi.Events you are using and what platform it is hosted on. Local, Docker etc.

Tested on both our own deployment of Hi.Events and the SAAS version.

Additional context
Add any other context about the problem here.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions