Skip to Main Content

MongoByte MongoDB Logo

Welcome to the new MongoDB Feedback Portal!

{Improvement: "Your idea"}
We’ve upgraded our system to better capture and act on your feedback.
Your feedback is meaningful and helps us build better products.

Status Future Consideration
Categories Atlas
Created by Shawn Hawkins
Created on Nov 14, 2025

Enable Customers to Prioritize Maintenance for Non-Production Environments

What problem are you trying to solve?

Focus on the what and why of the need you have, not the how you'd like it solved.

Customers managing multiple projects currently lack control over which project or cluster is prioritized for upgrades. Many customers have separate production and non-production (e.g., staging or testing) environments, but they are unable to prioritize upgrades for non-production clusters. This makes it difficult to test upgrades in a non-production environment before applying them to production.

What would you like to see happen?

Describe the desired outcome or enhancement.

Provide customers with the ability to prioritize non-production environments for upgrades within their Atlas organization. This ensures that production projects are not upgraded before non-production environments, allowing customers to perform application testing and identify potential issues prior to upgrading their production environment.

Why is this important to you or your team?

Explain how the request adds value or solves a business need.

This approach will minimize unnecessary production impacts, as customers can identify issues in non-production environments first. It improves customer satisfaction, reduces high-severity cases, and provides a more logical and efficient upgrade process.

What steps, if any, are you taking today to manage this problem?



  • Admin
    Anurag Kadasne
    Dec 5, 2025

    Hi, thank you for sharing your use case. This is on our near term roadmap, we will inform you once the feature is rolled out.

  • Dave Gotlieb
    Nov 24, 2025

    This is a minor issue for patch releases, but becomes much more of a risk for minor version releases. Without the ability to 'approve' of a new version ahead of Atlas automation applying it in no particular order, the risk is significant to Production environments where untested version upgrades (even patches can cause risk) can get to Production without proper time for Application Owners to test these changes in lower environments and then schedule the Production Upgrade window.


    This does not have many up-votes, but please put this into priority for a solution.

    Regards,

    Dave Gotlieb