You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we use searching functionality on the conversation page, it is not displaying more than 10 results, when there are more of it
To Reproduce
Open your Admin account
Navigate to Conversation page
Make sure you have many conversations
Search one of the user conversation which has more than 10 messages
Expected behavior
On the Search page, there should be displayed all results
Environment
app.chatwoot.com
Cloud Provider
None
Platform
None
Operating system
No response
Browser and version
No response
Docker (if applicable)
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Edik-Apoyan
changed the title
Search field on the conversation is displayed max last 10 results
"Search field" on the conversation is displayed max last 10 results
Jun 16, 2023
This is still the case, and would be so helpful to view many results!
For example, if I remember sending a canned response to inbound queries of a certain type, it makes sense to me to search for past messages/convos using the text from the canned response. But there could easily be more than 10 of these, and then many will just not show up
In general, adding more characters feels a bit counter-productive for a typical search scenario; if I already knew all the content/characters of a result, there wouldn't be much reason to search for it
Thanks for Chatwoot - such an awesome piece of software!
Describe the bug
When we use searching functionality on the conversation page, it is not displaying more than 10 results, when there are more of it
To Reproduce
Expected behavior
On the Search page, there should be displayed all results
Environment
app.chatwoot.com
Cloud Provider
None
Platform
None
Operating system
No response
Browser and version
No response
Docker (if applicable)
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: