Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to message button gives 'Room not found' for starred thread messages in Global search results #25032

Open
Kyogre opened this issue Apr 2, 2022 · 0 comments

Comments

@Kyogre
Copy link

Kyogre commented Apr 2, 2022

Description:

User got error "Room not found" when press "Jump to message" button on the starred message in thread, found by global search.

Steps to reproduce:

  1. go to channel 1
  2. star message in thread (exactly in thread! Not in the root of the channel)
  3. go to channel 2
  4. open global search -> search "has:star"
  5. press "Jump to message" button on the message from step 2

Expected behavior:

The same as for starred channel message. User teleported to the message in thread.

Actual behavior:

User gets "Room not found" error.

Server Setup Information:

Version of Rocket.Chat Server: 4.5.4
Operating System: CentOS Linux release 7.9.2009 (Core)
Deployment Method: yum + src
Number of Running Instances: 1
DB Replicaset Oplog:
NodeJS Version: v14.0.0
MongoDB Version: 4.4.13 / wiredTiger (oplog Enabled)
Proxy: nginx/1.20.1
Firewalls involved: iptables, ACCEPT ALL

Client Setup Information

  • Desktop App or Browser Version: both
  • Operating System: -

Additional context

Video demo: https://user-images.githubusercontent.com/2260980/162570025-6d8d94db-00f0-46a9-bf7d-f2ad91650028.mp4

Relevant logs:

-

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant