Ticket import

Ticket import

This module lets you import tickets in batch, from an Excel spreadsheet or comma-separated-values (CSV) file. (Excel is preferred if your data contain non-ASCII characters).

The file or worksheet to import should contain:

The fields must be Trac fields. The valid fields for this Trac instance are: ${field} and , . Field names are case-insensitive: 'summary', 'Summary', 'SUMMARY' refer to the same field. The order of the fields does not matter. If you want to import columns that are not Trac fields yet, these fields must have been created as custom fields in Trac (It is easy to create new fields, but must be done by the Trac administrator in the Trac configuration file).

The only required fields are either:

or:

If a field name starts with #, the contents of the field will be treated as references to other tickets, either a list of dependencies or a Work Breakdown System number. (The WBS is identified as the first ticket reference column which has a value containing a period.) This can aid import of projects created in an external project management program. For example:

summary#blockedby#wbs
Design schematic1
Layout board12
Check board22.1
Manufacture prototypes2,32.1
Verify prototypes43

Once imported, this might become:

idsummaryblockedbywbs
3000Design schematic
3001Layout board3000
3003Check board30013001
3004Manufacture prototypes3001,30033001
3005Verify prototypes3004

First, you will be shown a preview of the changes, and then you will be able to execute the import. The first step (uploading and previewing) will not modify the database.

Components, Milestones, etc... found in the spreadsheet will be added to Trac if they do not exist yet. You may want to customize them after that in the Admin section.

If the spreadsheet contains a Comment column, this column will be added as comment to the tickets.


Note: worksheets containing non-data (e.g., charts) are skipped when counting the worksheets.