Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Schedule Pre-event notifications job 📆 #478

Open
tomas-salgado opened this issue Aug 24, 2024 · 4 comments · May be fixed by #506
Open

Schedule Pre-event notifications job 📆 #478

tomas-salgado opened this issue Aug 24, 2024 · 4 comments · May be fixed by #506
Assignees
Labels
Backend 🔌 This requires backend work (ie: DB, business logic). Feature 🚀 A new feature or improvement.

Comments

@tomas-salgado
Copy link
Collaborator

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).

@tomas-salgado tomas-salgado added Feature 🚀 A new feature or improvement. Backend 🔌 This requires backend work (ie: DB, business logic). labels Aug 24, 2024
@imnotrafa
Copy link

Can I take on this? @tomas-salgado

@gpolite0
Copy link
Contributor

I can take this too!

@tomas-salgado
Copy link
Collaborator Author

@imnotrafa just assigned you to #477, so I’m going to leave this one for @gpolite0

@rafa1510
Copy link
Contributor

Can I take this? Following up from the oyster channel on Slack

@gpolite0 gpolite0 removed their assignment Aug 29, 2024
@rafa1510 rafa1510 linked a pull request Sep 10, 2024 that will close this issue
9 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Backend 🔌 This requires backend work (ie: DB, business logic). Feature 🚀 A new feature or improvement.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants