-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Environment:OS:
node.js / npm versions:
Additional info:
-
5
-
Not Needed
Problem Statement/Rationale
Problem (actual result): If a user starts creating or editing an aggregation and then switches to another collection via the left sidebar without saving the aggregation, the aggregation that they were creating or updating is not saved.
Desired action (expected result): If a user starts creating or editing an aggregation and then tries to switch to another collection via the left sidebar without saving the aggregation that they were working on, ask the user if they are sure about switching to another collection or if they want to save their aggregation before doing so.
Steps to Reproduce
- Make sure you have at least 2 collections in your db.
- Create an aggregation for one of the collections. Do not save it.
- Without saving the aggregation, click on a different collection via the left sidebar.
- Go back to the previous collection (the one you were creating an aggregation for) and check to see if the aggregation that you created is still there.
- Repeat steps 1-4, but update an existing aggregation instead of creating a new one.
- duplicates
-
COMPASS-5022 Touching a collection on the left hand side, wipes out your work in aggregations with no warning
- Closed