General
Please search for existing ideas before posting a new idea.
- or
No existing idea results
- ~ No ideas found ~
1232 results found
-
make private chats able to authorize users based on ldap groups
In corporate Environments often closed discussions take place between persons whose users already exist within predefined ldap groups. For Mattermost it would make sense to authorize users for private channels using such existing ldap groups.
2 votes -
Ability to export all of a specific user's content when required for compliance
From: https://github.com/mattermost/platform/issues/2291
In corporate environments it is sometimes necessary on legal grounds to check an employees communication. Usually the management asks the IT therefor to deliver ones communication. Currently an administrator is neither able to view the existing private chats from any user nor is there an export function to extract all users content from the database
5 votes -
email notifications for new messages and for channel joins look alike and have a similar email notification subject
This behaviour leads to that one could not see at first sight which type of message the notification was for, because the email subject is always "New Mention on...".
It would be more informating and appropriate to choose a email subject that makes clear at first sight which kind of mention the notification is about. (channel join, user disabling, mention, etc)
In my opinion a channel join is no mention in sense of a new message. There is a difference between a new message and other System activities and this should be clear withing the notification email.
Maybe ist reasonable to differ the email design a bit by choosing different colours for different notification types, so a user can see what the notification is about just based on the colours in the notification email.
see: https://github.com/mattermost/platform/issues/2312#issuecomment-196896155This behaviour leads to that one could not see at first sight which type of message the notification was for, because the email subject is always "New Mention on...".
It would be more informating and appropriate to choose a email subject that makes clear at first sight which kind of mention the notification is about. (channel join, user disabling, mention, etc)
In my opinion a channel join is no mention in sense of a new message. There is a difference between a new message and other System activities and this should be clear withing the notification email.
Maybe ist reasonable…1 vote -
add support for syslog output
It's a pain to deal with many scattered logfiles, so syslog support would be a welcome alternative.
The only extra configuration despite enabling, and the loglevel should be the syslog facility.
https://github.com/mattermost/platform/issues/18204 votes -
make an admin be able to differ between inactive and disabled users
The problem of the current situation is, that an administrator yet is only able to set an user account status to "inactive". This means more a disabling of the user, because the user is in no longer able to log in. In fact, he is locked out.
It would be more appropriate to rename the status "inactive" to "disabled".A new status "inactive" should be introduced where a user is in fact using the featureset of a "team edition". No license is acuired for this user and he doesn't get any push notifications anymore until he logs in again. By loggin in he could reactivate his Enterprise license and get back again all Enterprise features. This would extremly help saving licenses for Enterprise Customers if companies got a lot of users that do either not often use Mattermost or particular users of a Enterprise licensed server do not need the Enterprise features.
This feature would be rounded down by adding a batch job to the console that sets users to inactive automatically when they do not re-login to Mattermost within a to be specified time period.
The problem of the current situation is, that an administrator yet is only able to set an user account status to "inactive". This means more a disabling of the user, because the user is in no longer able to log in. In fact, he is locked out.
It would be more appropriate to rename the status "inactive" to "disabled".A new status "inactive" should be introduced where a user is in fact using the featureset of a "team edition". No license is acuired for this user and he doesn't get any push notifications anymore until he logs in again. By…
2 votes -
Sync between redundant servers
In 2015, GitHub user titanous proposed adding support for more than one instance of the API server. (https://github.com/mattermost/platform/issues/402) It was suggested that it would be added before the 1.0 release, but the issue has since been closed without any changes. Since I didn't see this feature requested in this forum, I thought I would post it so that the community can vote on it.
I work with a team of five, all of whom have personal servers, one of which hosts our Mattermost instance. It would be useful for us if we could host as many as five redundant instances of Mattermost, so that if one of our servers were to go down, we could seamlessly switch to another one without losing messages.In 2015, GitHub user titanous proposed adding support for more than one instance of the API server. (https://github.com/mattermost/platform/issues/402) It was suggested that it would be added before the 1.0 release, but the issue has since been closed without any changes. Since I didn't see this feature requested in this forum, I thought I would post it so that the community can vote on it.
I work with a team of five, all of whom have personal servers, one of which hosts our Mattermost instance. It would be useful for us if we could host as many as five…7 votes -
Don't show 'More' channels if none are available
Currently, the channel list will show 'More...' as the last item in the list.
If there are no further channels created in the team, then this item performs no function other than to confuse users. New channels are obviously created by using the '+' icon at the top of the channel list.
5 votes -
Adding the posting user to the post markup, to enable filtering
posted in http://forum.mattermost.org/t/marking-posts-with-the-user-who-posted-it/912, was told to post it here instead:
I've been playing with mattermost a bit and noticed that posts are not currently marked as having been posted by a specific user - the only element inside a post that identifies the poster is the UserProfile component deep inside the post component tree, so it would be very nice if a component tagged its top with a class like "post__wrapper " for easy chat log filtering: some things that this would unlock:
- hard/soft ignore lists
- hard/soft 'never miss...' lists
- hiding everyone-but-X posts to find information in the backlog
- probably more things that I don't need on a daily basis and so haven't thought of yet =)
posted in http://forum.mattermost.org/t/marking-posts-with-the-user-who-posted-it/912, was told to post it here instead:
I've been playing with mattermost a bit and noticed that posts are not currently marked as having been posted by a specific user - the only element inside a post that identifies the poster is the UserProfile component deep inside the post component tree, so it would be very nice if a component tagged its top with a class like "post__wrapper " for easy chat log filtering: some things that this would unlock:
- hard/soft ignore lists
- hard/soft 'never miss...' lists
- hiding everyone-but-X posts to find information in the backlog
- …
1 vote -
allow per-user settings for showing links inline or not, ideally per content type
from https://github.com/mattermost/platform/issues/1983, While it can be nice to have links to images, youtube videos, etc. that display inline autoexpand to the media that they link to, it would be extremely useful to have a way to turn that off, so that you just get a link instead of losing a massive amount of chat because of the inline media block.
1 vote -
Channel modes
We tend to use the channels in two different ways. Some channels are for chat; a stream of short messages. Other channels have more in-depth messages (like explanations, articles, meeting notes, etc.). In those latter channels, to communication focuses less on a single stream, and more on the replies.
Currently Mattermost solely focuses on chat streams (chat mode), having replies as an option (literally on the side).
I want to suggest an extra mode: topic mode. It differs from the chat mode in the sense that:
- The main might only show the topics (first level messages), not the replies.
- The reply sidebar should be more wider, making it possible to focus better on the replies.
- The input fields for topics might be larger by default, since it will be used for larger texts.We tend to use the channels in two different ways. Some channels are for chat; a stream of short messages. Other channels have more in-depth messages (like explanations, articles, meeting notes, etc.). In those latter channels, to communication focuses less on a single stream, and more on the replies.
Currently Mattermost solely focuses on chat streams (chat mode), having replies as an option (literally on the side).
I want to suggest an extra mode: topic mode. It differs from the chat mode in the sense that:
- The main might only show the topics (first level messages), not the replies.…18 votes -
Add Lita Integration
It would be awesome to have a way to integrate easily with Lita on Mattermost.
18 votes -
nano editor
Some of us prefer nano over vi. It can't be that big of a deal to include nano in the container, can it?
1 vote -
Comment on the posted IMG on specific elements.
My Feature Idea:
Open a Preview of the posted IMG or PDF and comment on specific elements. (For Design Teams like the feature in InVision)
Example: Comment on the button on the left side because it looks too small.
I love Mattermost and plan to integrate it in our workflow :)3 votes -
Support connecting with IRC clients
Mattermost should support regular IRC clients. A bridge require you to host an entire separate IRC server just for a couple of IRC clients, unless you want to give control to an IRC network. In addition, a bridge per definition is hackish. People speaking are not in the userlist, private messages are impossible etc.
6 votes -
iOS keyboard improvements
Currently both the iOS app and the Mobile view of mattermost (my local install is the last travis-ci build from a week or so ago) when you bring up the input box you are presented with a Send icon, on top of a Done button along with a Return on the actual keyboard. This from a user perspective is super confusing and unintuitive. I would suggest either completely removing the Send icon, or removing the Done text and that whole extra bar that ends up being drawn just to have it there. Also if at all possible changing return to the normal iOS blue button Send (for at least the app) would make it a lot clearer as to what is going on. If you leave the return and only have the send Icon (no Done button), then make return actually act as a new line rather than send, right now as far as I can tell there is no way for me to add a new line inside something I want to send.
Original: https://github.com/mattermost/platform/issues/1607
Currently both the iOS app and the Mobile view of mattermost (my local install is the last travis-ci build from a week or so ago) when you bring up the input box you are presented with a Send icon, on top of a Done button along with a Return on the actual keyboard. This from a user perspective is super confusing and unintuitive. I would suggest either completely removing the Send icon, or removing the Done text and that whole extra bar that ends up being drawn just to have it there. Also if at all possible changing return to…
2 votes -
Add autocomplete for webhooks
Sorry, I posted my idea here : https://github.com/mattermost/platform/issues/1256
Descirption :
Let me explain this through an example
I've set a outgoing webhooks triggered by "$", then sended text is parsed by my bot, and runs according command.
ie: "$start 1234" runs "start" command with "1234" args.Autocomplete hook could work like this:
I enter "$st" and press tab, the hook is triggered, sends current text to the bot and the response populates the autocomplete list with something like [{command: […], description: […]}, […]] and whatever needed by the list.29 votes -
Copying and pasting is not great
A copied mattermost conversation has three lines per message, and the first line is like "ryantm1 minute ago" and the last line is blank. It would be nice if there were cleaner ways to copy the conversations.
9 votes -
Display option to add a click count next to embedded links
Similar to how discourse (https://forum.mattermost.org/) tracks the number of clicks on a link.
Proposed spec:
1) Add Team Setting > Display > Advanced Message Display Options
Title: Advanced Message Display Options
Help text: "Advanced options for message display."
[ ] Show count of clicks next to hyperlinks in messages.
2) If zero clicks have been made on a link, show no indicator.
1 vote -
Add github integration
I think, an integration with github will become the most important feature that push mattermost among dev teams, because many companies use private github repositaries for internal software development. Btw. maybe it is related with this feature http://mattermost.uservoice.com/forums/306457-general/suggestions/9557994-add-git-hooks, but anyway I just wanted stress out particularly github.
Guys, thank you for your great work!
25 votesThere is a community integration with GitHub here: https://github.com/softdevteam/mattermost-github-integration
-
rooms for gitlab projects or issues
the gitlab integration should have chat rooms per Project or even issues.
3 votes
- Don't see your idea?