Community
Participate
Working Groups
In the final page of the import wizard, GitProjectsImportPage, the text field does not actually do anything. Looking at the code, it filters based on what items are checked and not actually what's in the string of the imported projects.
Only unselected entries are affected by the filter. So you have to unselect before filtering. This behaviour was intended to ensure that selections made by the user are not lost by applying a filter.
(In reply to comment #1) > Only unselected entries are affected by the filter. So you have to unselect > before filtering. This behaviour was intended to ensure that selections made by > the user are not lost by applying a filter. Are you suggesting this behaviour is correct or are you merely describing the current behaviour?
Works as designed. We had a feature request to do it in this way to avoid selections becomming invisible. To soften the possible user confusion we added the hint "type filter text to filter unselected projects".
This is very confusing behavior given that out of the box everything is selected. The user has no clue about the current "smart" behavior".
*** This bug has been marked as a duplicate of bug 362051 ***
It reuses similar code but this one is for projects whereas bug 362051 is for branches.
Ping!
When changing the filter in GitProjectsImportPage to not always return true if the element is selected, the problem is that getCheckedProjects does not return the selected but hidden projects (hidden due to filter). Maybe this could be fixed by not querying the widget for the checked elements but instead keeping a set of checked elements separately and updating it in the addCheckStateListener. We should also show a hint of how many projects are selected including the hidden ones, so that it's clear that they will also be imported.
