The new dark mode looks and feels quite bad. Can you please see how Sequel Pro (a free product for MySQL) developed it in comparison to Studio 3T?

I would give 8/10 to Sequel Pro and 2/10 to Studio 3T for the execution of dark mode.

BTW: I am on Mac, me and my team love Studio 3T, but team laughed at the initial release...

merge mode for existing collection from two different csv during csv or json import.

Upgrade the level of JS support in IntelliShell to support current/modern JS functions (such as flatMap() and others).

I would love to have "Client Side Encryption" in Studio 3T so that I can work with my DBs/Collections data with access to my real data even if they have been "written" from another client like pymongo as an example. Non-authorized people will only be able to work with my DBs/Collection viewing only encrypted data, not real ones, within Studio 3T.

I would like the option to show the JSON view as valid JSON so that I can copy it easily into other programs.

For example I would like guid's and ISODate to be shown as strings. Currently nothing will recognise it as valid JSON due to these things.

Add the ability to change the default text of each aggregation stage (and reset to the built-in one).

I would like to be able to, for example, change the default $lookup text so that the string values don't contain spaces (e.g. localField: "fieldfromtheinputdocuments" instead of localField: "<field from the input documents>") so that I can double click to select the entire content of the string, instead of having to delete by hand.

I think that creating templates, instead of just changing the $lookup default, might be a more powerful option.

It would be really nice to have the execution time in the results of the instellishell query.

Seems so basic that I am really surprised it's not there.

It would be great if there was a way in the UI to specify a required field for updates other than the _id so that it would be possible to update on a sharded DB without using the shell. Specific use case here is Azure CosmosDB which requires a partition key on all collections and that key has to be part of the find clause for updates.

It's way too small and I basically struggle every day to see the small font. colon vs semicolon is just hard to see.

It would be helpful if you could provide a auto hide feature like the way we have in sql server and and command to show or hide results window below

Situation: You are looking at a small collection of very small JSON documents so you select JSON View. You then need to open a new collection. However, this is a is giant collection with huge JSON documents (multiple arrays of subdocuments). It's so big it can take up to 30 seconds to render and or crash Studio3T altogether. But you can't stop the operation. So just have to wait. What would fix this is an option for default collection view when opening a new collection. I would just set that to Tree View and this situation would happen anymore.

A web bug tracker for reporting and following bugs/problems similar to Mongo Jira would be very useful.

I send bugs to support, then I have to continually ping support for a status. A bug I recently reported has gone through two update cycles without being addressed, so I have to hit on support for updates.

Migrate Empty table structure to MongoDB:

I have a table without data On the SQL server.
I am doing SQL to MongoDB migration using SQL to MongoDB Migration.
But the tables without data is not creating collections in MongoDB.

Please assist in how to migrate those types of tables.

Add duplicate collection like in Robo 3T

I have two compare different sets of documents in the same collections based on different match and filtering criteria. Currently I cannot add the same collection pair multiple times to Compare Sync and apply differetn criteria to each.

If you run a script twice in intelli shell, and you use a cons x = 3, you cannot run the script again.

[js] TypeError: redeclaration of const x :

even if you change it to a var afterwards, it still produces that error.
It seems that the context is kept between running scripts?

The json view is useful for easily seeing an entire document without having to drill down like in the tree view. But being able to collapse larger parts to reduce the need to scroll would be really useful.

In locally stored collection metadata, a field could be configured to be interpreted as an _id of a document in another collection. That way, when a field with such metadata was selected, the resulting pulldown could contain a 'Jump' entry. Selecting jump would open the target collection in a new tab and find that element. It would make referenced documents much quicker to access.

When data is serialized using Protobuf, then Studio 3T may not be useful to get the values which will be in Binary format. If Protobuf serialization is supported, then it would be great to have one tool supporting multiple serialization techiniques.