General
Please search for existing ideas before posting a new idea.
- or
22 results found
-
Support CAS integration (Central Authentication Service)
THe idea is to suppor CAS integration (Central Authentication Service), as Gitlab does for example. It's a SSO system.
CAS is used in many universities, and supporting it would favorize deployment of mattermost in such environments.
36 votes -
GitLab SSO OAuth SSL Client Certificate
On servers where GitLab+Mattermost are hosted and require SSL client certificates for all connections, Mattermost fails to get a token from GitLab OAuth because its request does not include a client certificate. Please add an option within config.json to include an SSL client certificate within "GitLabSettings" for those requests. Optionally add other SSL-related configurable fields just as CA validation, etc.
27 votes -
Have the option to configure special/specific notification sounds based on keywords
Currently it is not possible to have notifications triggered based on keywords, for example if there are any emergency keywords, a certain ringtone or vibration (or both) will be triggered.
This would be important in the event of any emergency that requires immediate action.
151 votes -
allow users to 'follow' others to create a filtered feed view.
Currently we have an in-built equality of posts which can become inefficient with high volume.
Recognizing the importance of hubs in scale-free network growth, we could allow for a filtered view of the main town-hall feed, where you just saw the posts (and related threads) of those you choose to follow.
One could also toggle back to the unfiltered view, but allowing people to cluster could make high volume teams more manageable.
Unlike Facebook, the user would remain in control - with no algorithm and the ability to toggle back to the unfiltered view.
9 votes -
JIRA Integration Channel Notification/Subscribe
Support all issue status update event transitions, not just only status changes when the ticket is reopened, or when resolved/closed, and assignee changes.
We use the issue status transition to trigger the QA Team to start work. Would be nice to have these notifications via the Mattermost Integration
40 votes -
Trigger outgoing webhook by join/leave event
This would allow integrations to welcome newly joining users.
3 votes -
Include user's language in body of outgoing slash command request
Currently, outgoing Slash commands send in the request body information about the user like userid and username.
However, to properly internationalize a slash command integration (such as https://github.com/jedfonner/MattermostOnFire/issues/2), the receiving system needs to know the user's specified language (from Account Settings > Display > Language).
Please add a "user_language" field to the JSON object passed in the body of the message sent by Mattermost outgoing slash commands. This field should be populated by the user's language (e.g., en-US, es-MX, fr-CA, etc).
8 votes -
Stop sniffing the User-Agent, use feature detection
The Mattermost web interface uses the User-Agent of the browser, which is a bad idea because browsers can (and do) anyway lie about which browser they are.
As a matter of fact, right now Mattermost will give a warning (and not work) when e.g. using Epiphany (the GNOME Web browser), but changing the User-Agent does work. Because its engine is WebKit, which makes it to support almost everything that Safari does (and Safari is in the list of supported browsers).
What Mattermost should do is feature detection. More info at: https://github.com/mattermost/platform/issues/3353#event-703118004
25 votes -
Plugin hooks for access control and logout events
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
16 votes -
Off The Record messaging
Implement off-the-record messaging (https://otr.cypherpunks.ca/)
1,040 votesTicket for this feature can be followed here: https://mattermost.atlassian.net/browse/MM-669
-
More events support for Mattermost Webhooks
I would like to see more support for Jira events for Mattermost Webhooks, other than just; Issue: Created, Updated and Deleted
Especially would like to see events for Created, Updated and Deleted comments
8 votes -
Support for the Slack Real Time Messaging (RTM) websocket API
The RTM API allows integrations to connect to slack from behind a firewall, seemingly connecting much like a normal desktop client might, from any computer, not just an externally visible server.
It's a very important enterprise feature for those wanting to integrate Mattermost with their internal applications.
Further discussion on this can be found here:
https://forum.mattermost.org/t/does-mattermost-support-real-time-messaging-api-from-slack/1287/2And this slack FAQ describes the differences between the Events and RTM API's:
https://api.slack.com/faq#events_apiThis is the Slack RTM API spec:
https://api.slack.com/rtm63 votes -
Have ability to close a channel without leaving it
Currently it is not possible to 'close' a channel without leaving it, or remove it from the sidebar. This can be problematic when you are a part of many channels, especially private ones where you will need to be re-invited to it after leaving it. For example, I would still like to be part of a particular private channel in the event that something comes up, but I would like to have the option to close it/remove it from the sidebar to avoid clutter.
Right now there is no method to close a channel from the sidebar and still…
7 votes -
Integration with Miro collaborative whiteboarding
Miro (https://miro.com/) is a collaborative whiteboarding system popular with (interaction) designers but also used in research and strategy planning.
Microsoft Teams allows the following events from Miro to be shown:
- invitees sign up
- board is shared with you
- there's a new comment or a reply to your comment on a board
- someone @mentions you in a comment or reply.
Source: https://help.miro.com/hc/en-us/articles/360017572514-Microsoft-Teams
It would be nice to have a similar integration in Mattermost.
21 votes -
7 votes
-
Have the ability for system admin to set channel admins via system console
Currently, channel admins can only be set by other channel admins. In the event that a channel does not have any admins (if the only admin accidentally left the channel or team for example), there is no way to set an admin for that channel outside of doing a manual SQL query.
It would be much more convenient if there was an ability to set channel admins via the System Console for example to handle situations like this
3 votes -
Put a timer on Banners
We use time-sensitive banners to inform users of ongoing events. If we don't manually disable them, they will run past the event. Could we put an end time on banners, the way that there are end times on statuses?
1 vote -
Improve reporting on invitation lifecycle
Currently, nearly no information is exposed to admins about what is happening with invitations individually, or even in aggregate. On any workspace with restricted teams it's important to be able to identify how any individual user was added to a restricted team. In the event that a user who should not be there is added, finding out how they were added so process, rules, etc. can be updated is critical. The critical piece of this is being able to track invites on an individual basis. This shouldn't require any user interface changes, just additions to…
1 vote -
Delete User (to be GDPR conform)
The european unions new general data protection regulation grants user the "right to be forgotten" (Article 17, GDPR). Event though Art. 17. (1) a. grants the exception, that data does not have to be deleted if it is still necessary for the purpose it was collected or processed, it is questionable if this exception is applicable.
I understand the effort to maintain a consistent history of conversations and interactions and therefore not implementing a deletion of users and the work it takes to implement a compromise between guranteeing the data subjects right to be forgotten and consistent conversation…
1 voteWe do have a CLI tool for deleting a user that I think should cover what you’re looking for: https://docs.mattermost.com/administration/command-line-tools.html?highlight=cli#platform-user-delete
Let us know if it looks like that will work, or if there’s anything missing from it!
-
Option to Disable Channel Sorting Based on User Join/Leave Activity
I would like to propose an enhancement to the current channel sorting functionality. Specifically, I would suggest making it possible to sort channels based on activity, while excluding user join/leave events from influencing the sorting order.
The current activity-based sorting is useful for keeping active conversations easily accessible. However, frequent user join/leave events can also cause channel reordering, which may lead to unnecessary disruption, especially in larger teams or public channels where such events are frequent.
2 votes
- Don't see your idea?