User information
 Loading ...
Show article in Knowledge Base

 Importing issues Export knowledge base Export     SubscribeSubscribe      Show article info

You can import issues into VisionProject from a .csv-file, an Excel file,  or a MS Project file exported to an xml-format.

This article mainly deals with importing issues into VisionProject from a .csv-file or Excel file.


(You can read more about importing issues from a MS Project file here: Import from MS Project)


Knowledge Base Images/Issues/Issue import icon.PNGThe import icon is visible in the top right in the issues list page. Click on it to open a dialog window.

In the dialog, you can select which file to import data from. You can import from these file formats: .csv, .xls or .xlsx . 



Knowledge Base Images/Icons/star_yellow.gifImporting from a .csv-file:

Note 1: Make sure that the imported .csv file is encoded with UTF-8, otherwise national characters using diacritics etc may be replaced with something else in the import.


Note 2: Make sure that the imported .csv file use semicolons as column separators, and not tab spacing or similar.


Note 3: If you export the .csv file from another program such as Microsoft Excel, make sure to save the file as plain .csv - as pure text as possible. If you export using Microsoft Excel's own csv-format, there will be a lot of invisible control characters etc, that tends to "break" the .csv-file when importing to VisionProject.  




Knowledge Base Images/Icons/star_yellow.gifImporting from an Excel-file:


The best way to get the correct format for the Excel file to import, is to either use the sample Excel file, or do an export. The import file should have two header rows, one with the normal issue field names, and one with the internal names of the issue fields.


 Knowledge Base Images/Issues/Import from csv dialog.PNG


You can download a sample file by clicking on "Download sample data" in the dialog.

Read more about the sample file and data setup here: The Import file formatting



When you upload the file, the results will be shown in a preview window where you can examine and verify the imported data. In this table, you also get information if an issue cannot be imported for some reason, and in some case also what the problem is.


If the file looks fine, click on "Save" to import the issue data. Hopefully, you'll then get the message that the import succeeded.


Knowledge Base Images/Issues/import issue confirmation table dialog.PNG



What does the different icons in the left column mean? They indicate the status of the individual row for the import.

Note: Hover over the icons to display a list of problems with the row/issue.


Knowledge Base Images/Issues/Import_success_icon.PNG OK - will be imported: this row will be imported as is.



Knowledge Base Images/Icons/star_yellow.gif  Error exists but this row will be imported: This row has one or more errors in it, caused when the system cannot match the value in the import to a valid value for the issue field in question. The text mentions which columns have problems.


What happens during import is that this row will be imported, but the problematic fields will be replaced with default values. Some fields (Status, Priority etc) have explicit default values. Other fields will be set to the first valid value in the list of possible values, or left blank/unassigned if that is a valid choice for the issue field.



Knowledge Base Images/Issues/Import_fail_icon.PNG No import will be made!: This row has such errors in it that this row will not be imported to an issue. Usually some text mentions which fields are problematic.


Note: We do not recommend import of more than 2000 objects at a time since that slows the system down. If more objects needs to be imported divide them into groups of a maximum of 2000 and then add more groups once the first is imported.

User comments
 Loading ...