HowTo import issues » History » Version 5
Pablo Estiga, 2017-02-01 20:25
| 1 | 1 | Moritz Who Cares | h1. HowTo import issues |
|---|---|---|---|
| 2 | |||
| 3 | 2 | Moritz Who Cares | "Since 3.2.0":http://www.redmine.org/news/104 Redmine can import issues. |
| 4 | 1 | Moritz Who Cares | In the issues tab there is a import link on the right. You can import any csv-type file. The first line must contain the column names. You can freely assign them to the different fields of an issue. |
| 5 | |||
| 6 | h2. Notes on different Fields |
||
| 7 | |||
| 8 | h3. Parent Issue |
||
| 9 | 3 | Moritz Who Cares | |
| 10 | 4 | Morty Morty | If the field starts with an #, the issue with that id is referenced. If the field contains a number it references the index of the issue in the import. Note that it's not the line number as line 1 contains the header. |
| 11 | 1 | Moritz Who Cares | |
| 12 | h3. Assignee |
||
| 13 | 3 | Moritz Who Cares | |
| 14 | 5 | Pablo Estiga | This must be the username. (Name and lastname works, tested on redmine 3.3) |
| 15 | |||
| 16 | h3. Category and Target version |
||
| 17 | |||
| 18 | During test with 3.3, the assistant allowed me to use an option to automatically create version or category. |
||
| 19 | |||
| 20 | h3. Project |
||
| 21 | |||
| 22 | The assistant will let you choose on which project you want to import the issue. |
||
| 23 | |||
| 24 | h2. Assistant |
||
| 25 | |||
| 26 | The assistant will help you (tested on 3.3): |
||
| 27 | |||
| 28 | # Will ask for options with the file: |
||
| 29 | *Field separator* |
||
| 30 | *Field wrapper* |
||
| 31 | *Enconding* |
||
| 32 | *Date Format* |
||
| 33 | !example_import_options1.jpg! |
||
| 34 | # Then next step will ask for the fields to match |
||
| 35 | This is very interesting, because no matter what the names of the columns are, here you map which column is which field on the issue. |
||
| 36 | !example_import_csv.jpg! |
||
| 37 | |||
| 38 | Attached attachment:"issues.csv" has the csv used during test with 3.3. |