Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 608198 - Bugzilla doesn't show the "Package list" and "Runtime testing required" fields for a stable request saved as a template
Summary: Bugzilla doesn't show the "Package list" and "Runtime testing required" field...
Status: CONFIRMED
Alias: None
Product: Gentoo Infrastructure
Classification: Unclassified
Component: Bugzilla (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Bugzilla Admins
URL: https://bugs.gentoo.org/enter_bug.cgi...
Whiteboard:
Keywords:
Depends on:
Blocks: 601304
  Show dependency tree
 
Reported: 2017-02-04 11:02 UTC by Ulrich Müller
Modified: 2017-02-05 10:12 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ulrich Müller gentoo-dev 2017-02-04 11:02:10 UTC
When recalling a stabilization bug saved as a template (see URL for an example), Bugzilla won't show the "Package list" and "Runtime testing required" fields. They appear only after filing the bug.
Comment 1 Michael Palimaka (kensington) gentoo-dev 2017-02-05 08:48:44 UTC
This appears to be an issue with Bugzilla. Conditional display of custom fields on product works, but not by component.
Comment 2 Michał Górny archtester Gentoo Infrastructure gentoo-dev Security 2017-02-05 09:53:53 UTC
EUPSTREAM, I'm afraid. I suppose some ECMAScript needs to be fired when data is supplied via GET.
Comment 3 Michael Palimaka (kensington) gentoo-dev 2017-02-05 10:12:59 UTC
(In reply to Michał Górny from comment #2)
> EUPSTREAM, I'm afraid. I suppose some ECMAScript needs to be fired when data
> is supplied via GET.

Just so I don't forget, I looked into this a bit and it turns out all fields are present in the generated HTML and display is controlled with class="bz_hidden_field". Bugzilla is supposed to evaluate the context when deciding whether to use this class in the initial HTML but this does not happen with component (but works fine for product). I suspect this is due to some internal naming differences (product vs. component_) but I don't know enough about the internals to be sure.

Client-side scripting is indeed used to change field state when changes are made after the page has loaded, but it only listens for change events which is of course useless for bug templates. We could probably "fix" it by also firing on a page load event, but this is unlikely to be accepted upstream and I doubt we want to hack our templates.