Share your ideas with us

  1. Apple Silicon Support

    Provide build able to run natively on macOS ARM/M1 (native JDK).

    28 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Flag idea as inappropriate…  ·  Admin →

    We are working on this and are currently waiting for some 3rd party library dependencies to be resolved for Apple’s M1 chipset. We are looking to release a native M1 build as soon as possible.
    In the meantime, please make sure to download Rosetta. We have tested Studio 3T extensively via Rosetta and it should run without limitations.

  2. Remember Query Builder Size

    Currently, the Visual Query Builder takes up ~40% of the screen until it is resized. Once resized, if a new collection is opened, the visual query builder for that tab is also the default size.
    It would be great to have 3T remember the last size used.

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    started  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Follow reference shortcut

    I use the "follow reference" action quite intensively and it's one of the very few actions without a shortcut.

    That would be a huge productivity boost given my dataset.

    Thanks!

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. configurable execution time format

    I think a recent update changed the execution time displayed in the lower-right of the window from milliseconds to what appears to be hh:mm:ss, which is helpful for longer-running queries but not great for anything under 1 second for fine-tuning. Hovering over the time gets me that data, but I'd love to be able to configure it to be one or the other, or even show ms if under 1 second.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    started  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. Be able to work in two+ JSON editor windows simultaneously

    Currently it is only possible to open a single editor on one document, or to view one document and edit another, but it is not possible to copy json from the viewer window to the editor.

    It would be incredibly useful to be able to work with 2+ editor/viewer windows at the same time.

    Currently we must copy a document into another editor, like VSCode, to be able to copy sections into a Studio3T editor window or to work on two or more documents at the same time.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    started  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. Using SQL reserved keywords in MongoDB SQL

    Suppose I have a collection named 'group'. Currently, I am unable to execute a SQL query on this collection as this is a reserved keyword in SQL and, though, manipulations like using ['group'] in SQL query don't throw any error, no result is fetched either

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. Allow to edit multiple documents as JSON

    When editing a document as JSON (ctrl+J), it is a modal window, and we can't do anything else on mongo while this window is open.
    Moving to an another document to make some copy/paste, or view data on other documents while editing the first one will be great.

    9 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    started  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. [BUG] CN for x.509 connections

    I don't think maybe when you upgraded your SSL as referenced in this post (https://studio3t.com/whats-new/ssl-protocol-security-upgrade/) you didn't catch all the edges.

    I can't get newer versions of 3t client to connect to a replica set via x.509. Even with "allow invalid hostnames" checked. The "discovered" entries for the replica set are contained in the SAN part of the cert presented by each node. Mongo v3.4, same URI and certs connect just fine with older MongoChef 3.6. Happy to send along the certs and connection uri.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. Native Apple M1 support

    Apple M1 devices are out for several months now. A native M1 support would be highly appreciated

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    We are working on this and are currently waiting for some 3rd party library dependencies to be resolved for Apple’s M1 chipset. We are looking to release a native M1 build as soon as possible.
    In the meantime, please make sure to download Rosetta. We have tested Studio 3T extensively via Rosetta and it should run without limitations.

  • Don't see your idea?

Share your ideas with us

Categories

Feedback and Knowledge Base