From 3cefbefe84dca3ae78449aefc80c1b90eaf22395 Mon Sep 17 00:00:00 2001 From: Max Kanat-Alexander Date: Wed, 27 Oct 2010 00:52:20 -0700 Subject: Bug 602458: Add is_mandatory to Bug.fields output. r=timello, a=mkanat --- Bugzilla/WebService/Bug.pm | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/Bugzilla/WebService/Bug.pm b/Bugzilla/WebService/Bug.pm index 372f0725f..a36eed957 100644 --- a/Bugzilla/WebService/Bug.pm +++ b/Bugzilla/WebService/Bug.pm @@ -134,6 +134,7 @@ sub fields { is_custom => $self->type('boolean', $field->custom), name => $self->type('string', $field->name), display_name => $self->type('string', $field->description), + is_mandatory => $self->type('boolean', $field->is_mandatory), is_on_bug_entry => $self->type('boolean', $field->enter_bug), visibility_field => $self->type('string', $visibility_field), visibility_values => @@ -1045,6 +1046,12 @@ across all Bugzilla installations. C The name of the field, as it is shown in the user interface. +=item C + +C True if the field must have a value when filing new bugs. +Also, mandatory fields cannot have their value cleared when updating +bugs. + =item C C For custom fields, this is true if the field is shown when you @@ -1150,6 +1157,8 @@ You specified an invalid field name or id. =item Added in Bugzilla B<3.6>. +=item The C return value was added in Bugzilla B<4.0>. + =back =back -- cgit v1.2.3-24-g4f1b