-
Type: Bug
-
Resolution: Fixed
-
Priority: Minor - P4
-
Affects Version/s: None
-
Component/s: None
-
None
-
Environment:OS: masOS Version 13.3.1 (22E261)
node.js / npm versions: v16.16.0/9.8.0
-
Not Needed
-
Iteration Hagryphus
Problem Statement/Rationale
Whenever a user tries to drop a collection(let's say collection A), and does so successfully they have to type in the name of the collection.
After that if they goto another collection(let's say collection B) and try to drop that collection as well, they see that in the prompt they still see the previously dropped collections' name(collection A).
Steps to Reproduce
Pre-requisites: 2 collections in your database
- Right click on the the first collection - A
- Click on "Drop collection" in the context menu
- Fill in the collections name in the opened modal and press the button "Drop Collection"
- Right click on the the second collection - B
- Click on "Drop collection" in the context menu
Expected Results
After step 5, the expectation would be to have the collection A's name removed from the input.
Actual Results
After step 5, the actual result is that collection A's name is visible in the collection B's Drop Collection Modal
Additional Notes
Any additional information that may be useful to include.
- is duplicated by
-
COMPASS-6791 Collection's name already pre-filled when dropping a collection
- Closed
-
COMPASS-7152 "Drop collection" name confirmation field is not cleared
- Closed