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

Add support for email templates #3

Open
zachmarshall opened this issue Jan 31, 2024 · 3 comments
Open

Add support for email templates #3

zachmarshall opened this issue Jan 31, 2024 · 3 comments

Comments

@zachmarshall
Copy link
Contributor

No description provided.

@Raajheer1
Copy link
Contributor

Email Notifications:

Transfer Request:
When a user submits a transfer request to a new ARTCC multiple emails need to get sent.
Email should be sent to the user that the transfer request is send and pending and they should expect something in 48 hours.
Email should be sent to the user when the request is accepted or denied
Email should be sent staff (ATM and DATM) of the originating ARTCC that a user has requested to transfer out, and to the destination ARTCC that a request has been submitted.

^ Same but for visiting requests
Taddler email:
Notification to staff if transfer/visiting request has sat for more than 7 days send another email

User added to roster:
After completing the academy a user can choose their starting facility, similar to above that facility staff should get an email that a new user has joined.

User removed from facility:
Send an email to the user that they have been removed X facility
Send an email to the division staff that X user has been remvoed from their roster (just in case they weren't the ones to remove them, say USA staff removes them for disciplinary issues)

Feedback Emails:
Send an email to the pilot that their feedback has been submitted.
Send an email to ARTCC Staff (ATM, DATM, and TA) that pending feedback has been received for a controller in their facility (maybe if its poor feedback send it to USA3 as well)
Once feedback gets approved send email to the controller that they received feedback.

ARTCC User missing operating initials
When a user joins a facility they get operating initials, the code attempts to generate these initials based on their set preference and falls back to their actual initials in my case (RP) if the preferred initials are not available however if neither of these are available it doesnt set any initials. This email should go to the ARTCC staff (ATM/DATM) stating that a user has no initials so the staff can set them manually.

News Emails:
Division news email not entirely sure how I want to do this yet as i dont want people to get spammed with all the news that goes out right now.

Upcoming Events for the month:
Send an email on the 1st of the month to everyone who ops in with a list or calendar with all the events for the month.

Event Signs Up:
Send an email to a controller if they're signed up for an event 24 hours before the event (reminder email)
Send an email to a controller if they've been assigned to a position for an event.

Neighboring ARTCCs have events coming up:
Say ZDV (Denver) has an event this month send an email to all the neighboring ARTCCs notifying/reminding them about it.

Training Sessions coming up:
Send an email to the student and mentor/instructor reminding them of an upcoming session
Send an email to the student/controller that a session has been scheduled

Training Note put in:
Send a email to the student that a training note has been entered for them (maybe with a link to it)

Training Note Missing:
Reminder email for mentor/instructor if they number of training sessions they've had in the last 24 hours doesnt equal the number of training notes they've entered.

Email to Groups:
Easy way to send emails to people of any group, groups could be:

  • All members of a facility
  • Staff at a facility
  • Training staff at a facility
  • Everyone in the division
  • All ATMs, DATMs, TAs, ECs, WMs.
  • Etc.

Disciplinary Log entry:

  • Sends to senior staff and VATUSA1 and VATUSA2 that an entry has been made for X user

Facility Welcome Emails:
Allow ATMs/DATMs to set predefined "welcome emails" that go to controllers as soon as they join the ARTCC

Activity Warning Emails:
Send to controllers who have not met the monthly/quarterly minimum activity for the ARTCC and are at risk of removal.
Should be something like "You have not met the activity requirements for ZDV, control x hours by x date in order to avoid being removed"

@BMWENING
Copy link

Link to current email templates:
https://github.com/VATUSA/current/tree/master/resources/views/emails

@Raajheer1
Copy link
Contributor

Email to staff on role changes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants