Skip to content

General

Please search for existing ideas before posting a new idea.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

269 results found

  1. include a Trace option in the logging modes.

    We were having an issue that was causing Mattermost to continually crash for no apparently reason. Nothing was consistent in the log files, debug didn't give enough information, heck I even did an strace on the PID and wasn't able to get anything useful. A Trace option should include DB calls, perhaps a transaction ID to link the API call to the DB call...

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. improve profile images by offering arbitrary size with cropping/centering

    from https://github.com/mattermost/platform/issues/1981, Currently you have to click a button in order to select and image, and it has to be a rectangular image already. Instead, it makes sense to do things more like twitter or flickr, where you can either click-to-browse or just drag-and-drop an image onto the UI, and then the UI gives you the option to crop and scale, so you can pick any image and then just select the rectangular subsection you want to have act as your profile picture.

    13 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. make administrators get a notification when new channels were created

    When users create new channels, there currently seems to be no notification emails send to administrators neither when a new channel is added nor who this channel added. This prevents administrators from being informed proactively about misbehaviours of users (i.e. if users create non corporate/private information exchanges on the system). A moderator feature would be very appreciated to help the IT securing itself and not having to explain the CEO why there is a public channel for exchanging illegal content, for example.

    9 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Secure direct messages using TextSecure/Axolotl algorithms

    Secure direct messages (and may be messages in private groups) using TextSecure/Axolotl algorithms. Unlike OTR protocol this will enable sending secure offline messages. I think TextSecure library could be used https://github.com/janimo/textsecure

    17 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. add support for syslog output

    It's a pain to deal with many scattered logfiles, so syslog support would be a welcome alternative.
    The only extra configuration despite enabling, and the loglevel should be the syslog facility.
    https://github.com/mattermost/platform/issues/1820

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. make an admin be able to differ between inactive and disabled users

    The problem of the current situation is, that an administrator yet is only able to set an user account status to "inactive". This means more a disabling of the user, because the user is in no longer able to log in. In fact, he is locked out.
    It would be more appropriate to rename the status "inactive" to "disabled".

    A new status "inactive" should be introduced where a user is in fact using the featureset of a "team edition". No license is acuired for this user and he doesn't get any push notifications anymore until he logs in again. By…

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Sync between redundant servers

    In 2015, GitHub user titanous proposed adding support for more than one instance of the API server. (https://github.com/mattermost/platform/issues/402) It was suggested that it would be added before the 1.0 release, but the issue has since been closed without any changes. Since I didn't see this feature requested in this forum, I thought I would post it so that the community can vote on it.
    I work with a team of five, all of whom have personal servers, one of which hosts our Mattermost instance. It would be useful for us if we could host as many as five…

    7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. nano editor

    Some of us prefer nano over vi. It can't be that big of a deal to include nano in the container, can it?

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Add a whitelist which protocols should be linkified

    See https://github.com/mattermost/mattermost-server/issues/7657 for details.
    TL;DR: It's not very useful to convert e.g. foo:bar to a link.

    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
1 2 10 11 12 14 Next →
  • Don't see your idea?

Feedback and Knowledge Base