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
We should handle informing the user when they receive the vouched badge as well as when they have it taken away. This should be done via an email sent through Ortto.
Currently we use an activity called project-verification that sends a verified-status variable - depending on the value of this variable we send a different email to the user. I've added two new conditions and emails that we can use for this purpose
vouched - triggers email for when a project becomes vouched
unvouched - triggers email for when a project become vouched
Note: If a project becomes verified and givbacks eligible in a single action we should ONLY send the GIVbacks eligible email
conversely, if a project loses it's badge either from rejection of its applicaiton or revoking it's givbacks eligible badge we should only send those email, not the "unvouched" email
steps needed to accomplish
- setup activity in ortto
- draft email for when project receives vouched badge in Ortto
- draft email for when project has lost vouched badge in Ortto
- setup activity trigger in BE when admin changes verified status of project
AC
Admin can change vouched/verified status of project from admin panel
when project receives vouched badge email is sent to project owner
when project has vouched badge removed an email is sent to project owner
when project has no vouched badge and receives both badges at once (givbacks & vouched badge) ONLY givbacks email is sent
when project has both badges and loses both in a single action, ONLY givbacks email is sent.
The text was updated successfully, but these errors were encountered:
We should handle informing the user when they receive the vouched badge as well as when they have it taken away. This should be done via an email sent through Ortto.
Currently we use an activity called
project-verification
that sends averified-status
variable - depending on the value of this variable we send a different email to the user. I've added two new conditions and emails that we can use for this purposevouched
- triggers email for when a project becomes vouchedunvouched
- triggers email for when a project become vouchedNote: If a project becomes verified and givbacks eligible in a single action we should ONLY send the GIVbacks eligible email
conversely, if a project loses it's badge either from rejection of its applicaiton or revoking it's givbacks eligible badge we should only send those email, not the "unvouched" email
steps needed to accomplish
AC
The text was updated successfully, but these errors were encountered: