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.

Data migration strategy

Added by Nicolas Paez at 2012-09-03 06:02 pm

Hi,

I am moving from another bug tracker (c#) to chili and I need to move all the open issues.
I first idea to accomplish this was to use the REST API but it seems it is not complete (I just need create users, projects and issues, nothing else)

What would you recommend?


Replies (2)

RE: Data migration strategy - Added by Felix Schäfer at 2012-09-21 09:33 am

Mmh, if you're fluent enough in ruby you could try exporting the data out of c# in csv/yml/json/xml/… and write a script to import all that into ChiliProject? You can toy with a ruby REPL/shell with the ChiliProject environment loaded with script/console in your ChiliProject folder (this will start a console for the development environment though, see the help of the console for more options), and once you're ready to write a script you can use /path/to/chili/script/runner as your shebang to have the script loaded an run in the ChiliProject environment.

RE: Data migration strategy - Added by Nicolas Paez at 2012-09-21 07:50 pm

Thanks, but I have already solve it. There were just a few records (around 30) so we did a manual migration.

(1-2/2)