The Clusters > Collections > Find option offers an auto-fill drop-down of previous entries, which is super helpful. However, it seems to offer suggestions from previous queries of all the Collections. This is not helpful, since Document keys tend not to overlap across Collections, so it would be even more helpful if the drop-down only listed previous queries from the selected Collection.

Please provide the option to include database username, password and role information during a Live Migration. DBAs often do not have direct access to database credentials and have to collect them from the various development teams.

Please add the capability to enforce 2FA (As a setting) for any user invited to join a team. This would be a good step towards better security management

Confluent cloud -Mongodb Sink connector requires Atlas whitelist IP to 0.0.0.0/0 which is a security issue on our side. Can mongodb partner with confluent and provide a solution that can be accessed through VPC private link? We are very interested in mnogodb Sink Connector for our solution so we don't have to maintain aws ec2 instances for the sink connectors.

https://www.confluent.io/blog/confluent-cloud-offers-kafka-mongodb-connector-fully-managed-clusters/

Add some way to restore old aggregations pipelines from history, that way, even if I accidently closed the UI. I will have backup.

Provide a per cluster mechanism to shut off client access for restore operations.

Please could you extend the modify cluster API so that when an M20+ cluster is downsized to the next smaller size, the API command executes a sanity check to see if the smaller size has sufficient resources?

Return a 40x if the smaller size has insufficient resources.

Many user have Production systems that don't need huge resources over night so smaller machine size is sufficient

The cloud atlas frontend is very buggy, and not usable at all, even with a fast connection takes minutes to load a page on click.

https://cloud.mongodb.com/

I think we are loading all the components and required data from server side.
Instead we can simply load the core components, and show a user friendly spinner, that will stop spinning once content is loaded via an XHR request. This would be so much more user friendly, just showing them a spinner (maybe estimated time as well).

Currently the page stays blank white, which is terrible UX.

To avoid use of terminology that for some will have racial connotations remove the term "whitelist" from the Atlas UI.

When connecting to a Atlas cluster and selecting to connect via a Application you can select to connect with what "Driver" where you can select "Python".

For new users, they might think that the Python library (https://www.python.org/doc/versions/) is what is being referenced when in reality Atlas is referring to the PyMongo Driver.

For clarity, alter the UI from "Python" to "PyMongo" or "Python (PyMongo)" or something similar to differentiate between Python and PyMongo.

1)User A login inot Mongo Portal
2) He selects an organization and sends an invitation to User B
3) Now in the Activity Feed menu we can see User B was invited to the organization
4)Before the user B accepts the invitation , User A goes and deletes the pending invitation
5)Nothing is shown in activity feed.

This would help products which are integrating with MongoDB atlas to get the true status of pending invitations.

1. Add a collection


2. Add an object field


3. Add a string field to that object. Call it _id.


4. Enter some value Save it.


5. Try to Edit by clicking on the edit button.


6. Try editing the value of _id (string) field. Not happening.

main menu should provide access to manage users

a faster mongodb compass installation that is taking forever to do so.

The Stitch confirmation and reset password emails for the Email/Password Provider are now only in English.

A page where you could translate these emails, would be very useful.

Now we must use the function method, which is more work. I suspect a lot of people would want this feature (all non English markets).

I wish they could provide the arn service with lambda.

when creating a private link, the resulted dns for the cluster is in the form of "cluster-pl-.{somerandomstring}.mongodb.net"
the only difference from the public endpoint is the 'pl' addition in the first section.

in order to configure the vpn wildcards and rules,
it can be extremely helpful to have this separation more general, for example
cluster.{randomstring}.pl.mongodb.net -- private links
cluster.{randomstring}.mongodb.net -- public

that way we can use the wild card *.pl.mongodb.net to differentiate and route the traffic accordingly