View Issue Details

IDProjectCategoryView StatusLast Update
0006610mantisbtcustom fieldspublic2010-06-09 03:45
Reporterntbone Assigned Todhx  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionduplicate 
Product Version0.19.4 
Summary0006610: Checkbox custom field and required status
Description

When a check box custom field type is created, and the required on __ is set, I am forced to check the value. This doesn't seem to fit my understanding of a check box.

Additional Information

Suppose I make a custom field "Data Validation" and its a check box. The possible value is "Completed". When I am filling out the report, if I have completed data validation, I check the box next to "Completed" othewise, I leave it unchecked.

I want to make this entry required when resolving a bug. My understanding here is that by making it required when resolving a bug, the resolover will see the check box and either check it to say they completed it, or leave it unchecked to say they haven't. If I make it required though, they have no choice but to check it. Perhaps I am miss understanding how the check box type is supposed to be used.

TagsNo tags attached.

Relationships

duplicate of 0011628 closeddhx Error 0001303 / Custom Field (Checkbox) evaluated as mandantory even when it is not 

Activities

atomoid

atomoid

2006-04-17 23:11

reporter   ~0012565

The feature seems to works as i would expect it to. If it were to not 'require' one of the checkboxes to be filled in, then it wouldnt really work as expected (since who knows whether or not someone had looked at it or not). Therefore. I suggest you add a second checkbox for the "havent checked it yet" status. That might make it easier for your users, and then you'll know that they 'havent checked it yet'. This will also allow you to search by either criteria.