On Mon, 16 Apr 2007, Paul Jakma wrote: > - The ability to link easily to the external bug, ie rather than > having to say "See http://bugzilla.....";, to have a box to enter > the bugid into so that viewers then could be given an easy path to > the external bug (inline viewing of the information or via browser) > > - Ability to have certain key fields of the external bug show up in > our bug DB. Bug resolution state particularly. > > I.e. If I have a bug in our system which is tracking some external > bug, and the external bug changes to closed/fixed - I'd like to > that to show up.
I think the ability to link with other databases is crucial. But I think that part of the current problem is because confidential customer data is part of the "bug info". What Sun (and in the future, other support vendors) needs to do is separate the bug info from the service call. In Sun support parlance of old, put the confidential data into sotool, and all the bug details into the bug system. Over time, I think we need to evolve to one external (to Sun) master bug database which contains just the bug info, which can be "plugged into" by other external programs from multiple sources. That is, we shouldn't just restrict our solution to Sun's confidentiality needs: in the future, it's quite possible that other entities will provide commercial support for OpenSolaris, and they would need the same confidentiality mechanisms as Sun. -- Rich Teer, SCSA, SCNA, SCSECA, OGB member CEO, My Online Home Inventory Voice: +1 (250) 979-1638 URLs: http://www.rite-group.com/rich http://www.myonlinehomeinventory.com
