| Summary: | [context] removing a project from the context does not always remove all elements from all models | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Shawn Minto <shawn.minto> |
| Component: | Mylyn | Assignee: | Shawn Minto <shawn.minto> |
| Status: | CLOSED MOVED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P2 | CC: | steffen.pingel |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
Shawn Minto
I think that we should look into this for 3.5 since this could be too risky for the 3.4.2 release. Steffen, what are your thoughts? What we will have to do to make this work is to look at all bridges for manipulations to make sure that we remove all of the elements, but we want to make sure that we don't duplicate efforts and ensure that the performance doesn't degrade. I will see if I can put together a patch for this so we can determine if the risk is low enough for a maintenance release or not. Yes, let's put that off. I haven't seen any reports of this before. Can users always recover by removing invisible elements from the context tab? Yes, they can recover by removing invisible. I never noticed it before either until I started investigating the remove from context problem. Mylyn has been restructured, and our issue tracking has moved to GitHub [1]. We are closing ~14K Bugzilla issues to give the new team a fresh start. If you feel that this issue is still relevant, please create a new one on GitHub. [1] https://github.com/orgs/eclipse-mylyn |