New custom fields proposal
bbaetz at acm.org
Fri Apr 11 07:44:52 UTC 2003
On Thu, Apr 10, 2003 at 07:44:39PM -0400, Sean McAfee wrote:
> Can "None" (or a similar word) be a special, reserved selection value? I'm
> thinking ahead to when I might want to programmatically determine whether a
> particular field has been set by a user yet. This won't be easy if each
> selection field gets its own notion of what being "unset" is called.
Well, we can have NULL (in the db side). That would work with the left
join rather well, actually.
> According to my proposal, the user would select projects "a" and "b" at the
> top of the page, press the "Show custom fields" button, and be presented
> with all of the custom fields for projects "a" and "b". At this point the
> situation is the same as your "always show all custom fields in all projects"
> approach, since fields in projects other than "a" and "b" are irrelevant.
Look at how the component/milestone/version stuff is done, depending on
which products you click on. I'm imagining something like that, except
we can just set .disabled, or something.
> custom fields, but group them in per-project <DIV> elements which initially
> have the style "display: none". An event handler attached to the "Project"
> selection element would dynamically toggle the display styles between
> "inline" and "none". Is this reasonable? Is there some minimum level of
> scriptability we should expect from Bugzilla web clients?
You can't _require_ any JS at all. You can start out with them all being
visible, hide then in an onload, and then use js as people click on
More information about the developers