[COMPASS-3672] Do not lose aggregation pipeline when switching to another collection or database Created: 31/May/19  Updated: 27/Sep/19  Resolved: 27/Sep/19

Status: Closed
Project: Compass
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: New Feature Priority: Major - P3
Reporter: Kai Orend Assignee: Unassigned
Resolution: Incomplete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

When working on an Aggregation Pipeline, it can currently be lost if the user switches to another collection. Better would be to auto save it or to to ask the user to save it before leaving the aggregation pipeline builder. 



 Comments   
Comment by Massimiliano Marcon [ 27/Sep/19 ]

Closing this issue in JIRA. It's been moved to the new, unified feedback engine at https://feedback.mongodb.com/forums/924283-compass.

We are looking for input to decide how to prioritize it, so go there, look for the suggestion, vote and leave comments. If you don't find it, feel free to create a new one.

Generated at Wed Feb 07 22:33:53 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.