View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0019460 | mantisbt | customization | public | 2015-03-02 11:36 | 2015-03-14 11:24 |
Reporter | david520 | Assigned To | dregad | ||
Priority | low | Severity | trivial | Reproducibility | N/A |
Status | closed | Resolution | won't fix | ||
Product Version | 1.2.19 | ||||
Summary | 0019460: Clone Bug | ||||
Description | Clone bug, number of times you have the option the custom field, for example if the custom field has 4 options that the bug will automatically clone 4 times. It is possible? | ||||
Tags | No tags attached. | ||||
I don't really like the idea of cloning an issue without editing it before submission, I see it as an open door for spamming. What's the rationale / business case ? |
|
It is intended to create a custom field versions for the project "to" this field will have versions (1.0, 2.0, 3.0) When you find a bug in the project this is, automatically clone by higher versions of the bug reported I hope you understand me, thanks |
|
Sorry, but it's not really clear... In any case, we can't implement a "standard" (i.e. alter Mantis Core) behavior based on custom fields. |
|
The idea is to clone the bug, by the number of versions that are in the custom field, it is possible? |
|
Well, technically I would say yes, but as I said before it's not something that we would do because we can't base standard behavior on local customizations that may or may not be present (a custom field in this case). |
|