New user onboarding emails: password-changed email sent first; neither email greets user by name or includes username / first-time login instructions
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 42/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- typescript
- Área
- authentication, backend
Línea de trabajo
Start by tracing the admin user creation flow and the code that sends the password changed and welcome emails; the issue does not name files or tests. Check how user name, username, workspace URL, and first login credentials are passed into each email, then review the relevant email tests. Done means new users receive clear, friendly login instructions with their name and username, without misleading password change wording.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Description
When an admin creates a new user (with name, email, and a default password), the email onboarding experience is confusing for a brand-new user. Two emails arrive, and between them the user is never told who they are, what their username is, or how to log in for the first time.
Email 1 — "Your password was changed by an admin" (arrives first)
Problems:
- Wrong framing for a brand-new account. The very first thing a new user learns about the product is that "your password was changed by an admin" — an alarming message about an account they've never used. This is really an "account created" email and should be worded like one.
- No greeting by name. It opens with a bare "Hi," even though the admin set the user's full name when creating the account.
- No username. The email gives a temporary password but never says what username (or that the email address) should be used to log in. The user has half the credentials.
Email 2 — welcome email
Problems:
- Generic marketing copy ("...try the best open source chat solution available today!") with no username, no temporary password, and no first-time login instructions.
- Also no name in the greeting.
Net result
A new user receives a scary-sounding password-change notice and a marketing email, and still has to ask the admin what their username is and where to log in. First-run onboarding via email effectively doesn't work.
Steps to reproduce
- As an admin, go to Administration → Users → New user.
- Fill in Name, Email, and a Password, and enable Send welcome email.
- Save the user.
- Check the new user's inbox: a "Your password was changed by an admin" email with a bare temporary password arrives first, followed by the generic welcome email.
Expected behavior
The email(s) sent when an admin creates a user should:
- Greet the user by their name (it's already on the user record).
- Tell the user their username (and/or that they can log in with their email address).
- Make clear where to log in (the workspace URL), not just a Login button.
- Be worded as an account created / welcome message rather than "your password was changed by an admin" — or at least use distinct, friendlier wording for newly created users versus actual password changes.
- Ideally be a single coherent email containing name, username, workspace login URL, and either the temporary password or a set-your-own-password link, so the user can log in on the first try without asking the admin anything.
Actual behavior
- The first email is a password-changed notice; the second is a generic marketing welcome.
- Neither email uses the user's name ("Hi,").
- Neither email states the username or how to log in for the first time.
Server Setup Information
- Rocket.Chat Version: 8.9
- Lenguaje dominante
- TypeScript
- Estrellas
- 46.5k
- Forks
- 14.1k
- Merge medio
- 1 d 21 h
- PR fusionados (30 d)
- 381
Preparar el entorno
Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de RocketChat/Rocket.Chat
-
Mark the empty state busy while a new search loads, like the table */}Posiblemente ocupada @aditya25bcy10173-a11y la tomó hace 2 días. Abiertotodo type: feature
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
RocketChat/Rocket.Chat#43699 · 1 comentario · 1 reacción ·
Los mantenedores suelen responder en 1 día
-
Timestamp with a time but no timezone shows as 1 January 1970Posiblemente ocupada @Sarthak-agrawal-tech la tomó hace 4 días. Abiertotype: bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
RocketChat/Rocket.Chat#43637 · 6 comentarios ·
Los mantenedores suelen responder en 1 día
-
Move this mapping from useQuery's old `select` into a usePaginatedQuery `combine`Posiblemente ocupada @aditya25bcy10173-a11y la tomó hace 3 días. Abiertotodo type: feature
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
RocketChat/Rocket.Chat#43609 · 4 comentarios · 1 reacción ·
Los mantenedores suelen responder en 1 día
-
evaluate switching to the other tab when the selected tab's permission is revoked mid-sessionPosiblemente ocupada @schizophrenicmaniac la tomó hace 4 días. Abiertotodo type: feature
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
RocketChat/Rocket.Chat#43579 · 3 comentarios · 1 reacción ·
Los mantenedores suelen responder en 1 día
-
Docs say packages can be installed with `npm` but use unsupported `patch:` URLPosiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abiertotype: bug
Dificultad 1/5 1-3 horas Aptitud para principiantes 72/100
RocketChat/Rocket.Chat#43554 · 4 comentarios ·
Los mantenedores suelen responder en 1 día
Todos los issues de RocketChat/Rocket.Chat
Issues similares
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
langchain-ai/langchainjs#12239 ·
Los mantenedores suelen responder en 1 día
-
Board view: the Monitoring column is always empty because compact issue rows drop displayStatusAbierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
paperclipai/paperclip#21837 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 73/100
code-yeongyu/senpi#6813 ·
Los mantenedores suelen responder en 1 día
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Dificultad 1/5 Menos de una hora Aptitud para principiantes 93/100
lingdojo/kana-dojo#34169 · 1 comentario · 5 reacciones ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100