Introduced in GitLab 11.7.
Issues can be imported to a project by uploading a CSV file with the columns
description, in that order.
The user uploading the CSV file will be set as the author of the imported 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:
- Navigate to a project’s Issues list page.
- If existing issues are present, click the import icon at the top right, next to the Edit issues button.
- For a project without any issues, click the button labeled Import CSV in the middle of the page.
- Select the file and click the Import issues button.
The file is processed in the background and a notification email is sent to you once the import is complete.
When importing issues from a CSV file, it must be formatted in a certain way:
- header row: CSV files must contain a header row where the first column header
titleand the second is
description. If additional columns are present, they will be ignored.
- separators: The column separator is automatically detected from the header row.
Supported separator characters are: commas (
,), semicolons (
;), and tabs (
\t). The row separator can be either
- double-quote character: The double-quote (
") character is used to quote fields, enabling the use of the column separator within a field (see the third line in the sample CSV data below). To insert a double-quote (
") within a quoted field, use two double-quote characters in succession, i.e.
- data rows: After the header row, succeeding rows must follow the same column order. The issue title is required while the description is optional.
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 the configuration value of Max Attachment Size for the GitLab instance.
For GitLab.com, it is set to 10 MB.