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.

I would like to have my channel sorted, and having these with unread messages on top.

When it comes to sprucing up your house and health, spending a little green on greens can go a long way. Decorate your house with the Greene of aloe Vera. Get the best pots for aloe plants <a href="https://expertplantman.com/best-pots-for-aloe-vera-plants/">here</a>

we have to click on each attachment to download it. make Save all attachments available please. Drag and drop would be nice too.

Thank you

Hello All,

Would be great to have any option to configure on MM to auto-archive channels (private or public) if no activity for a time period.
This will be really useful, due, we create channels everyday for temporal purposes (incidents, discussions, etc) and no always the participants archive the channels when are not needed.
So, an automatic way to do that would be great to perform the archival for the channels which the last activity was older than 30 days for example...

;)

By default, when a user connects to Mattermost, the user gets the "active" status even if the user does not belong to a team.
Is it possible set the status to "inactive" when the user does not yet belong to a team ?

Notifications of new chat messages should not be emailed if the chat message has already been deleted.

See:
https://github.com/mattermost/mattermost-server/issues/13064

When open server is enabled, users can signup without invite. However when they signup they are allowed to create team, so I disabled it. Now when they sign up there is nothing. How about let them send request to join teams, and administrators can confirm.

Add server plugin hooks for access control (permission change) and logout events to enable developers to create custom server plugins to integrate with internal auditing/intrusion detection tools.

https://developers.mattermost.com/extend/plugins/server/reference/#Hooks

Please make the Data retention and prune/reset/clear feature available on at least E10 we don't need any E20 feature only the data retention.

Please give users the ability to flag posts that could be considered abusive, dangerous, or contrary to corporate policies. Once flagged a link to the post would be sent to a specific email address.

it would be really nice for monitoring and auditing purposes, to be able to extract a list of members in teams and channels

Please add Gsuite as an officially supported SAML authentication source.

1. Easy! Use https://tsugi.org/. 2. Stand up your own tsugicloud to host one or many MatterMost integration tools. 3. Certify your app at IMS Global: http://www.imsglobal.org/lti-advantage-overview . 4. Get expert advice from @sakaiproject and @moodle , the open source learning management systems.

It would be incredibly helpful for enterprise license holders to be able to generate a sort of test license, so that they can set up a test instance with all the features of Enterprise instances (such as LDAP, SAML, etc) so they can test out their settings first before implementing them into their production instance.

We would like a feature to allow leveraging slash command integrations so that users could create custom aliases locally. For instance, one of our integration commands is '/zoom' with additional arguments of 'join' and '<meeting ID>'. We would like to be able to create a custom alias so that a user could always include the arguments along with the slash command without entering 'join' and their 'meeting ID' each time they use the integration.

When you have a multi user direct message and you add new members (as a conversation grows to need more people) you end up creating a new DM with no history. Instead mattermost should provide an option to keep the history available.

My organization would like to have the option to not show deactivated users in member lists.

Some improvements could help administration:

• In the Cluster Status table, highly the node that the user is currently connected to so it's obvious


• Provide a way to connect directly to the server on the local port to debug that specific server.

Any other ideas for improvement?