View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0009816 | mantisbt | bugtracker | public | 2008-11-14 05:08 | 2009-06-26 12:02 |
| Reporter | jonathh | Assigned To | thraxisp | ||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | closed | Resolution | duplicate | ||
| Platform | x386 | OS | Linux/Windows | ||
| Product Version | 1.2.0a2 | ||||
| Summary | 0009816: Custom fields not enforced. | ||||
| Description | I created a custom field with a type of numeric, but it allows me to enter a string or anything i'd like. Is this a bug? Surely the only reason to ask what the custom type is, is if it is going to be enforced? Also i am requiring this field to be visable only on the 'resolved' screen. It is a fixed @ revision field. As an extra note to this. Even though my custom field is set to 'Required On Resolve ' and 'Display When Resolving Issues ' ONLY If i set a minimum field length of 1 i can not add any new faults. The reason i guess is that the field isn't present on that screen but there is a check that it has a minimum field length anyway which fails. just FYI As i continue my investigation of this fault. I tried a radio button custom field for 'kicks' apart from having some sticky issues with 'security tokens and did i submit it twice' it seems to require a radio button be checked - which is good. But the min and max field length broke it if you populated it. Perhaps these options should be set to null and hidden if you select radio.. Thank you! | ||||
| Steps To Reproduce | Create a custom field of type x, enter a bug with details of type !x | ||||
| Tags | No tags attached. | ||||