search

enGits / engrid

ENGRID is a mesh generation software with CFD applications in mind. It supports automatic prismatic boundary layer grids for Navier-Stokes simulations and has a Qt based GUI.
Other
146 stars 55 forks source link

Move all issues from the old bug tracker to Github #22

Closed wyldckat closed 12 years ago

wyldckat commented 12 years ago

Old bug tracker: http://sourceforge.net/apps/mantisbt/engrid/my_view_page.php

wyldckat commented 12 years ago

Summary: Ended up moving issues manually. It was faster to do manually, than having to code and test HTML to Github via API in Ruby. Also created Gist repositories with the attachments (one gist per issue) that weren't marked private. Original reporters could not be preserved, which was an additional reason to move on to manual copy-paste-edit.

Details - How I moved manually:

  1. Logged in to Mantis and exported at MantisBT: http://sourceforge.net/apps/mantisbt/engrid/print_all_bug_page.php
  2. But exported to full HTML, not ASCII only: http://sourceforge.net/apps/mantisbt/engrid/print_all_bug_page_word.php?search=&sort=last_updated&dir=ASC&type_page=html&export=-1&show_flag=0
  3. Then used Firebug on Firefox to inspect each report table, turned on Edit on that table and copy-pasted to a new report. Also removed the first two rows, since they had no vital information.
  4. As for Notes, is was a bit trickier, because the main table had embedded other tables. Had to use Confluence to interpret the tables back to a simpler table, copy-pasting from rendered HTML to the Rich Text editor. Then in wiki mode I did some adjustments; then hit preview and copied the new table via inspect with Firebug.
  5. Added attachments later on, by creating Gist repositories, one per issue that had attachments... except for private issues.

Attached is the research I made about moving the issues automatically: https://gist.github.com/3072070