Database changes

[Gervase Markham]

Jordi Bunster wrote:

> I'm planning to introduce some big changes on bugzilla's internal logic 
> and database. Here at my shop, we have much more modularity than just 
> the two level (product, component) approach. What we want to do is, just 
> have bug "targets", which can nest. Each one would have a unique ID, and 
> a parent reference, and you can assign bugs to any of them, not just to 
> the lowest level one.

Have you thought about how the UI would work for this? Have you ever 
seen Bugzilla's "intermediate screen" when you change products? How 
would you avoid that? Remember, we can't depend on JS at the client.

Past discussions have reached the conclusion that:
- A third level is desireable, and if someone implements it, great
- Arbitrary levels above 3 are too much of a UI and config nightmare
   for the relatively small extra benefit you'd get.

> It is also my intention to have a configuration file, where you can 
> specify the way a target is called on the *webpages*, not internally, 
> depending on its nesting depth. For example, level one would be called 
> product, level two component, and three and on sub-component, so as to 
> avoid breakage with existing bugzilla installations.

This sort of naming goes in templates, so it can be localised.

> Knowing that this would make upgrading bugzilla here a nightmare, my 
> question goes: Would the bugzilla team be willing to accept this 
> changes, providing that the code is clean, follows the guidelines, and I 
> add code to checksetup.pl so that it automagically migrates everything?

We certainly wouldn't commit to doing so without a more concrete 
proposal :-)

Gerv