Closed Bug 574029 Opened 15 years ago Closed 15 years ago

The red star besides the "Component" label in show_bug.cgi has no meaning

Categories

(Bugzilla :: User Interface, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
Bugzilla 4.0

People

(Reporter: LpSolit, Assigned: timello)

Details

(Keywords: regression)

Attachments

(1 file, 3 obsolete files)

It should go away. I don't see what it means. This is confusing.
Indeed. The required field indication for the component is useless since there is no way to unset the component to something invalid.
Assignee: ui → timello
Status: NEW → ASSIGNED
Keywords: regression
Attached patch Small fix. (obsolete) — Splinter Review
So now, we have to use the template parameter 'mandatory' in order to differ enter_bug from show_bug, in that way, we can have such granularity.
Attachment #453433 - Flags: review?(LpSolit)
Comment on attachment 453433 [details] [diff] [review] Small fix. >=== modified file 'template/en/default/bug/field.html.tmpl' >+[% IF !mandatory %] >+ [% mandatory = field.is_mandatory %] >+[% END %] You can never pass mandatory = 0. Also, why haven't the product and version fields the is_mandatory attribute set to true? They are mandatory when calling Bug.create, isn't it?
Attachment #453433 - Flags: review?(LpSolit) → review-
Comment on attachment 453433 [details] [diff] [review] Small fix. The "required" star should never show up on show_bug.cgi for *any* field. We should not be removing is_mandatory from the component field in the database, and we shouldn't be changing the API of field.html.tmpl to fix this.
Attached patch Fix. (obsolete) — Splinter Review
I needed to do the same [% IF NOT bug.id %] in the field-label, because this template is called alone as well.
Attachment #453433 - Attachment is obsolete: true
Attachment #453487 - Flags: review?(LpSolit)
Comment on attachment 453487 [details] [diff] [review] Fix. Cool. Simpler, but we don't need "mandatory" as an option to field.html.tmpl anymore. Also, because of the way TT works, you need an ELSE that sets mandatory = 0.
Attachment #453487 - Flags: review?(LpSolit) → review-
Attached patch v3 (obsolete) — Splinter Review
Attachment #453487 - Attachment is obsolete: true
Attachment #453491 - Flags: review?(mkanat)
Comment on attachment 453491 [details] [diff] [review] v3 >+ # mandatory: a boolean specifying whether or not the field is mandatory. This actually isn't part of the API, is it? >+[% IF NOT bug.id %] >+ [% mandatory = field.is_mandatory %] >+[% END %] If it is part of the API, you're overwriting it here. Also, you need an ELSE that sets mandatory = 0 (because TT has no namespaces).
Attachment #453491 - Flags: review?(mkanat) → review-
Attached patch v4Splinter Review
I think it could be simpler than everything else I did here before.
Attachment #453491 - Attachment is obsolete: true
Attachment #453533 - Flags: review?(mkanat)
Comment on attachment 453533 [details] [diff] [review] v4 Looks great. :-)
Attachment #453533 - Flags: review?(mkanat) → review+
Flags: approval+
Committing to: bzr+ssh://bzr.mozilla.org/bugzilla/trunk/ modified template/en/default/bug/field-label.html.tmpl Committed revision 7244.
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: