....but I can only refresh all the db's, and that loses the selection and I have to go find it again. There are sometimes hundreds of db's in a cluster and the list of databases is not ordered alphabetically (or otherwise that I can tell) and has no db search so its a constant exercise in scrolling to refresh the collections in a db

It should be possible to import a raw execution plan generated with .explain(), and have it visualized in Compass!

Why - so we as developers don't need to read the JSON manually.

This would be very usefull when debugging slow queries using the aggregation framework.

/Alex

We use color context for ssh terminals when connecting to a production vs qa environments. I've noticed you can color context a Favorite. But if you color only the favorite button, it doesn't give you a full view of if your in production or not.

Suggestions:
* Add that color to the background of the title area where the collection name, document count, total size is.
* On the row view section. maybe just a small color icon on the left empty space of each row.

It could be very useful a command such as "Ctrl+R" in Ubuntu, where you can type some letters and find a command from the command history.

For instance, if I executed "use mydb", "mydb.mycollection.find()" and "use anotherdb", by typing "Ctrl+R" and "use m", there should be anything such as in the ubuntu's terminal that autocompletes the command "use mydb".

I frequently have documents with a lot of fields and it's quite annoying to keep needing to click on SHOW # MORE FIELDS - it would be a nice feature to eitehr
- always show all fields
- after opening, choose to show all fields in current view

It would be nice to choose a custom color for my favorites. Or at least increase the color options (for example all of the colors on this palette https://flatuicolors.com/palette/defo)

Provide the ability to explicitly deny a privilege on a specific resource.

Example: Grant the privilege to perform the find action on all collections in the test database except "test.secrets".

It would be nice for Compass to be easier to read for those with eyesight issues.

Nobody cares about how many plugins are still loading. Show the connection screen at least and load the plugins in the background. Also, by default have no plugins because why should I wait for plugins to load that I don't use? Also load plugins in parallel.

When attempting to connect to a cluster which is not reachable (i.e. localhost when you don't have a mongod running, or Atlas when you haven't whitelisted your IP), Compass blocks any user input until the connection request times out.

I do this periodically when my home IP gets changed, or I just make a mistake. I generally work out what's happened in <5s, but I have to wait for the connection to time out (30s?) or quit Compass in order to change/retry.

It would be much nicer to have a button to stop/cancel a connection request.

When adding a value, I cannot use my keyboard to switch between data types (like a typical dropdown).

Example, if I use TAB, it should highlight the dropdown, then I can hit "T" which would automatically select timestamp.

This is the normal function of dropdowns in the web - since this is an Electron app, it shouldn't be too difficult to implement.

even if you click on two refresh buttons (see the attached print screen), Compass does not update the information

Support Citrix as a new Compass platform

It's impossible to tell them apart without reading the tooltip (which takes a bit time to show)

Currently, there is no way to provide Client Side Field Level Encryption options inside of MongoDB Compass. We'd like to be able to provide AWS KMS details to Compass and have it decrypt read values if the user provides the correct credentials to access the Master key.

The Node driver which Compass is built on seems to be supported so having a way to provide the AWS KMS creds needed inside of Compass would be very helpful for us.

1. Run a query that returns a document with subdocuments.


2. Click the ">" to expand some of the subdocuments.


3. Open a new tab


4. Come back to the previous tab.

Notice how all expanded subdocuments were closed. This is pretty annoying if you need to, for example, go through array items and run queries in the other tab based on their values.