We had an issue with our version of mantis being very...very old, and customized. We also will need to migrate close to 100,000 issues.
So we actually wrote a simple php page (just modified the default report page from mantis) that filters the project/dates we are migtrating and generates a JSON payload.
YOu can use the JSON importer found in JIM, or for bonus points just have the php page post the json payload direct to JIRA's rest APIs.
This allows _full_ migration of attachments,watchers, comments, links, history, etc.
// how to setup filter and get initial list of bugs
$filter = filter_get_default();
$filter['_view_type']='advanced';
// Dates
$filter['start_year']=$start_year;
$filter['start_day']=$start_day; // yep, only integer
$filter['start_month']=$start_month;
$filter['end_year']=$end_year;
$filter['end_day']=$end_day; // dido
$filter['end_month']=$end_month;
$filter['do_filter_by_date']='on'; //IMPORTANT - to use dates, do_filter_by_date must = "on"
$filter['search']=$search;
$filter['show_category']=$category;
$filter['show_status']=$status;
$result = filter_get_bug_rows( $t_page_number, $t_per_page, $t_page_count, $t_bug_count, $filter , $projectId);
//$result = filter_get_bug_rows( $t_page_number, $t_per_page, $t_page_count, $t_bug_count );
$row_count = sizeof( $result );
Then just loop through, printing the json payload depending on your target.
You'll need to make some additional queries to the "monitor","bug_notes", and other tables for non-core values, but all the basic plumbing is already there. Just copy and modify to your needs.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.