You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On the auditions form, when selecting Yes or No, for either EXP or TECH interest, the response is recorded for each specific dancer. After that, each request must be individually processed, which takes a great deal of time and may not be very practical for semesters when there are a lot of dancers.
Reproducing the bug:
On localhost:3000/audition, create a new dancer with exp / tech interest.
On localhost:3000/admin/dancers, view the new dancer that is created, and you can see what the dancer had chosen for each interest.
Solution:
When dancers are finished auditioning, we should implement a one-click option or even an automatic option to send out the corresponding emails for each interest. We could do this through a simple script that parses through our database and selects those emails that correspond to dancers with interest, along with a webhook that triggers our email notifications.
The text was updated successfully, but these errors were encountered:
Issue:
On the auditions form, when selecting Yes or No, for either EXP or TECH interest, the response is recorded for each specific dancer. After that, each request must be individually processed, which takes a great deal of time and may not be very practical for semesters when there are a lot of dancers.
Reproducing the bug:
On localhost:3000/audition, create a new dancer with exp / tech interest.
On localhost:3000/admin/dancers, view the new dancer that is created, and you can see what the dancer had chosen for each interest.
Solution:
When dancers are finished auditioning, we should implement a one-click option or even an automatic option to send out the corresponding emails for each interest. We could do this through a simple script that parses through our database and selects those emails that correspond to dancers with interest, along with a webhook that triggers our email notifications.
The text was updated successfully, but these errors were encountered: