Closed Bug 930537 Opened 11 years ago Closed 11 years ago

custom field is not mandatory but generates "not allowed to be null" error when saving bug report

Categories

(Bugzilla :: Creating/Changing Bugs, defect)

Product:
Bugzilla
Component:
Creating/Changing Bugs
Version:
4.2.2
Type:
defect
Priority:
Not set
Severity:
major

Tracking

()

Status:
RESOLVED DUPLICATE of bug 919475

People

(Reporter: snavely, Unassigned)

Details

User Agent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Trident/5.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; .NET4.0E; InfoPath.3; Tablet PC 2.0)

Steps to reproduce:

1) Added a bug with the custom field showing and blank for just a subset of products and then saved the bug.
2) Added a bug with the custom field showing but left blank for all products and then saved the bug.
3) Added a bug with the custom field showing but left blank for all products with bugmail off and then saved the bug.  


Actual results:

I received an Oracle DB error saying that the custom fiedl was not allowed to be null.


Expected results:

The bug should've saved with no error since the custom field was not required.
Severity: normal → major
Priority: -- → P1
Priority: P1 → --
Summary: custom field is not mandatory but generates not allowed to be null error on the save of a bug → custom field is not mandatory but generates "not allowed to be null" error when saving bug report
You are using Bugzilla 4.2.2. This bug has been fixed in Bugzilla 4.2.7.
Assignee: general → create-and-change
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Component: Bugzilla-General → Creating/Changing Bugs
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.