Bug Report 121 - Custom options field that is mandatory doesn't accept the first option as a valid entry

Bug Id

121

Reporter

Mark Hagers

Product/Version

Bugdar / 1.2.2

Status

Closed

Severity

Moderate

Duplicate Of

- none -

Fixed in Revision

trunk:1620, branch: 1621

Mstone

Summary

Custom options field that is mandatory doesn't accept the first option as a valid entry

Report Time

April 22, 2008 01:22 PM

Assignment

Robert

Resolution

Fixed

Priority

Normal

Dependencies

- none -

Mstone (old)

Attachments

patch-121.diff Patch

Votes

For: 0 (0%)

Against: 0 (0%)

Total: 0

April 22, 2008 01:22 PM Mark Hagers

I have a custom field that is a popup/options menu. The field is mandatory. When I choose the first option in the field, the submission of the bug record is rejected with a message to the effect that the field in question is mandatory. When the bug has been created (with initially another option in the field) I can set it to the first option and update the record successfully.

On April 22, 2008 03:01 PM, Robert changed:

Status from "Unconfirmed" to "Confirmed"

On April 22, 2008 07:36 PM, Robert changed:

Status from "Confirmed" to "Closed"
Resolution from "Open" to "Fixed"
Fixed in Revision from "" to "trunk:1620, branch: 1621"

April 22, 2008 07:36 PM Robert

Thank you for your bug report. This issue has been closed and fixed in Subversion. This change will be available in a future release, but you can download the change at any time from the Subversion server.