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
This issue is dependent on #477.
(However, the logic is entirely separate from that issue, so it is possible to work on the PR for this issue before #477 is ready. We just need to make sure #477 is merged first!)
Description
#477 implements a function that sends pre-event notifications to members. However the function isn't being utilized anywhere, so we need to schedule this job. Additionally, we need to ensure that when an event is deleted, this job is also removed from the queue.
Acceptance Criteria
When an event is created, we should schedule a Bull job that calls the function from #477. We want to add to the createEvents function. Specifically, after creating the event, we want to call the job to send an email notification, and then save the job ID within a database field.
Currently, there is no field in the events table for storing this job ID, so that new field needs to be created using a database migration (see docs).
The text was updated successfully, but these errors were encountered:
This issue is dependent on #477.
(However, the logic is entirely separate from that issue, so it is possible to work on the PR for this issue before #477 is ready. We just need to make sure #477 is merged first!)
Description
#477 implements a function that sends pre-event notifications to members. However the function isn't being utilized anywhere, so we need to schedule this job. Additionally, we need to ensure that when an event is deleted, this job is also removed from the queue.
Acceptance Criteria
When an event is created, we should schedule a Bull job that calls the function from #477. We want to add to the createEvents function. Specifically, after creating the event, we want to call the job to send an email notification, and then save the job ID within a database field.
Currently, there is no field in the events table for storing this job ID, so that new field needs to be created using a database migration (see docs).
The text was updated successfully, but these errors were encountered: