All dates being set to migration date

[danielfernandez]

First of all, thanks a lot for this great utility. It's really saving me a ton of work!

I'm migrating a medium-size bugzilla database. The script is being executed on the following environment:

• Bugzilla version: 4.2.4
• Redmine version: 2.3.2
• Ruby 1.9.3p194
• mySQL 5.5.32
• Linux Mint 15
• Database size (approx 11,000 tickets)

The migration script ends OK and all the tickets look quite alright, except for the timestamp dates (created_on, updated_on, closed_on) which are all set to the moment the migration was executed instead of the original values. This happens for issues, comments (journals) and attachments.

The start_date and due_date, nevertheless, are set to the right values. Maybe this has to do with the fact they are only dates and not complete timestamps?

[ralli]

Hello Daniel,

current versions of redmine seem to update these dates automatically on save. I just have added a patch which should disable these unintended updates (by calling Issue.reset_callbacks :save)

[danielfernandez]

So quick! Tested, works OK. Thanks a lot.