Changes between Version 57 and Version 58 of TicketImportPlugin

Timestamp:

Mar 26, 2017, 1:17:29 PM (7 years ago)

Author:

figaro

Comment:

Moved example to functional description

TicketImportPlugin

@@ -14 +14 @@
 
 References to other tickets, such as the ones used in MasterTicketsPlugin, should be handled correctly, at least for the initial import.
+
+Once you have enabled the plugin and given yourself the `IMPORT_EXECUTE` permission, you will see a new '''Import''' tab in the main navigation. This tab contains a complete documentation on exactly how the import works, as well as a form to select the CSV or XLS file to upload:
+
+[[Image(import-wizard.png, width=80%, border=2)]]
+
+Once you have uploaded it, a preview screen shows what you will be importing and lets you confirm the import.
+
+To import tickets with history, they have to be imported in multiple go's. The first csv file should contain all tickets in new state. The second csv file the tickets in the next chosen states (can be any state known by the implemented ticket life cycle). Updates can include changes to the description, ownership and other fields.
+
+Basically, the second and next csv file imports update the tickets imported from the first. 
 
 It is used by software products development teams daily on several projects in at least three companies.
@@ -38 +48 @@
 
 You can check out TicketImportPlugin from [/svn/ticketimportplugin here] using Subversion, or [source:ticketimportplugin browse the source] with Trac. 
-
-== Japanese localization
 
 A Japanese localization has been done, you can access it at http://sourceforge.jp/projects/shibuya-trac/wiki/plugins%2FTicketImportPlugin, although it may not be the latest version.
@@ -107 +115 @@
 The format is the Python [http://docs.python.org/library/time.html#time.strftime fstrtime].
 
-== Example
-
-Once you have enabled the plugin and given yourself the `IMPORT_EXECUTE` permission, you will see a new '''Import''' tab in the main navigation. This tab contains a complete documentation on exactly how the import works, as well as a form to select the CSV or XLS file to upload:
-
-[[Image(import-wizard.png,width=300)]]
-
-Once you have uploaded it, a preview screen shows what you will be importing and lets you confirm the import.
-
-=== Importing tickets including history
-
-To import tickets with history, they have to be imported in multiple go's. The first csv file should contain all tickets in new state. The second csv file the tickets in the next chosen states (can be any state known by the implemented ticket life cycle). Updates can include changes to the description, ownership and other fields.
-
-Basically, the second and next csv file imports update the tickets imported from the first. 
-
 == Recent changes