I use the roadmap feature for my projects, and I have found that I must create the same version in each component or sub project to get them to report in the roadmap of the parent project.

Also I implemented the following patch, to have the sub project issues show up in the parent projects roadmap.
69,75d68
< $sub_project_ids = user_get_all_accessible_subprojects( $tuser id, $t_project_id );
< array_unshift( $sub_project_ids, $t_project_id );
< $projects = '('. $t_project_id;
< foreach( $sub_project_ids as $s_project_id ) {
< $projects = $projects . ',' . $s_project_id ;
< }
< $projects = $projects . ')';
105c98
< $query = "SELECT * FROM $t_bug_table WHERE project_id in $projects AND target_version='$c_version' ORDER BY status ASC, last_updated DES C";

                  $query = "SELECT * FROM $t_bug_table WHERE project_id='$                                                                             c_project_id' AND target_version='$c_version' ORDER BY status ASC, last_updated                                                                              DESC";

218c211
< ?>

?>

It's not perfect, I would like to see the roadmap in a "Tree" view, but for now this has been working for me.

Yes,our company met the same problem,it's important and very useful.Can anybody do a fix?

What is the status on this. I am using mantisbt 1.2? Has anyone made a fix so the road maps will be organized by version number?

Does anybody use plofote's fix or any other fix to resolve it?

Yes, We need it, too.

This is very importand for us and is the most importand drawback for using the mantis versions.

As a workaround we are working with user defined version strings which are entered in custom fields and a special script to generate a changelog.

To model milestones we are creating special milestone issues and add a bug relationship to the issues which have to be solved in the milestones.

This procedure is very slow because it causes a lot of relationships and a lot of email traffic when changing one issue.