Issues can be imported to a project by uploading a CSV file with the columns
description. Other columns are not imported. If you want to
retain columns such as labels and milestones, consider the Move Issue feature.
The user uploading the CSV file is set as the author of the imported issues.
You must have at least the Developer role for a project to import issues.
- Consider importing a test file containing only a few issues. There is no way to undo a large import without using the GitLab API.
- Ensure your CSV file meets the file format requirements.
To import issues:
- Go to your project’s Issues list page.
- Open the import feature, depending if the project has issues:
- Existing issues are present: Select the import icon at the top right, next to Edit issues.
- Project has no issues: Select Import CSV in the middle of the page.
- Select the file you want to import, and then select Import issues.
The file is processed in the background, and a notification email is sent to you after the import is complete.
To import issues, GitLab requires CSV files have a specific format:
|header row||CSV files must include the following headers: |
|columns||Data from columns beyond |
|separators||The column separator is detected from the header row. Supported separator characters are commas (|
|double-quote character||The double-quote (|
|data rows||After the header row, following rows must use the same column order. The issue title is required, but the description is optional.|
If you have special characters in a field, (such as
,), surround the
characters with double quotes (
Sample CSV data:
title,description My Issue Title,My Issue Description Another Title,"A description, with a comma" "One More Title","One More Description"
The limit depends on how your GitLab instance is hosted:
- Self-managed: Set by the configuration value of
Max Attachment Sizefor the GitLab instance.
- GitLab SaaS: On GitLab.com, it’s set to 10 MB.