Export Issue Fields in the right order / Import all Issue CSV Fields if Export comes from GitLab

Problem to solve

When using GitLab's export functionality a CSV file is generated whose header looks as follows:

Issue ID,URL,Title,State,Description,Author,Author Username,Assignee,Assignee Username,Confidential,Locked,Due Date,Created At (UTC),Updated At (UTC),Closed At (UTC),Milestone,Weight,Labels,Time Estimate,Time Spent

However, upon directly importing one such file, only the first and second columns are considered and their meaning is hard-coded (Title, Description). Therefore, the first and second columns of a GitLab export (Issue ID and URL respectively) are taken to mean (Title and Description) when imported. This leads to bogus imports such as the one depicted below:

Although said behavior is somewhat expected as per https://docs.gitlab.com/ee/user/project/issues/csv_import.html, it is neither intuitive nor obvious from the import dialog shown below. I'd also argue that it isn't, strictly speaking, correct.

https://files.slack.com/files-pri/T02592416-FPPLRGPEU/image.png

Minimal Fix

GitLab issue exports should be fixed so that the first and second columns are title and description, not issue ID and URL.

This would allow the issues to be imported, even if only those two fields are taken into account.

Ideal Fix

In addition to the minimal Fix, add a check box similar to the one shown below to the import dialog

Export comes from GitLab ( besides title and description, all other fields exported by GitLab will be imported )

Intended users

Personas are described at https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/ -->

Links / references

cc @smcgivern