Use progress track when importing single relations

Rodrigo Tomonarirequested to merge
rodrigo/disable-progress-tracking-in-sigle-relation into master

When projects are imported via the Single Relation Endpoint, different import files can be provided.

This change updates the process track to scope the tracking per tracker_id to avoid conflicts.

References

Please include cross links to any resources that are relevant to this MR. This will give reviewers and future readers helpful context to give an efficient review of the changes introduced.

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before After

How to set up and validate locally

  1. Export a project
  2. Download the archive file and extract it
  3. Open the issues.ndjson
  4. Remove all rows except for one.
  5. Update the issue's IID as the latest project IID plus 1.
  6. Save the file
  7. Repack the project archive using the following command: tar -C extracted_folder_path -czf new-project-archive.tar.gz .
  8. Import the archive using the single relation endpoint to the same project from step 1
curl --request POST --header "PRIVATE-TOKEN: ACCESS_TOKEN" \
  --form "path=project/path" \
  --form "relation=issues" \
  --form "file=@new-project-archive.tar.gz" \
  "https://example.gitlab.com/api/v4/projects/import-relation"
  1. The issue should be imported.
  2. Repeat steps 5, 6, 7, 8, 9
Edited by Rodrigo Tomonari

Merge request reports