Reminders

[valeriagrazzini]

created 3 types of cases:

• Account created but no Tokens or Collectibles (Email with tips on how to deploy assets)
• Account and tokens / collectibles created but no pools to start using features (Email with tips on how to config pool)
• Pool created for tokens / collectibles but no withdrawals for that pool (Email with tips on how to config rewards etc)

the email template has been created, only the final title/text need to be implemented.

[peterpolman]

@valeriagrazzini Hey! Please use normal casing for comments or remove your notes when publishing the PR :)

[peterpolman]

@valeriagrazzini We need to keep track of who we have mailed somehow. I'll add a task for that to refine.

Perhaps we already noticed this during refinement, but currently we will be spamming people every week with the same email when they meet the email conditions.

[peterpolman]

• Add new collection "TransactionalEmails"
• Add new schema TransactionalEmail

TransactionalEmail {
  type: string, // 'account_no_erc20_no_erc721'
  sub: string, // '123455'
}

• Move 3 email conditions into separate agenda jobs
• Make sure to choose good job name constants
• Before sending the email check how many TransactionalEmail objects exist for the job specific sub and TransactionalEmail.type
• After sending the email create the TransactionalEmail
• Use the job name constant for TransactionalEmail.type

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
1 Code Smell

No Coverage information
0.0% Duplication

[bram-rongen]

I'd suggest to consider using (external) email lifecycle tools. They can also deal with unsubscribing etc..