search

RocketChat / Rocket.Chat

The communications platform that puts data protection first.
https://rocket.chat/
Other
39.98k stars 10.31k forks source link

Global Search Error: 'Room not Found' When Jumping to Thread Messages from Direct Messages #32956

Closed CyberStranger closed 1 week ago

CyberStranger commented 1 month ago

Description:

When using the Search Messages feature with the Global search option enabled, the search results will correctly include messages located within a thread. However, if you attempt to jump to one of these thread messages by clicking the "Jump to Message" button, an error message "Room not Found" appears, even though you are a member of the room where the thread is located.

Steps to reproduce:

  1. Enter any room and create a thread.
  2. Write any phrase within the thread.
  3. Open any direct message conversation.
  4. Click on the "Search Messages" button.
  5. Enable the Global Search toggle.
  6. In the search bar, enter the phrase you wrote in the thread.
  7. When the search results appear, click on the "Jump to message" button.

    Expected behavior:

The system should jump to the specific message in the thread within the correct room without any errors.

Actual behavior:

An error message "Room not Found" is displayed. This issue is specifically observed when the global search is initiated from a direct message window with another user. The error does not occur when the global search is activated from an open group window, and the message jump works successfully.

Server Setup Information:

Client Setup Information

Additional context

animation1

Relevant logs:

reetp commented 1 month ago

Please always test on latest (currently 6.10.2 or 6.11.x). A lot happens in a few months.

Also upgrade to latest 6.8.x to fix outstanding bugs.

I think similar has been reported before. Have a search here as well.

CyberStranger commented 1 month ago

I was able to reproduce this issue on 6.10.2

github-actions[bot] commented 3 weeks ago

This issue has been marked as stale because there has been no further activity in the last 10 days. If the issue remains stale for the next 4 days (a total of 14 days with no activity), then it will be assumed that the question has been resolved and the issue will be automatically closed.

github-actions[bot] commented 1 week ago

This issue was closed because it has been inactive for 14 days since being marked as stale.