General
Please search for existing ideas before posting a new idea.
144 results found
-
a way to secure self-managed Mattermost deployments...
It is possible to secure self-managed Mattermost deployments w/ Fyde (www.fyde.com)'s unified security and trusted access platform.
Fyde provides granular access controls for enterprise apps (i.e. Mattermost) and workloads, and continuously monitors access requests.
With Fyde, you can roll-out strong device authentication, improve security posture of unmanaged devices and remediate configuration errors.
1 vote -
implement a ChannelWillBeCreated hook for plugins
Implementing a ChannelWillBeCreated hook would allow plugins to react to new channel creation events and should make it possible to deny creating new channels and/or to trigger external services (like provisioning of a bot) when new channels are created.
15 votes -
add a plugin hook for search
If plugins had a hook when someone performs a search, they could customise the search experience, e.g. by querying other systems and offering those results too (maybe as an ephemeral post).
I would love to use mattermost search as our cross-platform search provider...
1 vote -
Allow plugins to add to the settings menu
Allow plugins to add to the settings menu, much like they can add to the System Console settings.
18 votes -
Plugin hook for channel header, title and purpose change.
I would like to add a string to the header and purpose every time it is changed via a plugin, but this is currently not possible as there is no hook for channel metadata in the plugin API.
23 votes -
4 votes
-
Allow Incoming Webhooks to use response_type
From: https://github.com/mattermost/mattermost-server/issues/10463
Please allow incoming webhooks to use response_type. I'm looking at making a bot that would allow others to roleplay. This bot functions by watching the channel, and when it sees a message with a trigger that has been set up with it, uses a incoming webhook to post a message with a custom picture and username before deleting the triggering message.
This gives the effect of someone being able to play different characters, especially when paired with: https://mattermost.uservoice.com/forums/306457-general/suggestions/37237117-allow-webhooks-to-post-to-reply-threads3 votes -
Allow Webhooks to post to Reply Threads
From: https://github.com/mattermost/mattermost-server/issues/10463
At the moment, the "comment" value for response_type will only trigger for the triggering message, even if that message is part of a thread. Maybe a value of "thread" can tell it to reply in the thread rather than creating another thread just to respond to the trigger message.
27 votes -
Hiding user from User directory
Right now when you click to Add new + icon beside direct message it show you directory where it show all user registered on the server.
So to protect that, a option to hide that directory will be added. To add other user you have type email address of that user from which he registered on your server.
More like whatsapp where you can msg people whome phone number you have.
21 votes -
Provide support for storage within Microsoft Azure
Provide access to Microsoft Azure blob storage through shared access signatures / keys.
2 votes -
Login with OpenShift Credentials
Leverage OpenShift’s OAuth IDP to login to OpenShift.
1 vote -
Add typescript type definitions to the mattermost-redux api-lib
Please could you add types so that developping of plugins/integrations/hooks and such may benefit from the power of type verification and auto completion.
It would, specially on API dev, be a strong plus ;)3 votes -
An integration for Zabbix
Zabbix is OSS like Mattermost easier to manage than Nagios.
2 votes -
Add YouTrack Integration
Add integration for YouTrack by JetBrains
104 votes -
include message metadata in webhook/slash http requests to help tell bot messages apart from human messages
It is currently not possible for a webhook/slash command webservice (a bot) to tell whether a message came from another bot (or this bot) or from a human.
See also the GitHub discussion: https://github.com/mattermost/mattermost-server/issues/9719#issuecomment-438320149
Summary:
Even though it is usually possible to set the displayed username to an arbitrary value when programmatically creating a post, this username is ignored when the created message is sent out via a webhook, leaving a lot of opportunity for loops.
There are 4 ways new messages (posts) can be created:
- Human types them
- Incoming Webhook
- Outgoing Webhook bot response.
- API…8 votes -
Interactive buttons supporting emoji
If the text outside the interactive button is an emoji, eg. ":smile:", it gets rendered as the smile emoji. However, if this text is inside an interactive button, the test ":smile:" gets rendered.
Similarly when dealing with "£" signs, "£" renders correctly outside the button, but inside just the text is rendered.
It would be good if emoji and other HTML shortcuts could be implemented within the buttons themselves.
2 votes -
Trigger outgoing webhook by join/leave event
This would allow integrations to welcome newly joining users.
3 votes -
add multiple channel selection for incoming webhook
System users should be able to add multiple channels instead of one channel. We have users that are creating several individual webhooks for the same hook. Is there a way to add multiple selection when setting up an incoming webhook? This will allow an easier way to set this up.
1 vote -
Bluejeans Integration
Be able to start a Bluejeans meeting with "/bluejeans" similar to Slack.
15 votes -
Use Gitlab's API to provide metadata for private resources
Gitlab projects are more often than not shielded off into private repos.
Given that Mattermost easily installs along with Gitlab (using the Omnibus installer, just by providing the url mattermost can listen on) it would make a lot of sense to have that info there; instead of a very unhelpful & confusing "Sign in" metadata63 votes
- Don't see your idea?