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

Touching a collection on the left hand side, wipes out your work in aggregations with no warning

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 1.43.3
    • Affects Version/s: None
    • None
    • Environment:
      OS:
      node.js / npm versions:
      Additional info:
    • 5
    • Not Needed
    • Iteration Earth (Jun 17-Jul 1)

      Problem Statement/Rationale

       When using aggregations and you are busy with your pipeline(s)

      If you left click on any of the collections on the left panel, 

      It wipes out your work on the aggregations (no warnings at all)

      Steps to Reproduce

      • Open any collection, start an aggregation pipeline
      • Enter some pipeline text
      • Left click on a collection on the left hand panel: even the same collection you are busy with
      • Wipes out your unsaved work

      Expected Results

      Not to wipe out someones aggregation work and give a warning 

      Actual Results

      All the hard work someone is busy doing to build an aggregation, wiped out in a single click

      Additional Notes

      [when we paste in an exported version of the pipeline it gives a warning, why can't we have one when clicking away]

      This makes it hard to teach people how to use aggregations, as they have to treat the left hand panel like a land mine (and all they wanted to do was to look up the name for the field)

      Proposed fixes:

      • give a warning you are about to erase your work
        • this would be bad for new user journey, they wouldn't know why the warning was there
      • don't erase and just open in a new tab
        • this would create more tabs open
        • If this could be a setting value

       

      This might need to save when the tab is in a dirty state (the user has done something) to know to show a warning

       

            Assignee:
            sergey.petushkov@mongodb.com Sergey Petushkov
            Reporter:
            sean.thomas@lexisnexisrisk.com Sean Thomas
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: