General
Please search for existing ideas before posting a new idea.
256 results found
-
add Slack-like integrations
Are there future plans to add integrations with dropbox, github, google drive, twitter, etc. ... like Slack has ?
49 votes -
Add Markdown support
Support Markdown formatting: that will help us get fancy with our text (bold, italic...) provide link in a convenient way (instead of dumping overlong urls) and above all format code (a must have for developers).
There are many js implementation for markwdown: I usually recommend commonmark: after all, the well tested library used by stackoverflow and github (among others) seem good enough :)
30 votesMarkdown now on master, ships with Oct 2 release.
Michael, definitely like your suggestion, perhaps it could go into a new feature idea for the community to upvote?
In terms of markdown flavor, after much consideration we went with GitLab markdown: http://www.mattermost.org/open-source-slack-alternative-adopts-markdown/
Thanks to everyone for feedback and upvotes, feature is in!
-
Nickname autocompletion
Just as simple as press tab to complete nickname of a channel member.
15 votesAutocomplete was fixed in v1.3.
-
Display full post timestamp in a tooltip
When hovering over the "5 minutes ago" timestamp on a post, display the full date and time that the post was made as a tooltip.
1 vote -
Integration with LDAP / Active Directory
Posting from Kaushik Chakraborty's original request in old feature request forum:
For Mattermost to matter inside enterprises, users should have ability to use their existing AD credentials for login. The profile management could happen like it is within MM.
Creating sign-ups for large groups within an enterprise is a massive operational hassle and it would miss all the facilities / advantages of single-sign on.Also, additional requests for LDAP from GitHub discussion: https://github.com/mattermost/platform/issues/78
128 votesSupport for Microsoft Active Directory and LDAP now available in [Mattermost Enterprise Edition](http://docs.mattermost.com/deployment/sso-ldap.html)
-
Unite messages of the same user
No need to break messages with username.
Example:
user: message
user: message
user2:message
user: messageto
user: message
message
message
user2: message
user: message5 votesSequential messages are visually combined starting in v1.3
-
Local storage of files and photos
I understand Amazon S3 is a good choice, but local storage is surely important when your server is behind a solid firewall.
17 votesNow available in Mattermost v0.6, thanks for your feedback!
-
Make message sending faster
After pressing "enter" there is a small delay before message is posted into chat. Could it be speeded up at least on user side? It's annoying.
5 votesThis is now fixed on master, thanks for your feedback!
-
Don't mark message as "1 minute ago" if it's not older than 60s.
No need for such a useless timestamp which overloads UI.
3 votesDisplays “Just Now” if less than 1 minute
-
Custom format for join messages
Firing "User has joined this channel." as regular message is not a good idea. May be it should have some special formatting to make it
a) more noticable
b) impossible to fake for regular users2 votesFormatting of System Messages such as “User has joined this channel” was updated in v1.3.
-
Option to hide email from public view
For privacy concerns.
2 votesShowEmailAddress option now supports this http://forum.mattermost.org/t/preview-documenting-config-json-settings/162
-
Add ability to use [IP address]/team instead of team.domain.com for Mattermost
This feature addresses multiple bugs being filed on install issues and should simplify things significantly.
2 votesIncluded in v0.6.0 release, available now
-
Enable installer to complete without referencing external domains
Related to multiple requests: https://github.com/mattermost/platform/issues/86
https://github.com/mattermost/platform/issues/1043 votesNow available in Mattermost v0.6, thanks for helping shape the product!
-
7 votes
Now available in Mattermost v0.6, thanks for helping shape the product!
-
Ignore slash commands containing slashes
Typing (or, more likely, pasting) a file path such as /data/some/thing in a post causes an error "Command with a trigger of data/some/thing not found". This happens surprisingly often in my workplace.
While the error does of course make sense and there are other things the user can do, I think it would be more user-friendly to disallow forward slashes in the names of actual slash commands, and do not attempt to process a word as a slash command if it contains slashes.
0 votesThe error message now also includes the option “Click here to send as a message”.
-
0 votes
- Don't see your idea?