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

Right now, only mattermost instance admin can export teams but only all teams.
There is two issues:

• first: we can't export one team (see this request: https://mattermost.uservoice.com/forums/306457-general/suggestions/39225376-mattermost-bulk-export-single-selected-team)


• second: it's the instance admin job to export

It would be a great improvement if team admin could use the user interface (and not has to ask to his instance admin).

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

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.

Ability to use a generic 3rd party OAuth server for programmatic logins to mattermost server (team edition)

Please see for detailed description:
https://github.com/mattermost/mattermost-server/issues/14293

Please add the team name to any notification emails sent by MM. While we have few teams with common channel names, it is really confusing from email body which team it is.

I was receiving a generic "Received invalid response from the server" messages when trying to upload the BigBlueButton plugin. I eventually discovered that it was because the Maximum File Size was configured to 5MB.

A clear message stating either what the "invalid response" was or flagging the issue as "too large of a file" size would be less generic and easier to troubleshoot.

Summary
At the moment, it is only possible to use root of the bucket. It will be nice to be able to use subfolder of the bucket. Some of us have more than 50 buckets...adding even single one more is chaos.

Expected behavior
Be able to set S3Prefix in order to use s3://bucketname/s3prefix/s3_object

Github: https://github.com/mattermost/mattermost-server/issues/14498

A simple image editor for uploaded images. This to draw lines, write text and add arrows. Would be great when explaining things. As in a quick bug report.

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.

The "purpose" element of each channel is very difficult to see. Information such as who created this channel doesn't need to be noticeable. The necessary "purpose" statement is buried in the information. I want at least the "purpose" statement to bold the font.
I want to hide or move information other than the purpose.

When there are multiple teams, when a new post is made to another team, it is difficult for users to notice it. I want you to show it with an impact that would reverse the color information of the icon.
The same can be said for the channel name display within each team. It is difficult to understand with the current bold display.

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.

It's kind of annoying that the syntax for code blocks is so strict.

Mattermost image proxy supports atmos/camo Image Proxy and local image proxy. Support should be added for normal proxies that one would set via HTTPSPROXY environment variable. I need images to go through a proxy but I don't want to see HTTPSPROXY for entire application.

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