View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0003526 | mantisbt | custom fields | public | 2004-01-23 21:28 | 2019-09-26 16:41 |
Reporter | chrisj | Assigned To | dregad | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | duplicate | ||
Platform | i386 | OS | Linux/KDE | OS Version | SuSE/3.1.4 |
Summary | 0003526: Custom field regular expression doesn | ||||
Description | I created a custom field (Library Version) and added the following regular expression to the field: When creating a new bug, entering an invalid value (such as 1.2.3.4) into the field and hitting 'Submit' correctly generates the message "APPLICATION ERROR 0001303 Invalid value for field". However, a bug record is still created with an empty 'Library Version' field. If the user hits the 'Back' button and fixes the problem and resubmits, a second bug record is created, leaving two bug reports for the same bug, one of which has an invalid custom field. | ||||
Steps To Reproduce | Create custom string field with regular expression. | ||||
Tags | No tags attached. | ||||
duplicate of | 0016952 | new | When reporting issue receive error on custom field, but issue is still created |
The problem is that the report bug does the following:
So, if the custom field validation yields an error, then the bug is already added! There are two options:
|
|
How about performing the validations via javascript before even submitting the bug? |
|