Integrate similar image previews as in Skype / Slack, rather than just "Download":
- Enable copy pasting of an image from preview
- Enable zoom on image when passing mouse over it
- Open preview in a sub-window for better viewing

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

Currently, using the UX, we cannot determine the last time a user when offline. this feature is useful and could be compared with flowdock.com, as you can see in the image https://user-images.githubusercontent.com/907914/71488129-12347800-2873-11ea-8b03-867c8fc2b357.png

Steps to reproduce:
mattermost Server 5.16+
Open a conversation 1-1 with any user, and if it is offline, we cannot determine since when that user is offline

Expected behaviour:

Open a conversation 1-1 with any user and if is offline. Display as part of user status since when the user is offline.

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).

Users can minimize an image preview of an URL that is directly pasted in the message, with the cross button at the top left corner. However, there is no such button if the same image is inlined with the folowwing syntax .

It'd be useful to have a way of minimizing inline images, like Slack does and like Mattermost does for raw URL previews.

This is a follow-up on multiple requests from the users of moussetc/mattermost-plugin-giphy on GitHub (Issue 12).

By default custom emojis are available to every user in the server in every channel.
I would like to be able to restrain the visibility of a custom emoji I upload.
When uploading a custom emoji, I would like to pick in which channel it can be selected.

I am interested in implementing this feature myself.

When pasted into chat, render percent-encoded URLs into readable characters.

i.e. instead of displaying https://ru.wikipedia.org/wiki/%D0%93%D0%B5%D0%BE%D0%B3%D1%80%D0%B0%D1%84%D0%B8%D1%87%D0%B5%D1%81%D0%BA%D0%B8%D0%B5_%D0%BA%D0%BE%D0%BE%D1%80%D0%B4%D0%B8%D0%BD%D0%B0%D1%82%D1%8B

show https://ru.wikipedia.org/wiki/Географические_координаты

I propose changing text only, not the href of an <a> tag.

Original report: https://github.com/mattermost/mattermost-server/issues/14602.

Currently it is not possible to have notifications triggered based on keywords, for example if there are any emergency keywords, a certain ringtone or vibration (or both) will be triggered.

This would be important in the event of any emergency that requires immediate action.

Support all issue status update event transitions, not just only status changes when the ticket is reopened, or when resolved/closed, and assignee changes.

We use the issue status transition to trigger the QA Team to start work. Would be nice to have these notifications via the Mattermost Integration

Enable the ability for a user org/admin to make 'reply to the last message in a channel' the default option when starting a new message, so threads are the default for a conversation. This could perhaps also be optionally limited to replies that explicitly start with or contain an 'at-mention' of the handle of the creator of the original post.

Currently, the option to restrict who can send team invites are only available for E10 and E20 editions of Mattermost.

Not having this functionality in the Team Editions of Mattemost can cause their instances to be potentially insecure as anyone can send out these invite links.

Add an server wide option to forbid renaming user names. It might be a security problem, if someone claims abandoned user name (/account name).

Have a button in the code block to copy it on clipboard

Allow the wildcard to be used in the email domain whitelist so that not every email your company/org owns needs to be added individually, i.e. *.mycompany.com

When a user is removed from a channel, they aren't notified in any way - the channel just disappears from their window. It would be helpful to indicate that you've been removed.

iOS Timeout/Logout Notification

Based on being automatically logged out every 3 days; it has been a consistent problem having people recognize when they are no longer on and thus not receiving messages (iPhones wise at least). This has already been implemented for Android CAO 2018 according to the search bar.

Currently, when people have "Send messages with CMD+Enter", this shortcut does not work in the message editing window and people have to save their edited messages with a mouse click.
I propose the message editing window to behave the same as the message sending box works.

Originally submitted as a bug: https://github.com/mattermost/mattermost-server/issues/14934

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

While the current Bulk Export Tool - https://docs.mattermost.com/administration/bulk-export.html#running-the-bulk-export-command - allows backend admins to export all the teams based on the following command:

sudo ./mattermost export bulk /home/user/bulk_data.json --all-teams

It will be great to have the ability to export single / selected team to remove any "inactive" teams when moving / migrating systems around.

The current workaround of removing unwanted teams from the export file is not ideal for instances that have a large number of teams.