Community
Participate
Working Groups
Given Project X, and Project B depends on Project A. Select Project A, and close unrelated. B is considered to be related to A because it is downstream. So B remains open, X gets closed. Start over, select X, and close unrelated. A and B are now closed. If A is opened, the B should be considered related again, and get re-opened if I choose "yes" to open related projects. The bug is that downstream related projects are not recognized when reopening.
Another way to say "close unrelated" is to say "leave related open". So "related" should be calculated the same whether opening or closing.
There is no "open related" option when opening projects. The user is prompted to open "required projects". We can't compute downstream projects because it would require analyzing all closed projects. See discussion in bug 113178.
Every closed project was at some point previously open. You could just store a terd in the workspace's .metadata that tracks projects that got closed and were downstream dependencies at the time they were closed. If you are wrong then the worst you have done is opened a project. On a side note, this new context menuitem adds to a huge list of actions available on a project's popup. Perhaps a cascade could be used to reduce clutter. Or maybe use the "Project" top-level menu in the menubar? Why is the main project menu so much smaller than the popup menu on a project? Is that because its really the "workspace" menu ;-)
*** This bug has been marked as a duplicate of 128397 ***
Not a duplicate
No plans to support this.