Simon,
Below is an addition to my original reply.
Please keep in mind that I have been using Mantis just for a little
while and we went live a couple of months ago. I am not an expert and
this is my approach to a similar (kin of) problem.
I hope someone else will join this conversation with a better solution.
Regards,
Gabriel
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 ?
Creating a clone will result in a new issue/bug with a RELATIONSHIP to
the initial issue/bug.
This RELATIONSHIP can be parent-child , related , etc. By having a
relationship this two bugs/issue will always be "together". If
parent-child relationship then the parent issue cannot be closed until
the child issue is closed. This rule can be useful in certain situations.
Any changes on the parent or child issues will be visible from either
one with the condition (this is the catch) that the respective Mantis
User has at least VIEW access to both projects (if parent child are in
two different projects). This is the downside of this solution.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
mantisbt-help mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mantisbt-help
