Context sensitive custom fields

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Context sensitive custom fields

Jochen Wiedmann
Hi,

I am currently preparing a customization project for a customer with a
relatively large number of products and components. The products in
question aren't software, but hardware. In particular, they have very
different requirements in terms of custom fields. Therefore, the
customer wants some context sensitivity. Context would be defined as
the bugs product and component:

- Custom fields should be enabled or disabled automatically.
- Validation of custom fields (mandatory yes/no) should honour the context.
- Drop down values must be context sensitive.

I would like to ask whether there is some interest in such features
here. If so, I'd add some private time to enhance the likelihood of
acceptance into the Bugzilla code base. Otherwise, I'd obviously do
some hacking, in order to make it short. (For example, I'd use
Data::Dumper to store the meta data, rather than the database.)

Thanks,

Jochen

--
Look, that's why there's rules, understand? So that you think before
you break 'em.

 -- (Terry Pratchett, Thief of Time)
-
To view or change your list settings, click here:
<http://bugzilla.org/cgi-bin/mj_wwwusr?user=lists@...>
Reply | Threaded
Open this post in threaded view
|

Re: Context sensitive custom fields

Steve Wendt
On 8/4/2008 11:50 PM, Jochen Wiedmann wrote:

> I would like to ask whether there is some interest in such features
> here. If so, I'd add some private time to enhance the likelihood of
> acceptance into the Bugzilla code base. Otherwise, I'd obviously do
> some hacking, in order to make it short.

There's certainly interest - I think the tricky part is designing it in
a broadly applicable way, that meets the approval of the core
developers.  You might want to do the quick and dirty solution to make
your customer happy, and that will probably give you some ideas about
how to design a long term solution.
_______________________________________________
dev-apps-bugzilla mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-apps-bugzilla
-
To view or change your list settings, click here:
<http://bugzilla.org/cgi-bin/mj_wwwusr?user=lists@...>
Reply | Threaded
Open this post in threaded view
|

Re: Context sensitive custom fields

Guy Pyrzak
Max and I have done a lot of work along these lines for NASA, the term "context" isn't very clear so let me know what you specifically mean and we'd (being the nasa folks) be happy to supply code and work with you to get it back into the code base.

-Guy

On Tue, Aug 5, 2008 at 10:45 AM, Steve Wendt <[hidden email]> wrote:
On 8/4/2008 11:50 PM, Jochen Wiedmann wrote:

> I would like to ask whether there is some interest in such features
> here. If so, I'd add some private time to enhance the likelihood of
> acceptance into the Bugzilla code base. Otherwise, I'd obviously do
> some hacking, in order to make it short.

There's certainly interest - I think the tricky part is designing it in
a broadly applicable way, that meets the approval of the core
developers.  You might want to do the quick and dirty solution to make
your customer happy, and that will probably give you some ideas about
how to design a long term solution.
_______________________________________________
dev-apps-bugzilla mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-apps-bugzilla
-
To view or change your list settings, click here:
<http://bugzilla.org/cgi-bin/mj_wwwusr?user=guy.pyrzak@...>

Reply | Threaded
Open this post in threaded view
|

Re: Context sensitive custom fields

Max Kanat-Alexander
In reply to this post by Jochen Wiedmann
On Tue, 5 Aug 2008 08:50:31 +0200 "Jochen Wiedmann"
<[hidden email]> wrote:
> I am currently preparing a customization project for a customer with a
> relatively large number of products and components. The products in
> question aren't software, but hardware. In particular, they have very
> different requirements in terms of custom fields. Therefore, the
> customer wants some context sensitivity. Context would be defined as
> the bugs product and component:

        That's these bugs:

        Restrict custom fields to product/component:
        https://bugzilla.mozilla.org/show_bug.cgi?id=371995

        Which in turn should be implemented as a special case of this:
        https://bugzilla.mozilla.org/show_bug.cgi?id=291433

        Fields whose list of values depends on other fields:
        https://bugzilla.mozilla.org/show_bug.cgi?id=308253

        I already have code for that in NASA's Bugzilla, called PRACA,
for which I have full permission to contribute back to Bugzilla. The
most modern branch of PRACA is here:

        http://bzr.everythingsolved.com/nasa/praca4

        That has a LOT of extra customizations, of course, so you'd
have to pick the code out of there.

        The first thing that needs to be done is to extract the
Bugzilla::Field::Choice object from that code and bring it upstream.

        -Max
--
http://www.everythingsolved.com/
Competent, Friendly Bugzilla and Perl Services. Everything Else, too.
-
To view or change your list settings, click here:
<http://bugzilla.org/cgi-bin/mj_wwwusr?user=lists@...>