mantisbt:cloning_requirements
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
mantisbt:cloning_requirements [2008/03/03 17:11] – created daryn | mantisbt:cloning_requirements [2008/10/29 04:25] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== | + | ====== |
* **Author**: daryn | * **Author**: daryn | ||
Line 5: | Line 5: | ||
===== Introduction ===== | ===== Introduction ===== | ||
- | Introduction | + | Development groups have different requirements for how they clone issues and what needs to be cloned. |
+ | |||
+ | ==== Current Approach ==== | ||
+ | Currently cloning in Mantis is just re-reporting an existing bug as a new record. | ||
+ | |||
+ | ...expand to detail what happens in the current approach... | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | ==== Proposed 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 | ||
+ | ... | ||
===== Implementation Notes ===== | ===== Implementation Notes ===== |
mantisbt/cloning_requirements.1204582272.txt.gz · Last modified: 2008/10/29 04:31 (external edit)