@hdelalic I've created a rough prototype that captures what we brainstormed earlier today. The big question I have is should we give the user the option to upload a file? If so, why?
We need to keep the file upload around since that is the current way of importing a group. Once we deliver the full migration feature, we may (or may not) deprecate the file-based export/import process.
Btw, the link above doesn't work for me. I see a black canvas that has no interactions.
@amandakhughes Thank you for putting this together. This flow is very easy to follow and illustrates well what we are trying to accomplish.
I would like to see a more streamlined experience for importing multiple groups. We talked about a checkbox column on the left of the list that the user can use to select which groups they want to import and only having one call-to-action button to start the import(s). Even if that's not what we end up doing in the MVC, it would be helpful to present that vision to the developers and find a way to iterate toward that solution.
@hdelalic Ah ok. I knew we were going to have checkboxes, I just didn't know if I should include it in the designs for MVC. I didn't want to confuse anyone - but I'll put them in. No problem! New designs coming soon...
I fully expect the MVC to be rudimentary (i.e. importing just one group), but would like to present the solution we are targeting. The UX with the buttons column seems like an investment in that direction.
@amandakhughes These are my notes for MVC UX from our sync call:
Need a URL and token to authenticate with another GitLab instance. Once authenticated, we should skip the auth page and go straight to the list of groups.
The group list has no checkboxes, nor the [Import all] button. It has a column with all top-level groups, a column with editable destinations, and a column with individual [Import] buttons.
Would you please look through the prototypes or attached user flows and let me know if anyone has any suggestions for the text. @hdelalic and I have revised and added text and need to see if it all makes sense.
Also, in general, let me know if anyone has feedback on the UX.
The text on the left seems the same as what we have for a New Group. Can we do custom text for when the import tab is selected? If so, something like what we did for the project import might be more appropriate. I propose: Import Group
Migrate your group from another instance of GitLab.
The titles for each block (type of import) should clearly state what each does (and how they differ). Something like: Connect directly to another instance of GitLab
Authenticate to migrate your groups directly from another instance of GitLab.
Source GitLab URL
Personal access token (from the source instance) Import a GitLab group export file
@hdelalic, @amandakhughes In my opinion Connect can be confusing, in my mind I associate it with Keep Connected, like project mirrors or Projects with connected with GitLab CI/CD. I'd use with Authenticate to import or Import directly from another GitLab instance