RocketChat / RocketChat/Rocket.Chat

5.0.1 - Issue Tracker links no longer work in messages

Open
#26,538 13 comments 10 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

message rendering type: bug
Dominant language
TypeScript
Stars
46.1k
Forks
13.9k
Avg merge
3d 3h
Merged PRs (30d)
130

Description

Description:

After upgrading to 5.0.1, the issue tracker links no longer work.

Steps to reproduce:
  1. Enable Issue Tracker Links in the Message Settings inside the administration panel
  2. Send a message to any room or DM with a hashtag (#) and a number. Like #12345

image

Expected behavior:

The number should become a clickable hyperlink.

Actual behavior:

image

Server Setup Information:
  • Version of Rocket.Chat Server: 5.0.1
  • Operating System: Debian 10
  • Deployment Method: tar
  • Number of Running Instances: 5
  • DB Replicaset Oplog: yes
  • NodeJS Version: v14.19.3
  • MongoDB Version: 5.0.9 / wiredTiger (oplog Enabled)
Client Setup Information
  • Desktop App or Browser Version
    image

  • Operating System: Windows 10

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

Reproduce the issue by enabling Issue Tracker Links in Message Settings and sending a message containing a hashtag and number such as #12345. Trace the message rendering and linkification path to find why the number is not converted, then verify that it becomes a clickable issue-tracker hyperlink in rooms and direct messages.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.