Looks like required "fastercsv" is not working, but required "csv" can.
more explicit about why the unique field is needed. Also, made it localized! Yikes.
specifically the way interpolation was done (I don't read Chinese much so this is just asking for trouble). Also added a note about requiring the fastercsv gem, I forgot to put that in the README originally.
…enamed the directory.
While testing that, realized that there was a small bug in the code that tries to auto-match columns against the localized version of the column headings. I fixed that and added a new sample file that demonstrates how localized matching can work. Worse, I realized that a number of the sample files were using the English localized version of the name instead of the international versions -- fixed those. They should all automatch now no matter what language you're running Redmine in.
some more info to README.rdoc.
Added UI and labels for controlling these options. i
…nship of a particular type can be imported in one import run). Optimized the general performance of relationship import by eliminating queries in the simple case. This also makes the uniqueness constraint much weaker for the simple use case where the target issues are higher in the same CSV file. Improved both the English and Japanese strings for the new functions.
Added lots more import samples. Added reference to the documentation in progress. Fixed the interface to correspond to the new features. Did some preparatory work towards supporting importing issue relationships.
If you provide a column that you map to "Parent Task", you can import parent tasks. There are several restrictions: - If you want to import parent tasks, you must set the "Select unique field for identify issue" value in the upload. - Obviously, that field must be unqiue. - Finally, and most importantly, parent tasks must come before child tasks in the list. Although this is kind of a pain, it makes this a one-pass rather than two-pass feature. This has not yet been tested with using the ID as the unique column. Also, right now the "Select unique field for identify issue" option is disabled by default; the second half of this update will update the UI as well.
- If no "Author" field is provided, the author will now be blank (in some cases, it would previously be the user "Anonymous") - If the Assigned To field contains an invalid value (a non-existant user id), it will now be blank (instead of Anonymous)
… or value
…automatically when possible