The very definition of checkboxes implies the selection of one or many options at once, as opposed to radio buttons, which imply single choice sets. But if you want the user to only select one item, you can just use a list, which is more compact to display anyway.

Thanks for the info, however please let me clarify. My users are confused by lists (I know, it's unbelievable) They need to be able to see the options at once, and I don't care about the wasted real estate. Your response prompted me to see if a radio button is available for custom fields, but it appears that they are not.

Any other suggestions for my custom field to show all options (i.e. not a drop-down list) and allow only one selection?

Thanks!

I can really only think of one solution, and one hack. The better solution wolud be to request that paulr or someone on the team familiar with custom fields implement a radio-button type, and then upgrade your Mantis install to the latest version once that feature is in place.

The "bad" alternative, at the expense of upgradability, would be quicker to implement, and would require you manually editing your Mantis install to have the checkbox custom field output "<input type='radio'..." rather than "type='checkbox'". However, this will be more work for you to maintain when you decide to upgrade your copy of Mantis, as it will be overwritten.

The choice is yours...

Changed summary to reflect what is implemented, which is to add a new custom field type 'radio'. The radio type is an enumeration type that is exposed as radio buttons and hence allowing a single selection.

Fixed in svn:5139
http://mantisbt.svn.sourceforge.net/mantisbt/?rev=5139&view=rev