Adminmattermost.org
(Moderator, Mattermost)
My feedback
68 results found
-
1 vote
An error occurred while saving the comment -
7 votes
Under review by our desktop community: https://github.com/mattermost/desktop/issues/305
An error occurred while saving the comment Updating the GitHub issue to track this feature: https://github.com/mattermost/desktop/issues/399
-
1 vote
An error occurred while saving the comment Emoji Picker (https://mattermost.atlassian.net/browse/PLT-2354) is complete and shipped with v3.8 on April 16th. Let us know if it addresses your suggestion?
-
61 votes
An error occurred while saving the comment Hi Mike, this is possible, we'd need a contributor for this. Anyone interested?
-
1 voteAdminmattermost.org
(Moderator, Mattermost)
shared this idea
·
-
4 votesAdminmattermost.org
(Moderator, Mattermost)
shared this idea
·
-
3 votesAdminmattermost.org
(Moderator, Mattermost)
supported this idea
·
-
11 votes
An error occurred while saving the comment Hi there, can you please confirm if this is still an issue for you after upgrading to Mattermost v3.4? If so, can you provide more information on the browser and device you are using to access Mattermost?
-
18 votes
An error occurred while saving the comment System admins can set who can create, edit and view webhooks from System Console > Integrations > Custom Integrations > Restrict managing integrations to Admins. You can also customize the profile picture and username that the webhook posts as.
-
12 votes
An error occurred while saving the comment Mac Desktop App v1.3 had some updates that should reduce CPU usage.
Please let us know if you've seen an improvement? You can download the latest version here: https://about.mattermost.com/downloads/
-
74 votes
An error occurred while saving the comment This feature hasn't been implemented yet but in the meantime we've added a way to reset the "new message indicator". You can read about how it works in this ticket: https://mattermost.atlassian.net/browse/PLT-3366
-
178 votes
An error occurred while saving the comment Hi @hans, per our contribution guide, before a pull request can be accepted with need an APR ticket opened, and we can't open one for FreeBSD without "Criteria #3", which is volunteers willing to test, document, support and maintain changes: http://docs.mattermost.com/process/accepting-pull-request.html
@georg, sorry, we definitely don't mean to discourage contributions. We've just had problems in the past with people submitting one-time contributions of new functionality without documentation, verification and fixes, that couldn't be supported by regular volunteers, and it caused a lot of issues that hurt the rest of the project.
Adding the APR process helps address this issue.
-
518 votes
Here’s a plugin that can be used: https://github.com/mattermost/mattermost-plugin-autolink.
An error occurred while saving the comment @Иван Найдёнов, Apologies, I've changed the status of the ticket to public.
-
39 votes
This is planned. Would anyone be interested helping with this effort as we create tickets for them?
It would be great to hear people’s feedback on what are the biggest gaps with accessibility currently.
An error occurred while saving the comment Cross-posted from: https://github.com/mattermost/platform/issues/2946
> Attachment button can't be reached via keyboard
This has been added: https://github.com/mattermost/platform/pull/2848
> Focus indicator not clear in most cases
Need help understanding this one
> Skip link doesn't work in Safari
Need help understanding this one
> Text in sidebar channel list doesn't have enough contrast (3.8:1, #7A7A7A, #F0F0F0)
> Message timestamp text doesn't have enough contrast (2.8:1, #9A9A9A, #FFF)Can anyone help add an accessibility theme (ideally with some commentary on how other community members can contribute similar themes)? https://forum.mattermost.org/t/share-your-favorite-mattermost-theme-colors/1330
> Search tooltip not linked to search field
Need help understanding this one
> NVDA causes flickers in member list
Need help understanding this one
-
5 votes
An error occurred while saving the comment In public channels and private groups, you can see how many members are in a channel. The number of users is shown to the left of the "search" box and if you click on the "little man" icon you can see who the members are.
Could you clarify what it is you're looking for in your second sentence? At the moment, the "star" in the browser tab shows that there are new messages in a team and if the icon is red with a number next to it, that is how many mentions you have.
-
253 votes
An error occurred while saving the comment ARM has been discussed internally and to set expectations, it's not likely the official Mattermost project could support ARM in the near term because of the variations in architectures, the difficulty in building a volunteer community to run the extensive monthly manual tests required to adopt a new platform
An error occurred while saving the comment Before dedicating a lot of work into this, please review the code contribution guidelines so there aren't any surprises regarding the APR process? http://docs.mattermost.com/developer/contribution-guide.html
Would be helpful to understand the use cases community is interested in having around ARM.
-
18 votes
An error occurred while saving the comment Regarding 2) - you can disable notification sounds in Account Settings --> Notifications --> Desktop Notification Sounds.
Merging 1) with a duplicate suggestion of this issue.
-
4 votesAdminmattermost.org
(Moderator, Mattermost)
shared this idea
·
-
7 votesAdminmattermost.org
(Moderator, Mattermost)
shared this idea
·
-
241 votes
Work has begun to support OpenID Connect, which enables one to use any OAuth 2.0 identity solution. It is planned for Mattermost Cloud and Mattermost Self-Managed E20.
An error occurred while saving the comment Thanks Neil, highly appreciate the feedback. There's been a fair amount of internal discussion around this.
Your help sharing more details would extremely helpful. About how many users are you aiming to serve? Are you hosting for internal use, or opening this to clients/customers, etc.? May I ask which industry you're in?
An error occurred while saving the comment Thanks Simon, definitely appreciate your offer to help. While the question of direction involves the code, internally we also consider design and support.
Regarding (1) and (2) GitLab SSO is a single provider that's manually tested and verifed in each monthly release of Mattermost, and it's repeatedly a consideration in other features we build.
As a product, we're focused on the design principle of "fast, obvious, forgiving" (http://www.mattermost.org/design-principles/) and that sets a quality requirement on SSO.
A specific provider means we're able to test, document, verify, support, repro and help troubleshoot specific issues. A generic provider is significantly more expensive to support, and there's potential to expose Mattermost users to security issues in 3rd party OAuth implementations, especially if email validation isn't done correctly.
There's a corner case where the interface for the specific provider happens to be compatible with other providers, such as GitHub and GitHub Enterprise OAuth.
In this case, there's "unofficial" documentation for variations--for example, if you use GitHub SSO each user needs to make sure their email address is set to "public" whereas that's not a requirement in GitHub Enterprise--and these variations are documented, e.g. see Step 7 here: http://docs.mattermost.com/deployment/sso-gitlab.html#github-unofficial
Could you help share more about your use case? Curious what other approaches could be considered.
Would also welcome use case feedback from others who upvoted this feature,
An error occurred while saving the comment Moving discussions on generic OAuth from different places to this feature idea forum post
Matterircd: https://github.com/42wim/matterircd/issues/29#issuecomment-176479267
Mattermost platform:
https://github.com/mattermost/platform/pull/1938#issuecomment-176077706Forum:
https://forum.mattermost.org/t/mattermost-oauth/588Mattermost core team discussed this at length and, right now, we're not ready to make a commitment to generic OAuth SSO.
Our thinking is that:
1) After its implementation, the core team would need to divert energy to test, document, support and troubleshoot generic OAuth means cutting other features.
2) Applications for Mattermost (e.g. native iOS and Android apps, connectors to XMPP, Matrix, IRC, etc.) may feel burdened to build support OAuth which could mean cutting their own planned features or even being discouraged to build in the first place.
This said, we're not experts on OAuth, and other applications do support it. We wanted to post here to get feedback from the community--and encourage upvotes from teams who would prioritize this over other features.
Updating the GitHub to track the `search in current channel` feature of this suggestion: https://github.com/mattermost/desktop/issues/399