"Resolved Date" lost in migration to 3.0 database format

Last Friday I migrated our in-house instance to 3.0.  Everything went smoothly, but I have noticed that the "resolved date" on any issues resolved before the migration got set to the time of the migration.  This is unfortunate, because we are doing our project planning based on this data.  This seems like a deficiency in the migration tool.

I still have the pre-migration data, but I do not see an obvious way in the REST APIs to copy just the resolve dates over.  Has anybody else out there solved this problem?

3 comments
Comment actions Permalink

We surely have a bug,  which we should fix. We will try to fix it ASAP and provide you with a bugfix build with this flaw removed.

0
Comment actions Permalink

That is excellent, but is there a way I could load my pre-migration data into an instance of 2.2 and get the resolved dates out, and then update them in the 3.0 instance via the REST API?  The import API seems to be the only way "resolved" can be specified, but I'm not sure this works for updating an existing item.

0
Comment actions Permalink

I don't think it will work for an existing item. We will figure out how to fix databases affected by this problem tomorrow.

0

Please sign in to leave a comment.