Uploaded image for project: 'Compass '
  1. Compass
  2. COMPASS-3010

Usability issues with MongoDB Compass 1.11 (Query Bar, Hotkeys & Saved sessions )

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 1.11.1
    • Component/s: Connectivity, Query Bar
    • Labels:
      None
    • Environment:
      Windows 7, MC 1.11
    • Needed

      Hello,

      We've identified below issues in MC 1.11.1, please let us know whether they've incorporated 1.14

       

      • Query bar issue : It was so evident that (with MongoDB Compass 1.11.1) when we type the query swiftly the Query bar behaves bizarrely as mentioned below. But when we tested the same collection, db and query with Compass 1.8.1 we don’t see that issue at all.

       

      There seem to be issue with MongoDB Compass application – when we type filter it freezes and prints typed characters in a wrong order. E.g. if we quickly type “{state: “ it results in something like “

      {statetate: }

      ” or “{te: sta”.

       

      • Hotkeys : Ideally We are looking for keyboard shortcuts like other IDEs/GUIs have, for example executing query ( E.g., SQLyog has “F9“ to execute the query ) instead of doing it with mouse ‘FIND’ button from GUI. Please let us know when can we have this functionality.
        Online documentation only mentions mouse click “Click Find to run the query and view the updated results.”

       

      • ** Saved session/connections :  When we reboot system/pc and relaunch the MC application, we're losing all the previously saved sessions/connections - hope this has been fixed in MC 1.14.x

        1. compass1.png
          compass1.png
          132 kB
        2. compass2.png
          compass2.png
          228 kB

            Assignee:
            Unassigned Unassigned
            Reporter:
            srinivas.mutyala@citi.com Srinivas Mutyala
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: