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
As alliance with many members form it is hard to distinguish the important information from the general discussion.
I would love to be able to have two conversations called "Alliance" and "[IMPORTANT] Alliance" for people to be able to not have to filter through the messages to find important information.
Current behaviour:
When we attempt to create a conversation with the same participants, we get the error "A conversation already exists with the selected participants named CONVERSATION NAME."
Proposed behaviour:
We check if a conversations with the same name. If the name is unique then create the conversation.
Alternate prosposed behaviour:
Be able to pin messages that are important and being able to show only pinned message. All participant in the conversation can pin and unpin message.
The text was updated successfully, but these errors were encountered:
Ownezx
changed the title
Multiple conversation with the same recipient
Multiple conversation with the same recipients
Sep 1, 2021
As alliance with many members form it is hard to distinguish the important information from the general discussion.
I would love to be able to have two conversations called "Alliance" and "[IMPORTANT] Alliance" for people to be able to not have to filter through the messages to find important information.
Current behaviour:
When we attempt to create a conversation with the same participants, we get the error "A conversation already exists with the selected participants named CONVERSATION NAME."
Proposed behaviour:
We check if a conversations with the same name. If the name is unique then create the conversation.
Alternate prosposed behaviour:
Be able to pin messages that are important and being able to show only pinned message. All participant in the conversation can pin and unpin message.
The text was updated successfully, but these errors were encountered: