RocketChat / RocketChat/Rocket.Chat

Missing link in text/plain sections of offline message alert email

Open
#34,216 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

planned
Dominant language
TypeScript
Stars
46.1k
Forks
13.9k
Avg merge
3d 3h
Merged PRs (30d)
130

Description

Description:

Offline message email alerts sent with either "Send only plain text emails" enabled or when rendered in a plain/text email client are missing a link to for the "GO TO MESSAGE" button.

Steps to reproduce:
  1. Receive an offline message alert
  2. View email as plain text
Expected behavior:

A link to the missed message is included in the email text body

Actual behavior:
----_NmP-bfb1301f864d2641-Part_1
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

admin sent you a message GO TO MESSAGE
----_NmP-bfb1301f864d2641-Part_1
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Server Setup Information:
  • Version of Rocket.Chat Server: 7.1.0
  • License Type: Enterprise
  • Number of Users: 3k
  • Operating System: Debian
  • Deployment Method: Binary
  • Number of Running Instances: 1
  • DB Replicaset Oplog: x
  • NodeJS Version: v20.5.1
  • MongoDB Version: 6.0.19
Client Setup Information
  • Desktop App or Browser Version: n/a
  • Operating System: n/a

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The report names no source file, test, or entry point. Start by reproducing an offline message alert with plain-text email output, then locate the code that assembles that alert. Done means the plain-text body includes a usable link to the missed message while the existing HTML behavior remains intact.

Written by the indexing model from the issue text.

Assessment

Domain
backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.