Cloning Requirements

• Author: daryn
• Status: Draft | Work in Progress

Development groups have different requirements for how they clone issues and what needs to be cloned. It is possible for different requirements to exist between different groups even in the same company. Currently the Cloning feature of Mantis is limited in it's implementation to basically an easy way to copy some issue data. I would like to expand the cloning of issues to provide greater control for administrators and greater functionality for users.

Currently cloning in Mantis is just re-reporting an existing bug as a new record. However, a limited set of data is copied to the new bug.

…expand to detail what happens in the current approach…

• Give administrators the ability to configure what sections of data get cloned.
• Give administrators a configuration option to allow users to choose which sections to be cloned.
• Add access level threshold so administrators can limit which users can choose sections to be cloned.

• Add ability to change the project and category for a cloned bug

If we have a set of options A, admin can select subset B of A, user can select subset C of A, where C may or may not be restricted to a subset of B …

• Some notes

• Required database changes to mantis_XXX_table

• $g_var indicates something

• Please provide feedback