MongoByte
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.
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.
|
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. |
When filtering the Atlas Project Activity Feed by Deployment name, there are no events which show when the MongoDB Version of a cluster has had their MongoDB upgraded. |
|
What would you like to see happen? Describe the desired outcome or enhancement. |
The Activity Feed shows all relevant information in relation to an Atlas cluster when filtering the Activity Feed by deployment name. |
|
Why is this important to you or your team? Explain how the request adds value or solves a business need. |
This can cause confusion when a Atlas user has various clusters within an Atlas Project, and when attempting to investigate for example, the cause of an election on a specific cluster, filtering by "Deployment" will not show this information. |
What steps, if any, are you taking today to manage this problem? |
This causes Atals Users to open Support cases or chat in order to get clarifications. This would not be needed if there were more information available in the Active Feed. |
@Guest thank you for the feature request! I'd like to gather some more information to help me triage this ticket. How are you filtering by "deployment name"? Is this referring to the "cluster name" or is it something else?