I'm not sure that there's a "good" option for this.  There's no mechanism for going back and updating existing imported data; the best you could do is to either delete the data back far enough (or the entire imported repo), and rerun the import-latest option to regenerate a bunch of new data, but the problem with that is that it will want to update existing linked issues, and will likely cause a lot of noise via email/history entries.  The only other "good" option would be to write a repair action that will go through the repo history one-by-one and compare imported data against what it "should" be, but I think that would just be yet another potential for inconsistency, not to mention being a fairly large amount of coding effort.  Perhaps a one-off script to find and fix bad entries in our own database would be more prudent, and maybe contribute it to the source integration plugin for anyone else who may have come across a similar issue.

John Reese

On Fri, Feb 22, 2013 at 9:53 AM, Damien Regad <damien.regad@merckgroup.com> wrote:
Hi John,

I pushed a commit today [1] fixing an issue on Github source control plugin (and
possibly affecting other VCS too, did not check).

Basically, the issue was that when a commit was authored by a given user and
committed by another, the plugin would store in the changeset both the author
and committer as the author. Refer to the Github issue [2] for full details.

Due to this bug, we now have a number of changesets in the database on
mantisbt.org/bugs, which do not reflect the reality of the repository (not sure
exactly how many).

Would you have any advice on how to best go about fixing the data on the server
(i.e. basically updating mantis_plugin_Source_changeset_table.committer_id) ?

Thanks in advance

[1] https://github.com/mantisbt-plugins/source-integration/commit/602cc40b
[2] https://github.com/mantisbt-plugins/source-integration/issues/29

Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
mantisbt-dev mailing list