View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0016952||mantisbt||custom fields||public||2014-02-11 10:27||2019-09-17 08:15|
|Summary||0016952: When reporting issue receive error on custom field, but issue is still created|
I was doing a sample upgrade and the system did not like our checkbox configuration. When I reported an issue the red error appeared, "Invalid value for custom field xxxxx". I just assumed the creation of the issue failed.
So I guess there are two issues here:
|Tags||No tags attached.|
|related to||0003759||confirmed||Duplicate bug is created when resubmitting after file upload failure|
|has duplicate||0003526||closed||dregad||Custom field regular expression doesn|
|has duplicate||0016954||closed||dregad||Date type custom field with a default value set might result in application error on a new bug adding|
Please provide detailed, step-by-step instructions to reproduce the issue, including the exact custom field definition (before and after you changed it), also indicate if you have customized Mantis in any way and if so, how.
Note on the Checkbox custom field:
OK, in 1.1.7 the field was defined as show in the attached "before_chk*png" file. I upgraded to mantis 1.2.15, so the field was actually the same. That was when the errors occurred as I mentioned, but the issue was created anyway. I didn't see anything in the documentation that explained changes to checkboxes.
I only got it to work with the radio buttons, which is the file "after*png".
In thinking about this - radio buttons actually make more sense because you may only select "yes" or "no", and not both at the same time. I did not originally set this up but it always worked. Maybe it shouldn't have.
With 1.1.7 the behavior of this field was as follows: if you check the box, "yes" is selected, otherwise unchecked box, sets it to "no".
My issue really is whether or not there is a bug with the upgrade. Theoretically as I mentioned, if you want only one individual selection, radio buttons are better anyway.
Note on the fact that the issue was added when an error occurred:
My other issue which maybe should be separate from this one, is that although I got an error on a custom field definition, the issue was added/created/reported anyway.
Issue creation despite error sounds like the same issue as 0003759
|2014-02-11 10:27||info4km||New Issue|
|2014-02-11 10:27||info4km||File Added: mantiserror.png|
|2014-02-11 11:51||dregad||Note Added: 0039373|
|2014-02-11 11:51||dregad||Status||new => feedback|
|2014-02-11 15:45||info4km||File Added: before_chkbox-1_1_7.png|
|2014-02-11 15:46||info4km||File Added: after_radiobutton-1_2_15.png|
|2014-02-11 15:54||info4km||Note Added: 0039377|
|2014-02-11 15:54||info4km||Status||feedback => new|
|2014-02-11 15:56||info4km||Note Added: 0039378|
|2014-02-12 03:22||dregad||Note Added: 0039380|
|2014-02-12 03:22||dregad||Relationship added||related to 0003759|
|2017-08-19 21:40||cproensa||Relationship added||has duplicate 0003526|
|2019-09-17 08:15||dregad||Relationship added||has duplicate 0016954|