General
Please search for existing ideas before posting a new idea.
- or
1232 results found
-
Add notification replies for wearables
Currently, whenever a mobile notification is received, it displays the message in the notification, but accessing the notification from a wearable (Android Wear, Tizen, Pebble, etc.) only gives the option to show on phone, with no choice to reply to the message from the notification. It would be nice to have notification replies so that people with wearables can respond to messages quickly without needing to pull out their phone.
31 votes -
Permalink to the part of message
If you want to show something in source code message or big plain text, you can select part of message and send it as permalink instead full message permalink.
7 votes -
Preinstalled "matter-bot"
I´m just stealing the idea from slack ;)
I would like to see a simple bot that I can configure much like the "Slack Bot" (https://get.slack.help/hc/en-us/articles/202026038-Slackbot-your-assistant-notepad-programmable-bot)
This is a great and simple way to get started with bots!
110 votes -
Add a way to spoiler some messages or part of messages
I think it would be a great idea to add spoiler tags like message or message but for spoilers (i.e ^This is a spoil^)
There are several ways to implement this:
-By having an expand/close button for showing/hiding the message
-By having to select the text to see it
-By having to hover on the text with the cursor to see it (might be problematic for touch-based devices)I suggest discussing on what is the best for mattermost.
151 votesFor now, a plugin can be used: https://github.com/moussetc/mattermost-plugin-spoiler.
-
Let admins allow anonymous posts / anonymous channels
A setting that allows users to make anonymous posts. Or that forces all posts in a given channel to be anonymous.
On a trusted server, this gives users a safe place to make anonymous statements.
Similar to the "Anonymous posting" feature of Discourse: https://www.discourse.org/about/
Enable anonymous posting mode and your users can easily switch to anonymous mode to post about controversial, dangerous, or political issues without fear.
47 votes -
Create a "already used tags" drop down menu when typing # , based on the already used hashtags
To preserve or moderate a given thread , theme or channel, tagging them makes the search much easier afterwards. But to make sure, that the given hashtags will be the same (tag cloud?), by typing # a dropdown should show up with already used tags. Behavior could be the same lile with @ or :(for smileys!).
138 votesHey all! Thanks for upvoting the feature, it is now planned: https://mattermost.atlassian.net/browse/MM-10456
Anyone interested helping contribute the feature to the project?
-
Positive sorting of emojis for autocomplete
Switch to the positive attitude of Slack
If you type : thumbs ... : slack suggests :thumbsup: where as mattermost suggests :thumbsdown:15 votes -
Create an ARM build pathway
Right now there's no approved way to do mattermost on ARM. I think ti'd be a great idea to fix that, and I'm working on fixing it myself. If I get a definitive result, I will post it in the regular forums and/or submit a pull request.
256 votes -
Easily change default channel town-square
Across Go and React code, town-square channel is hardcoded. Maybe we can make it configuration-based so teams can easily change it and the platform can redirect correctly to /channel/<new name>.
However doing this, we also have to change the mobile app code e.g. https://github.com/mattermost/android/blob/master/app/src/main/java/com/mattermost/mattermost/MainActivity.java#L137 code.
122 votes -
EE: Single-Channel Guests for non-team members
For IT policy compliance, offer the ability to invite non-team members users to Mattermost as "single-channel guests" to have access to read and write to one channel and direct message any other users in that channel.
Potential scenarios include opening discussions with non-team members, including customers, vendors, partners and interview candidates.
685 votesThis is now available in Beta in E10 and E20: https://docs.mattermost.com/deployment/guest-accounts.html.
-
Support different sets of Emoji / allow users to switch Emoji styles
Slack (sorry --) supports different styles of Emoji, which would be awesome because I'm not a big fan of the current emojoy style ^^
15 votes -
Order DM and Members list by online indicator
- Member list (popup box) in the header
- Direct Messages list
- If you can change order by in this lists to order first by online status, then second by name, then it could be more useful.
5 votesThe member list in the channel header now orders members by their online status and then by their name.
-
Better /me command style
/me command has very poor style distinction. It only uses italics but it is enclosed in a dialog balloon as any other message.
It is more distinguishable, for example, when the system balloon tells join/leave actions in 3rd person. I think something like that would be more accurate for the /me command.
18 votes -
Open channels and direct messages in different windows (Desktop apps)
Right now we use Mattemost for communication about projects and Spark/Jabber/XMPP for direct messages. The reason we prefer Spark over Mattermost is that we can have each communication in a different app window and that makes it easier if you communicate with more people at once. Typical use case is that you send a question to your colleague and keep the window open until you get the answer.
9 votes -
FreeBSD support
It would be great it mattermost is supported in FreeBSD.
I think in order to support more OS, specially BSD unixes, mattermost should not depend from Docker.
For instance Docker doesn't well supported on FreeBSD.178 votes -
should implement an admin interface to the System Console to make the server auto update to the latest MM release
It would be great to make admins life easier to develop an auto admin function to Mattermost that on click downloads, installs and updates the given installation, so the admin doesn't need terminal or root access anymore. Especially renewing the config (put the existing entries in the new/extended config) would be helpful.
148 votes -
Support for multilines in cell in markdown tables
Add support for multiple lines in tables.
From: https://github.com/mattermost/platform/issues/1557183 votes -
way to turn off emoticons?
from https://github.com/mattermost/platform/issues/1982, Skype etc. allow you to turn off emoticons, so that you get the raw text input instead of the converted smiley face. Not everyone appreciates chat filled with emoji, so it'd be a nice feature to have emoticon rendering a setting people can turn on or off (note that this is about MM-conversion of one an ASCII sequence into an emoticon. If someone types an actual unicode emoji, then that's what they intended to type. But if someone types a colon, a dash, and a closing parenthesis, they did not type a smiley icon, and not everyone appreciates a platform autoconverting another user's input)
from https://github.com/mattermost/platform/issues/1982, Skype etc. allow you to turn off emoticons, so that you get the raw text input instead of the converted smiley face. Not everyone appreciates chat filled with emoji, so it'd be a nice feature to have emoticon rendering a setting people can turn on or off (note that this is about MM-conversion of one an ASCII sequence into an emoticon. If someone types an actual unicode emoji, then that's what they intended to type. But if someone types a colon, a dash, and a closing parenthesis, they did not type a smiley icon, and not everyone…
156 votes -
Provide an option to only show channels with unread messages
We have a Mattermost installation where I'm subscribed to 24 channels, most of which are fairly quiet. Except for the channels that are at the top and bottom of the list (of course). I'm continually scrolling up and down.
I'd like to have an option that hides channels that have no unread messages. Hiding all-read private groups and DMs would be a bonus.
96 votesThanks Brian and others for suggesting this feature!
We are considering to add a setting to hide all read channels in the sidebar: https://mattermost.atlassian.net/browse/MM-7502
In the meantime, there are two features that can help your teams:
1) Mattermost v4.7+ supports a setting to group all unread channels at the top. This makes it easier to find all your unreads. It must first be enabled by your System Admin: https://docs.mattermost.com/administration/config-settings.html#group-unread-channels-experimental
2) Mattermost v4.9+ shows unread channels when using the channel switcher (CMD/CTRL+K) -
Access Control List for Web Interface & Mobile App
We are a .org wishing to implement Mattermost.
We would like only a specific group of "internal" users to be allowed to access the server from outside the firewall. In addition, we would also like a specific group of external clients to be able to access the server through the mobile app.
I understand one method is to use a VPN. However, an additional app to put on someone's device may be a burden.
The Novell/Micro Focus Product Webaccess has a feature that allows the admin to specify users via an .xml file.
A snippet:
"Controlling WebAccess Usage:
You can control which users can use WebAccess to access their GroupWise mailboxes. By default, all GroupWise users can use WebAccess.
You can control access based on the domain or post office where the user’s mailbox is located. You can control access for related users based on groups, and you can control access for individual users.
Access control is established through the gwac.xml file, located in the same folder with the webacc.cfg file.
The default gwac.xml file illustrates the following options:
<!-- To allow access to all EXCEPT a few, use this technique. -->
<!--
<gwac access="prevent">
<domain name="domain1" />
<postOffice name="po2.domain2" />
<user name="jdoe.po3.domain3" />
<distributionList name="helpdesk.po4.domain4" />
<resource name="confroom.po4.domain4" />
</gwac>
--><!-- To prevent access to all EXCEPT a few, use this technique -->
<!--
<gwac access="allow">
<domain name="domain1" />
<postOffice name="po2.domain2" />
<user name="jdoe.po3.domain3" />
<distributionList name="helpdesk.po4.domain4" />
<resource name="confroom.po4.domain4" />
</gwac>
-->
You can use any ASCII text editor that you prefer to edit the gwac.xml file.Open the gwac.xml file in a text editor.
Typically, you use the gwac.xml file to override the default of allowing all users to use WebAccess.
Remove the comment marker lines (<!-- and -->) around the section that you want to use.
(Optional) Under the <gwac access="prevent"> line, create one or more lines to prevent users in one or more domains from using WebAccess, for example:
<domain name="provo5"/>
<domain name="provo6"/>
(Optional) Create one or more lines to prevent users in one or more post offices from using WebAccess, for example:<postOffice name="interns.provo1"/>
<postOffice name="temps.provo1"/>
Specify the post office in post_office.domain format.(Optional) Create one or more lines to prevent users in one or more groups from using WebAccess, for example:
<distributionList name="webaccessdenied.admin.provo1"/>
Specify the group in group.post_office.domain format.Using one or more groups is the most flexible approach to access control for WebAccess. The group belongs to a specific post office (for example, the one you belong to), but it can include GroupWise users located anywhere in your GroupWise system. By using a group, you can easily modify access control for specific users by modifying the group in the GroupWise Admin console, rather than needed to modify the gwac.xml file whenever access control changes are needed. For more information about groups, see Section 56.0, Creating and Managing Groups.
(Optional) Create one or more lines to prevent specific users from using WebAccess, for example:
<user name="sjones.interns.provo1"/>
<user name="gbock.interns.provo1"/>
(Conditional) If you want to prevent most users and allow only specified users, use a <gwac access="allow"> line instead of a <gwac access="prevent"> line.Save the gwac.xml file."
Please consider.
Original Request:
http://forum.mattermost.org/t/restricting-users-from-accessing-mattermost-outside-firewall/2617We are a .org wishing to implement Mattermost.
We would like only a specific group of "internal" users to be allowed to access the server from outside the firewall. In addition, we would also like a specific group of external clients to be able to access the server through the mobile app.
I understand one method is to use a VPN. However, an additional app to put on someone's device may be a burden.
The Novell/Micro Focus Product Webaccess has a feature that allows the admin to specify users via an .xml file.
A snippet:
"Controlling WebAccess Usage:
You can…
9 votes
- Don't see your idea?