Skip to content
GitLab
Next
Menu
Why GitLab
Pricing
Contact Sales
Explore
Why GitLab
Pricing
Contact Sales
Explore
Sign in
Get free trial
Primary navigation
Search or go to…
Project
GitLab FOSS
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Privacy statement
Keyboard shortcuts
?
What's new
4
Snippets
Groups
Projects
Show more breadcrumbs
GitLab.org
GitLab FOSS
Commits
c44a2fdb
Commit
c44a2fdb
authored
5 years ago
by
Noveed Safipour
Browse files
Options
Downloads
Patches
Plain Diff
Clarified order of column headers and recommended test import
parent
cddf9b87
No related branches found
No related tags found
1 merge request
!28449
In CSV Import doc, clarified order of column headers and recommended test import
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/user/project/issues/csv_import.md
+13
-7
13 additions, 7 deletions
doc/user/project/issues/csv_import.md
with
13 additions
and
7 deletions
doc/user/project/issues/csv_import.md
+
13
−
7
View file @
c44a2fdb
# Importing
I
ssues from CSV
# Importing
i
ssues from CSV
> [Introduced](https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/23532) in GitLab 11.7.
Issues can be imported to a project by uploading a CSV file
. Supported fields are
`title`
and
`description`
.
Issues can be imported to a project by uploading a CSV file
with the columns
`title`
and
`description`
, in that order
.
The user uploading the CSV file will be set as the author of the imported issues.
> **Note:** A permission level of `Developer` or higher is required to import issues.
## Prepare for the import
-
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
](
#csv-file-format
)
requirements.
## Import the file
To import issues:
1.
Ensure your CSV file meets the
[
file format
](
#csv-file-format
)
requirements.
1.
Navigate to a project's Issues list page.
1.
If existing issues are present, click the import icon at the top right, next to the
**Edit issues**
button.
1.
For a project without any issues, click the button labeled
**Import CSV**
in the middle of the page.
...
...
@@ -20,11 +26,11 @@ To import issues:
The file is processed in the background and a notification email is sent
to you once the import is completed.
## CSV
F
ile
F
ormat
## CSV
f
ile
f
ormat
### Header row
CSV files must contain a header row
beginning with at least two columns,
`title`
and
`description`
, in that order
.
CSV files must contain a header row
where the first column header is
`title`
and the second is
`description`
.
If additional columns are present, they will be ignored.
### Column separator
...
...
@@ -53,7 +59,7 @@ The limit depends on the configuration value of Max Attachment Size for the GitL
For GitLab.com, it is set to 10 MB.
## Sample
D
ata
## Sample
d
ata
```
csv
title,description
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment