Bugzilla Integration Status

I have been doing some integration of bugzilla,rt and some other
things for one of my employers (I am a contractor) - its simple right
now, just user info and passwords. However I may be doing some work for
them that involves a deeper integration of the systems (transfering rt
jobs into the bugz db and perhaps back).

I am thinking that if I get this contract I can contribute some to

the Bugzilla integration protion of rt.

The only thing I could find relating to bugzilla was in the

config.pm file (at bottom of message), which implied that only stubs for
integration exist. Wanted to verify that this was true and seek some
advices.

Thanks

Wade Burgett
wadeb@burgettsys.com

{{{ RT Linking Interface

A hash table of convertion subs to be used for transforming RT Link

URIs to URLs in the web interface. If you want to use RT towards

locally installed databases, this is the right place to configure it.

(TODO!)

%URI2HTTP=
(
‘fsck.com-rt’ => sub {warn “stub!”;},
‘mozilla.org-bugzilla’ => sub {warn “stub!”},
‘fsck.com-kb’ => sub {warn “stub!”}
);

A hash table of subs for fetching content from an URI

%ContentFromURI=
(
‘fsck.com-rt’ => sub {warn “stub!”;},
‘mozilla.org-bugzilla’ => sub {warn “stub!”},
‘fsck.com-kb’ => sub {warn “stub!”}
);

If you want to use those, ask at rt-devel or to tobix@fsck.com for

advices.

The only thing I could find relating to bugzilla was in the

config.pm file (at bottom of message), which implied that only stubs for
integration exist. Wanted to verify that this was true and seek some
advices.

This is in RT2. I can tell that we do have some sort of linking locally
between our Bugzilla and our RT2 instance - however, most of this is done
in our Bugzilla, the local Bugzilla administrator has made a separate
table for relating rt-tickets with bugzilla-bugs. I might try to ask him
for some patches if it’s interessting.

I’ll send my config.pm privately to you, you might probably figure out
what’s the bugzilla integration and what isn’t. The FAQ-thing is another
nifty feature our support department can’t live without; whenever they get
a frequently asked question, they just enter a tag for the wanted reply,
and the frequent answer will be inserted right into the message sending
form - unfortunately it’s currently a hack that is only working locally.

Spell checkers are for wimps
(please send feedback on all typos)