In this article various methods of importing issues into GitLab are discussed. If you're looking for a solution to move GitLab issues between repositories check out this page.
GitLab offers an import feature which can be found on the Issues main screen:
If issues are already present, the import feature is available via this toolbar icon:
The CSV file should be structured as follows:
Instead of using commas to separate title and description you can also use tabs and semicolons.
There are several open source projects that use these APIs to facilitate importing:
Pro: there are hardly any limitations when using the GitLab API.
Con: using the API requires coding experience.
Zapier offers many integrations with GitLab:
Pro: Zapier offers a wealth of pre-made integrations powered by a point-and-click interface usable by non-coders.
Con: Most integrations are event-driven which means that every change in e.g. Trello is automatically synchronized with GitLab. If you want to cherry-pick issues then using Zapier is not ideal.
Releasewise connects to data sources like spreadsheets, CSV files, and applications like GitLab.
Importing issues into GitLab is simply a matter of dragging and dropping.
You even have the option to update the item states (e.g. "new" or "pending") of the source and destination issues while importing issues, and add comments to newly created issues.