https://twitter.com/MongoDB/status/1267452775421685760

Currently it only supports 4 languages, Java, Node, C# and Python3. I would love to see in more languages, especially Go

This is very useful when used with aggregation pipeline builder. Productivity x100

Would be nice to have ability to copy data in mongo shell compatible format. NOT like this:
{"_id":{"$oid":"58a1b4496711f017c2be2c86"},"reportedBy": "$oid":"589b5cddb8843f642c09eecd"},"createdAt":{"$date":"2017-02-13T13:27:37.594Z"}}
But like this:

{ "_id" : ObjectId("58a1b4496711f017c2be2c86"), "createdAt": ISODate("2017-02-13T13:27:37.594Z")}


Add support distinct queries in Compass.
https://docs.mongodb.com/manual/reference/method/db.collection.distinct/

List open Compass connections under "Windows" menu

Aggregations can be saved in Compass but they are only accessible in the Aggregation Builder for the specific cluster and namespace. It would be good to be able to reuse pipelines across different clusters and namespaces (e.g. I build it against my staging database but then I want to also test it in prod).

It would also be great to have a way to share a library of pipelines with the rest of the team. In the ideal scenario, pipelines would be versioned and multiple people would be able to contribute to a shared library of pipelines.

Geospatial data filtering can be displayed in Compass in Analyze Schema, but the geospatial index to make new maps cannot be made. mongo shell or embedded shell need to be used. Documentation about geospatial capabilities or at least links to the server manual would be nice.

https://www.mongodb.com/blog/post/compass-1196-gets-edgy

Everytime we open compass it starts with default zoom size 100%.

Is really annoing to have to adjust zoom using crtl + +/- everytime we open it.

It currently dumps a bunch of analysis information even though the menu item is "Share Schema as JSON". This file is useless for trying to harden or define a schema, even in non-mongodb tools (like validating documents match schema in our programs).

....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

Currently it's quite a lot of work to onboard Atlas Clusters especially if you have a lot. We have 80+. It would be a great if there was an easier way to create Cluster connections within Compass, whether that be an export/import process or you just connect it to Atlas and it works it all out via an API.

To further support this it would also be great to set username/password details and preferences like secondary at root or group level so that clusters under root or group can inherit those credentials rather than filling in for each connection

Right now, if we add a facet stage into the aggregation pipeline, we have to write the rest of the aggregation query manually. Users should be able to edit the sub-pipelines within a facet stage.

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".

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.

Compass cannot connect via ssh tunnel with SRV connection string when the MongoDB server is behind Private Endpoint.

looks like Private Endpoint appear 3 different ports for each replica.

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.