Resolve "GitLab Migration - More fine-grained status for group bulk imports"
What does this MR do and why?
This MR changes backend to create separate bulk import entity for each request provided and updates frontend accordingly
Previously, when initiating multiple imports they shared same bulk import id and had status in sync
Screenshots or screen recordings
How to set up and validate locally
(this assumes your gitlab instance is running on localhost / http://127.0.0.1:3000)
-
Create personal access token (PAT) at http://localhost:3000/-/profile/personal_access_tokens with
api
scope -
Go to New Group -> Import (http://localhost:3000/groups/new#import-group-pane)
-
Use
http://127.0.0.1:3000
as source instance (localhost
might not work) and PAT created on step one -
Setup import as following (you can use video as reference):
- Select two groups to import
- Select one group (for example
gnuwget
to targetgnuwget/something
)
-
Initiate import but clicking "Import selected on top"
-
Observe expected behavior:
- One group immediately fails with error message
- Two groups are imported, and their status change independently (Note: you might be unlucky and two imports change their status simultaneously due to 3 seconds polling. Just try again)
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Related to #330887 (closed)