It blocks my data and uses up valuable screen real estate.

Compass users with many deployments need the ability to:

- reorder favorites, possibly based on usage patterns, as well as,
- organize favorites into folders.

These features will allow users to efficiently access important connection favorites, even when there are a large number of deployments present.

For the Compass saved "Favorites", is it possible to save the Fav specifically without the LDAP Password and the without the Client Key Password? Instead leave them blank as a favorite, so I can then enter them each time logging in?

The reason is if the MongoDb has PHI data, and if I lost my computer, a hacker could not just click to open and gain immediate access. Thank you.

The filter query Export to Language feature would be more useful for developers if it included support for the filter options:
- PROJECT
- SORT
- SKIP
- LIMIT
- COLLATION

Right now it seems favorites are sorted by least recent created. When you have a bit more (I have 9) it would be great to have them sorted by name instead. Or otherwise, sort by most recent used, or allow to sort manually.

As a user of two or more favourites, and who cycles between them both frequently, I would like the ability to double-click on the favourite connection in the sidebar so I can quickly connect to the connection. This would speed up my journey from disconnecting from one connection > clicking on the favourite for the other connection > scrolling down to click the primary "connect button" > connecting. With it I could simple double-click to connect.

The icons in the toolbar of the map view look very similar. I mistakenly selected "polygon" when I wanted to select "circle". This mistake can be prevented by designing the icons with more differentiation e.g. Using a more pronoucned shape, angle, fill or border. Ideally, at a glance, the two shapes should be distinct and self-explanatory.

It would be nice to include the mongo shell within Compass.

The current Aggregation Pipeline Builder is good for authoring pipelines, but not so much for running them. The final results are limited to 20 docs and not easy to view, and viewing the intermediate stage outputs can slow down performance. There should be a way to execute a pipeline and page through the complete results.

Update on Shard Cluster in Document Tab

Provide a histogram of commonly slow queries since entering the performance tab or pressing PLAY. Same as hottest queries but over time. Sum the query milliseconds over each invocation of the query shape.

While one specific query may be slow at any given time. The best practice in performance troubleshooting is to optimize the queries that are consuming the maximum total time when aggregated together. So, a relatively fast query that is extremely common may consume more resources in the mongod than a very rare query that is relatively slower.

I would like to have multiple connections in a single Compass window so that I don't have to have multiple windows open when working across many deployments.