Making a bug viewable in two differents projects

[mallers]

My problem is that I don't understand well what "creating clone" actually does by reading the doc.
Moreover, I cannot find a functionality "clone" in Mantis, but only a "duplicate".

What effect on database does "cloning bug" have ? Is it a link, or a copy ?
Does "cloning" correspond to a specific functionality ? Or is it the same as "duplicating" ?
What is the true difference between "cloning" and "duplicating" a bug ?


More generally, I would like to expose my needs, with more details.

I need to distinguish "Products" Mantis projects, for which both users and developpers have access, and "Component" project, for which only developpers have access.

"Component projects" correspond closely to the source (svn) projects.

Mantis users should be able to browse both "Component projects" and "Products projects" in Mantis (list bugs, search for a bug, etc.).

In this way, while analysing a bug reported in a "product", a developper would first analyse in which "Component" the bug originates.

The developper would create a "clone" of the bug in the appropriate "component" project.

Now, we would have two "bugs id" in the database, but, in fact, they relate to the same "observable bug" in the application.

Question :

If someone modifies something (status, comments...) in the original bug (ie the bug that belongs to a "product" project), will these changes be reflected in the cloned bug (ie the bug that belongs to a "component" project)?

If a developer modifies something (status, comments...) in the cloned bug (ie the bug that belongs to a "component" project) , will these changes be reflected in the original (ie the bug that belongs to a "product" project) bug ?


I hope I am clear enough ! ;=)

thank you for answering

Simon