-
Notifications
You must be signed in to change notification settings - Fork 173
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
? #1
Open
iwaomaster
wants to merge
41
commits into
angro:master
Choose a base branch
from
leovitch:master
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
? #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…automatically when possible
- 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)
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.
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.
…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 UI and labels for controlling these options. i
Can be turned off with the new checkbox, but it defaults to the normal emails.
some more info to README.rdoc.
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.
Conflicts: README.rdoc
Portuguese Brazilian translation
…enamed the directory.
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.
more explicit about why the unique field is needed. Also, made it localized! Yikes.
Thanks to archonwang for the strings.
…..", i add "RAILS_ENV=production" and it works better
a CSV, and turned "update existing issues" on, and the existing issue had 0 journal entries, and "deliver notification emails" was on, the import would fail with an error.
I will make a more complete comment after merging.
…list should work now. - Greatly imporoved error reporting. All the errors that were ever checked for are now consistently reported through the flash message and the failed rows display. - Implemented all subsidiary User and Version lookups through a cache. This should help the performance of large imports on sites with a large number of users appreciably. Redmine has no index on the login name field for Users so multiple lookups are important to avoid.
TypedCustomFields.csv is the test file for the Redmine 1.2 custom field support. ErroneousStandardFields.csv is the test file for error reporting on standard fields. TypedErroneousCustomFields.csv is the test file for custom fields. Typed*.csv require adding a whole bunch of custom fields to your project. Full documentation will be placed on Wiki. ErroneousStandardFields.csv should be run with "Auto-add Versions" off.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.