[BUG]: when multiple password reset attempts follow-on email text below the line in user email view #5678

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

Password reset email differentiation

Summary

When users request to reset email the text is the same each time, so if the user requests to reset email multiple times, gmail consolidates the reset guidance text below the ... line and users don't see that there's a second link to lick to reset password

Expected Behavior

Users are able to clearly see and differentiate each password reset email so that they know which link is the most recent and are able to reset their password successfully

As a Human Essentials user, I want to be able to tell which reset password link to use, so that I am able to reset my password without admin help

Steps To Reproduce

• the dev way is to access the email via your local machine

User flow

• log into Human Essentials
• if logged in, log out
• click the forgot password link
• enter email address
• receive pw reset email
• update pw using reset link, continue to login
• log out and click forgot password link again
• observe follow on email in gmail shows as blank, unless you click the ... menu to display full content of the second email (see screenshot)

Environment

- OS:
- Node:
- npm:

Criteria for Completion

• when a user clicks the link to reset their password more than once in a day and multiple reset pw emails are received by the user
• then each pw reset email must include a timestamp or datetime stamp in email subject to differentiate them in gmail, so that users are able to distinguish each message without expanding the "more" ... menu
• the email sent to the user addresses them by their name in salutation
• include the datetime stamp in the body of the email
• add a signature at the bottom of the email with datetime saying something like "From your Human Essentials Team "
• this change applies to any role password reset flow
• test that the update applied to email subject
• test that the update applied to email body signature

Anything else?

Use this placeholder logo with signature in the email body

Code of Conduct

• I've read the Code of Conduct and understand my responsibilities as a member of the Ruby for Good community