Community
Participate
Working Groups
Build ID: Build id: N20070723-0010 At this moment importing a Team Project Set file is divided into few steps. First you need to select a Team Project Set from the Import Wizard, on the second page you specify a file of interest. Then, after clicking Finish, work with the wizard ends but the import is not necessarily done yet. When a project(s) from the Team Project Set exists in your workspace you will be prompted whether you want to overwrite it or not. After that you could be asked to provide some additional information about repositories from the project set file (see bug 159258). I think that instead of displaying all these dialogs we could combine into one wizard (i.e. add pages to the Import Team Project Set wizard). I believe this will make the importing process more intuitive and consistent with other similar features of the workbench.
Moreover what was suggested in bug 159258 we should add the check box "show only compatible repos" and remove "show connection method".
(In reply to comment #1) > Moreover what was suggested in bug 159258 we should add the check box "show > only compatible repos" and remove "show connection method". Szymon, I'm not sure if we want to do this. Consider two cases: 1) "show only compatible repos" is off by default: A user can theoretically select a non-compatible repository location from a combo-box. After that, when he/she decides to show only compatible repositories the previous selection will be lost. The only solution I can think of is to inform a user about that fact before proceeding. But I'm not convinced to this either. 2) The option is on by default: This can lead to a situation when locations from the team project set are not preselected or even shown by default. Unfortunately, this breaks our assumption that, if the user clicks OK, the old behavior still occurs. So, once again, my proposition is to either add named separators to combo box entries (as mentioned in bug 159258, comment 28) or use Field Decorator/Field Assist to indicate type of a suggested repository location. Anyway, if that's ok with you, I believe we can log a separate bug for this issue and move the discussion there. My intention while reporting this bug was to create the wizard itself.
Both comment 1 and comment 2 seem to be more related to bug 203608 than to the original issue described in comment 0.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
