-
Notifications
You must be signed in to change notification settings - Fork 59
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
Account-Mailer - New Account notification includes acct number #18181
Comments
@pstemkens Can you please attach a screen shot of the current notification indicating that it is missing this account number? |
@JohnamLane , I created a new acct under BCROS BCREGA001 and it created a new acct but no notification was sent out. Email on file is riyazs2910@gmail.com. I contacted Riyaz and he said he has not received any notifications. I also checked with Ethan and could not find any notifications that reference the account number. |
Hey team! Please add your planning poker estimate with Zenhub @avni-work @hanlunBCRegistries @Jxio @lizhuomeng71 @ochiu @rodrigo-barraza @sameer0422 @seeker25 |
@JohnamLane Github ticket for email notification is referenced above. |
Added Figma link for wording reference. |
Issue is verified. please see attached screen shot |
Currently when a client uses BCeID or BCSC and chooses GOVN or GOVM account type an email is generated.
Sample email generated for BCSC users below which does not show account number:
Github ticket for email notification
https://github.com/bcgov/sbc-auth/blob/main/queue_services/account-mailer/src/account_mailer/email_templates/admin_notification_email.html
Notification should work for all account types and to include new account number.
GIVEN - client has requested new account
WHEN - client receives notification that new account has been approved.
THEN - notification that their account has been approved includes their account number
Figma design:
https://www.figma.com/design/NcchZlxVp502zeoiCLeMgi/Enhancements-for-Staff?node-id=2627-1398&t=l7n9zCZqe08D0i2c-4
The text was updated successfully, but these errors were encountered: