Opened 10 years ago
Closed 8 years ago
#920 closed enhancement (fixed)
Send e-mails to custom segments in CampTix Notify
Reported by: | kovshenin | Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Component: | WordCamp Site & Plugins | Keywords: | needs-testing |
Cc: |
Description
One of the features we were asked to develop for CampTix is the ability to e-mail attendees based on custom segments using the Notify section in Tickets - Tools. This will allow organizers to get in touch with very specific groups of peoples, such as those who opted in for vegetarian lunch, or those who selected women's XS t-shirt size.
I pushed the first pass to the notify-segments branch on GitHub: https://github.com/Automattic/camptix/tree/notify-segments
It currently supports segmenting only be ticket type (like the original interface) as well as the ticket purchase date. Feel free to give it a spin and let us know if you encounter any bugs or have any questions. We'll be adding other segment fields soon and launch this on WordCamp.org after another round of testing.
Thanks!
Change History (7)
#3
@
10 years ago
Added select-type questions to fields available for segmenting in ed8db76050b993642c85d7aeff2371a132a2942e
#6
@
8 years ago
I was coming here to suggest this very thing. Our particular use-case was: emailing all of our volunteers or speakers (we usually have about 40 of each), based on the coupon they used. Easier than keeping a separate email list outside of Camptix. I can also see the "email vegetarians" or other options being potentially useful as well. Any chance this can be moved forward? Thanks!
#7
@
8 years ago
- Resolution set to fixed
- Status changed from new to closed
emailing all of our volunteers or speakers (we usually have about 40 of each), based on the coupon they used. [...] I can also see the "email vegetarians" or other options being potentially useful as well.
Those should be be possible already. It looks like this was just never updated once the code was deployed.
Closing, since it looks like everything has already been merged, but let me know if I'm missing something.
#574 has some related work that might be able to be used.