The use case is to provide information to users, for example, release notes, status updates, etc. In order to keep the channel relevant and to avoid clutter, non-admin users have read-only access.

This feature allows a team to create "reference" channels.

1. team admins: create, read, update, delete


2. non-admin users: read-only

This idea is similar to, and currently under review for Enterprise Edition:

https://mattermost.uservoice.com/forums/306457-general/suggestions/12874797-add-write-policy-for-channels-and-private-groups#comments

This idea is related to:

https://mattermost.uservoice.com/forums/306457-general/suggestions/11205615-different-user-roles-to-configure

Hello,
cli tool is not user's compliant :)
Users should be able to delete (not just deactivate) their datas without any admin intervention.

Support Gitea's OAuth2 provider as an authentication source.

Currently, the team edition only supports GitLab as an OAuth2 source. GitLab is pretty heavyweight and many people prefer other software for a variety of reasons.

Gitea (https://gitea.io/en-us/) is a really nice open source, community supported Git server. They recently added support for acting as an OAuth2 provider (see https://docs.gitea.io/en-us/oauth2-provider/ for documentation). It would be great if Mattermost would support Gitea as an OAuth2 provider.

When a user want to delete his account, he can think "deactivation" is enough but doesn't necessarily know that it just means that he cannot log anymore…

Maybe (in advanced settings):

"By deactivating your account you will no longer be able to log in but the messages will be kept. To permanently delete your account and your messages, please contact your administrator."

And a similar (or the same) message in email notification.

Slack recently increased their character limitation on channel names. We would like Mattermost to increase the limit as well, as this has been a helpful feature since it was rolled out.

for the default search backend (sql), search results are capped at 100!

you can verify this by loading jquery and doing:

$('.search-item__container').length;

you can see that paging isn't supported:

https://github.com/mattermost/mattermost-server/blob/master/app/post.go#L821

and the sql uses LIMIT 100:

https://github.com/mattermost/mattermost-server/blob/master/store/sqlstore/post_store.go#L834

i know this isn't an issue in enterprise because you're using elasticsearch, but please either bring elasticsearch to team edition or fix the default search backend. 100 results is sad :(

The same way we can send messages, we should be able to send voice messages.

It should be as simple as click "add voice", record what you want, press send and it's made available on the server for others to listen.

It should be supported by browser and mobile client apps.

While system administrator are limited to only have the following methods to create / import users:
* Local users: mattermost user create CLI, direct invite, team invite link
* External users: LDAP / AD / SAML

It will be good to have the ability to use CSV or Excel file to bulk import the users with specific formatting especially if the organization has a lot of customers and is not utilizing AD / LDAP / SSO.

In a thread, because we cant create subthreads, the comment menu should have a new item called "quote reply".

"Quote Reply" should allow the user to add a new comment with reference from the comment he is replying.

A : I like cars.
A : Wanna go for pizza? <-- "Quote Reply"
B : I like Ferrari.
B : "Wanna go for pizza?"

 Yes. Pizza is a great idea.

For example, it will be great to see such information in private messages to the user.

A user should be able to easily see & search the list of all channels they have joined and can join. I'm seeing a number of duplicate channels created across teams because the user did not know it existed in another location.

Currently you need to make two calls to get the total count of unread messages or to get the count of unread messages from a single channel (/users/me/teams/{{team_id}}/channels and /users/me/teams/{{team_id}}/channels/members).

To avoid the first request, it would be nice to have a new property e.g. new_msg_count that returns the current new message count for a channel. This is currently only possible by substracting the msg_count (second request) from the total_msg_count (first request).

This topic has already been discussed on github: https://github.com/mattermost/mattermost-server/issues/8591#issuecomment-383909505

this is the opposite of the current setting:
ENTER inserts a new line and CTRL+ENTER submits the message.

On the [...] button on the right side of a message, there's a tooltip displaying the text "More Actions". When I click on this button, the menu pops up and then the tooltip appears, blocking the "Edit" menu item. The tooltip should never be allowed to pop up if the menu is already open.

Firefox, Mattermost Version: 5.6.2

people are often sloppy in using answers to messages and just type it to the channel when it should be an answer to the message above.
I propose a button visible to the author and admins that allows to transform a message into an answer to the message above.
I hope it'll help to create more consistency in the usage of the answer/thread feature.

Change attachments for adaptive cards, is more flexible.

https://adaptivecards.io/samples/InputForm.html

Currently, search is horribly broken for technical conversations. For example, given a post which contains a log message, such as:


PROBLEM srvnagios at 10.4.1.74/MYSQL_threads-connected is WARNING


A search for MYSQL will not show this as a result. This is, certainly, just an example and it's been relayed that this is by design due to a lack of support for preceding wildcards (which shouldn't be needed anyway). Simply typing MYSQL in the text box should return any string that contains MYSQL or mysql.

As of now, a change of theme on one device is automatically synched to all other devices.

I'm hosting a single team installation for 2 local charities (each has their own team). It would be great to be able to set a separate storage limit per team. In small situations like this it's not necessary to run 2 instances of mattermost. but this setup is only manageable if we can specify a limit per team.