RocketChat / RocketChat/Rocket.Chat

The search message feature doesn't work sometimes maybe for specific words and also doesn't if complete word is not searched for

Open
#21,028 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Description:
Steps to reproduce:

1.Go To search messages option
2. Search for a message
3. Sometimes it works and sometimes not

Expected behavior:

It should work always for all words and even if an entire word is not searched should work for matching letters

Actual behavior:
  1. Doesn't work for the word 'what'
    what

  2. Doesnt work for the word 'other'
    other

  3. Detects only if complete word is written and doesnt if only some letters are written

comp1

Here it doesn't detect for 'hell' or for anything shorter than hello , but will detect for hello (This bug is for all messages most probably )
Whereas some words are not detected for some reason

Server Setup Information:
  • Version of Rocket.Chat Server: 3.12.0
  • Operating System: Windows(WSL)
  • Deployment Method:
  • Number of Running Instances: 1
  • DB Replicaset Oplog:
  • NodeJS Version: 12.x
  • MongoDB Version:4.x
Client Setup Information
  • Desktop App or Browser Version:Browser
  • Operating System: Windows
Additional context

I dont exactly know for which all words it doesnt work , the above were some examples which I tested

Relevant logs:

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 message search in Rocket.Chat using the reported words “what,” “other,” “hello,” and partial terms such as “hell.” Compare the observed results with the expected matching behavior, then trace the message-search entry point to identify the responsible search path; done means searches consistently handle these cases as specified.

Written by the indexing model from the issue text.

Assessment

Domain
search
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.