Top Level Data Explorer

XMLWordPrintableJSON

    • Type: Epic
    • Resolution: Gone away
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Data Explorer
    • None
    • Top Level Data Explorer
    • Developer Tools
    • Needed
    • Hide

      1. How does this change affect a user?
      2. Why would a user want to use this?
      3. What command or series of steps does the user follow to make this change?
      4. What is the expected result?
      5. Can this affect database performance? How?
      6. Is there a minimum or maximum setting for this change (if this is a configurable parameter)?
      7. How could the user break something by using this incorrectly?
      8. Is there an ideal setting or way of using this feature?
      9. Does this feature affect any other settings or parts of the product?
      10. Does this feature affect upgrade / downgrade compatibility?
      11. Does this replace some other thing that we should downplay / retire / remove?
      12. When are docs required? Iteratively throughout the project, at project close/feature release, or whenever the Docs team is able to prioritize after release?

      Show
      1. How does this change affect a user? 2. Why would a user want to use this? 3. What command or series of steps does the user follow to make this change? 4. What is the expected result? 5. Can this affect database performance? How? 6. Is there a minimum or maximum setting for this change (if this is a configurable parameter)? 7. How could the user break something by using this incorrectly? 8. Is there an ideal setting or way of using this feature? 9. Does this feature affect any other settings or parts of the product? 10. Does this feature affect upgrade / downgrade compatibility? 11. Does this replace some other thing that we should downplay / retire / remove? 12. When are docs required? Iteratively throughout the project, at project close/feature release, or whenever the Docs team is able to prioritize after release?
    • Atlas Clusters
    • AD: We'll want to slide this into the left nav, so we may need to coordinate with Atlas team on this.
    • In Progress
    • None
    • 🔵 Done
    • None
    • Hide

      2026-06-22 - 🔵 Done
      No project update provided

      2026-06-22 - No confidence status provided
      No project update provided

      Add updates here

      Show
      2026-06-22 - 🔵 Done No project update provided 2026-06-22 - No confidence status provided No project update provided Add updates here
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Epic Summary

      Summary

      Move Data Explorer outside of the existing cluster hierarchy, improving screen real estate and allowing users to access Data Explorer without first navigating into a cluster. 

            Assignee:
            Unassigned
            Reporter:
            Patrick Lowry (Inactive)
            David Hou David Hou (Inactive)
            None
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved:
              12 weeks
              None