Create job to send mass SMS notifications 👥

colorstackorg / oyster

Monorepo that houses ColorStack's core product software.

MIT License

289 stars 146 forks source link

Create job to send mass SMS notifications 👥 #472

Open tomas-salgado opened 3 months ago

tomas-salgado commented 3 months ago

Description

We want to create a job that takes all the existing phone numbers in the database and sends a text notification utilizing Twilio.

Acceptance Criteria

The job should take in an array of phone numbers and a message
The job should send an SMS message to all phone numbers with the given message

Additional Context

We will want to add this code within a new directory named twilio within the path packages/core/src/modules.

This will be the first integration of Twilio with Oyster(!) so this will require some research-here are the Twilio docs. Feel free to check out the Slack use-cases to see examples of Slack jobs.

Habeebah157 commented 3 months ago

I would like to do this one.

Habeebah157 commented 3 months ago

Hello, I am not sure if I am checking wrong but phone numbers would be under students right? Like the students numbers. I do it as one of the students fields. I also tried searching phone number in the codebase to give me a clue of what it could be but could not find it. There is nothing like phone number in the oyster channel on slack either.

tomas-salgado commented 3 months ago

Just left a comment about this in your Slack message, but basically PR is partly dependent on issue #477, since that issue will add the field phone_number to the database. While that is still in progress, you can add the field locally by adding the migration script here (which is from the PR that's up for issue #477).

wflore19 commented 2 weeks ago

Are there any updates on this issue @Habeebah157 ? I'd like to help

Boris713 commented 1 week ago

tomas-salgado commented 1 week ago

Assigning this to @wflore19!

wflore19 commented 5 days ago

@Boris713 wanna pair program on this issue?

Boris713 commented 9 hours ago

@wflore19 I'm down if you are

wflore19 commented 6 hours ago

@Boris713 Habeebah finished this issue and is submitting a pull request

Habeebah157 commented 4 hours ago

What is it now, are you guys still doing it? Is it still assigned to me? I can still make a pull request right? Sorry I am just seeing this.

tomas-salgado commented 4 hours ago

@Habeebah157 it seems like the others haven't started working on it. If you've already finished this feel free to put up your PR!

Habeebah157 commented 3 hours ago

Usually how much time are we allowed to spend on an issue before it is transferred to someone else? I was not aware there was a time constraint or anything

tomas-salgado commented 3 hours ago

The ideal timeframe is about 3-4 weeks, after which the issue will be reassigned

Habeebah157 commented 3 hours ago

Oh, ok. Thank you. I was not aware of that. Sorry it took so long. I will try to make a pull request asap