ChiliProject is not maintained anymore. Please be advised that there will be no more updates.

We do not recommend that you setup new ChiliProject instances and we urge all existing users to migrate their data to a maintained system, e.g. Redmine. We will provide a migration script later. In the meantime, you can use the instructions by Christian Daehn.

Import issues from csv - Done ratio not updated

Added by Rolando Valdivia at 2012-06-18 05:15 pm

Hi,

I'm migrating data from another system, I have everything in csv files adequate for ChiliProject.

I can import to to chili database and the data is displayed properly and I can edit it without problems.

The only problem I have is when I add subtasks to an issue, the parent issue done ratio is not updated.

If I create the issue from ChiliProject and add subtasks the done ratio is updated without problem.

I've been reviewing the db to see if there's some additional data in other tables related to the calculations, but I can't find anything.

Any tips on this?

Thanks,
Rolando


Replies (3)

RE: Import issues from csv - Done ratio not updated - Added by Rolando Valdivia at 2012-06-18 08:39 pm

I'm using MySql and I use this command to import from csv:

LOAD DATA LOCAL INFILE "$(PathToCSVFile.csv)" INTO TABLE chiliproject.issues FIELDS TERMINATED BY "," ENCLOSED BY '"' LINES TERMINATED BY "\r\n";

RE: Import issues from csv - Done ratio not updated - Added by Felix Schäfer at 2012-07-10 12:41 pm

Sorry for the late response :-(

The calculation of the done ratio for parent issues is done in ChiliProject at issue update time, so if you're writing directly to the database, you'll have to update those yourself too (and every other attribute that might be related to the ones you're updating…). You'll notice you probably don't have the journals (in the activity view) for updates you do via this method.

The "better" way to do this would be to update the issues in ruby (via the script/runner script which gives you a "ChiliProject environment in a ruby script", i.e. you can then program something like issue = Issue.find(123); issue.some_attribute = "new_value"; issue.save which should trigger everything "else" ChiliProject does around the update) or via the web API (which I realize might not be complete enough for your use-case, do tell us if that's the case).

(1-3/3)