Commit 3e7aee0e authored by Mike Jang's avatar Mike Jang

Merge branch 'shemgyll-csv-import' into 'master'

CSV Import for issues documentation: Add clarification that two columns are imported

See merge request gitlab-org/gitlab!53251
parents d4accaf6 deb98222
--- ---
stage: none stage: Manage
group: unassigned group: Import
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
--- ---
...@@ -9,7 +9,8 @@ info: To determine the technical writer assigned to the Stage/Group associated w ...@@ -9,7 +9,8 @@ info: To determine the technical writer assigned to the Stage/Group associated w
> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/23532) in GitLab 11.7. > [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/23532) in GitLab 11.7.
Issues can be imported to a project by uploading a CSV file with the columns Issues can be imported to a project by uploading a CSV file with the columns
`title` and `description`. `title` and `description`. Other columns are **not** imported. If you want to
retain columns such as labels and milestones, consider the [Move Issue feature](managing_issues.md#moving-issues).
The user uploading the CSV file is set as the author of the imported issues. The user uploading the CSV file is set as the author of the imported issues.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment