nextcloud / nextcloud/spreed

Search should not show archived rooms by default or at least seperate them clearly

Open
#18,031 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement Needs triage
Dominant language
JavaScript
Stars
2.2k
Forks
586
Avg merge
18h 27m
Merged PRs (30d)
333

Description

When I search in the room list on the left side bar all results shows up, archived rooms and active rooms. Completely mixed up, there is no way to distinguish them by just looking at the results. Which is especially tricks if you have multiple rooms with similar name but only one is the active one and the other ones are old archived conversations.

Most of the time I want to search my active rooms, showing the archived rooms as well adds a lot of noise if you have many archived rooms and make it harder to spot and select the right room in the search result.

Ideas to solve it:

  1. Only search active chat rooms by default. If you want to search archived chat rooms you first have to go to "Archived conversations" and search than only the archived rooms.
  2. Clear separation of search results: show at the top only search results for active conversation than a separator/headline "Archived conversation" and than the result from the archived conversations.
  3. Like the first one but with a button/filter "include archived message" to easily add them to the search result.

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

Start with the room-list search UI and inspect how active and archived rooms are currently included in results. Compare the proposed filtering and separation options, then verify that the chosen behavior makes active rooms easy to find while still allowing archived rooms to be searched when needed.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.