General
Please search for existing ideas before posting a new idea.
1248 results found
-
Support moving channel without adding all members to new team first
Currently when moving a channel with CLI you must first manually add all users to new team. The CLI should automatically add missing users to new team when moving channel.
1 vote -
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 -
make Shift-Up select from the list of recent messages to reply to
Currently Shift-Up allows for a quick reply to the latest message, but what if someone just said something and the one you want is no longer the latest?
Repeated presses could move up through the message history, allowing to reply to a message that isn't the latest.
Likewise, Shift-Down (currently unused) could move down the list (and, optionally, all the way back to the main input field like Ctrl-Shift-L)
1 vote -
Closing UI for direct messages in the channel list
Mobile app for Android dose not have close UI of direct message channel in channel list. Browser and Windows client have it.
This feature should be useful when maintaining the channel list if many direct messages are opened.2 votes -
Enable Team invite link when account creation is set to false for private teams
Team invite link is not available when account creation is set to false.
Inviting users manually via email is tedious, it would be easy if the team invite link is available.3 votes -
Notificiation settings per server
If using Mattermost with more than one Server it would be great if the user could have separate notification settings or the option to mute one or more selected servers.
1 vote -
Mark Channel as "Read Only" so it remains searchable but nothing new can be posted
I often find myself searching old mattermost channels for discussion items, but many of the channels are no longer in use due to a project ending or a team getting re-org'd.
It would be cool to have a Read Only or Inactive or Abandoned mode for those channels so I can still search for previous discussions, but they won't get written to anymore.
14 votesThank you for nominating the feature! It is now available in Mattermost v5.22.0 in Enterprise Edition E20 (Beta).
-
API rate limiting whitelist
It would be really helpful to be able to specify a whitelist of IPs or accounts that can bypass the API rate limit. For instance, I use the API to batch-create lots of user accounts, which generates a high volume of requests. Yet, I don't want to allow such a big volume for any user account/IP address, just for sysops and localhost. Would this be possible?
1 vote -
Integration with smallchat
Smallchat is a live chat for visitors of our websites. It already works with slack, so it would be great if it would work with mattermost too https://small.chat/
3 votes -
Being able to kick multiple and all users at once from a channel
Expanding the
from
/kick @USERNAME
to
/kick @all
/kick @here
/kick @channel
/kick @username @username2 votes -
chat level
it is possible t create our own chat hierarchy? for example i want to create some chat on this way
1.- Client
2.- Team
3.- Project: inside here the prject cht rooms woth groups of members managed in a custom app or mattermost1 vote -
maintain right hand sidebar (RHS) open state, when switching between teams (4.1.2)
Every time I switch between teams, the sidebar closes.
I'm looking to have the sidebar open 100% of the time, because it's functionally useful and it's more cognitive load when screen looks different after every team switch (often).
3 votes -
Show slash command for in_channel integration responses
One subtle different between slack and mattermost around slash commands is that "in_channel" responses in slack also show the initial user and command. I find this helps visibility, especially if the command has arguments -
/bitbucket statusvs/bitbucket status projectfor example.https://api.slack.com/slash-commands#in_channel__vs__ephemeral__responses
4 votes -
Add a text display feature to off/on the auto-collapsed（Show More Link）
“If it includes more than 300 characters or more than 5 line breaks, the message will be collapsed and a “Show More” link will be added to expand the message.”
This Message Attachments rule is not good for quick reading.You must click the "Show More" link again and agian to read a lot of long texts.So would you mind adding a feature to off/on This?
3 votes -
Prevent users from posting ineffective @mentions while editing a post
At the moment, there is no indication whether a mention will be "effective" (i. e. it will actually trigger notifications).
This lead to confusion among our users, who intended to trigger a mention by editing an existing post, what - of course - currently doesn't work.There are two possible solutions to this:
1) Show users a warning, when their @mention will not have any effect
This could be along the lines of: "You can't trigger @mentions by editing an existing post. Please write a new post if you want to mention someone."2) Make edits trigger mentions
This would…14 votes -
Mention notifications should differentiate between “mention you” and “mentioned all”
This seems like an almost fatal flaw. I hope it can be implemented soon as it doesn’t seem like a major project!
3 votes -
Interactive Message links/flat-buttons
I really like the interaction message buttons!
https://docs.mattermost.com/developer/interactive-message-buttons.htmlI am trying to clone the /remind functionality in Slack into Mattermost, and the button interactions are working well, but the links to 'delete', 'Close list', 'view completed items', etc do not have an equivalent in Mattermost. (For now I am going to perhaps have buttons for these though it's not as flexible as I'd like)
1 vote -
Clear cache automatically at set time or do not cache data on Desktop client
On Windows, conversations are cached locally on the desktop client under the Roaming/Mattermost/Cache folder. These cache files contain sensitive information from conversations in the desktop app. I would like an option in the desktop client to either 1) disable cache completely or 2) clear the full cache on a regularly scheduled timeframe (ex. every 6 hours). Disabling cache is better as it makes sure that the conversation isn't saved to the local file system. This is important for projects that do not want any sensitive conversations available outside of Mattermost.
3 votes -
Add the posibility to have a list of teams instead of the very small squares in the teams column
The small squares of team names are very difficult to find a team in as the team name does not fit in the little square.
I would like to have the option to have a list similar to the one with topics within a team instead of those small squares.2 votes
- Don't see your idea?