search

element-hq / element-meta

Shared/meta documentation and project artefacts for Element clients
65 stars 11 forks source link

Improve Visibility of Active Threads #2417

Open hitchhooker opened 1 month ago

hitchhooker commented 1 month ago

Your use case

Problem: In the current implementation of the desktop and web versions of Element, messages within threads do not appear in the main chat in chronological order. This makes it difficult to follow conversations that are part of threads as they are not integrated with the timeline of standalone messages.

Suggested Enhancement: I propose an option to sort all messages, including those within threads, chronologically in the main chat view(option to bounce whole thread as latest). This would allow users to see messages from both threads and direct replies in the order they were posted, ensuring a seamless flow of conversation.

Expected Benefit: Implementing this feature would enhance the user experience by providing a continuous and coherent view of all conversations. It would help users keep track of discussions more effectively, fostering better engagement and communication across the platform.

Have you considered any alternatives?

i tried to search such option in the logs or prefer checking mobile app element x where this is non issue.

Additional context

No response

dbkr commented 1 month ago

I'm attempting to triage this but I'm afraid I don't understand what's being proposed. Why would a message in a thread appear in the main chat at all? If they're out of order, wouldn't this be a bug? What does the title mean - is the 'feat' suggestion it's a feature? We don't use this naming convention, we use the labels.

hitchhooker commented 1 month ago

hey @dbkr,

so issue that we are facing using element for collaboration that when someone replies to lets say active thread from a week ago there is barely no way from UI to notice that someone has responded to the thread. I am asking for a flag/feature to be able to have threads bounce latest in message list when they get responses instead of staying in the location based on first message of the thread.