This just came to my head and my sound as prosperous idea ( Fedora features first mantra ) but would solve a common problem that both reporters and upstream maintainers and downstream packagers are faced with a relatively low disruption in operating procedures between upstream and downstream.

As things stands today maintainers need to be part of both upstream and various downstream bugzilla instances to handle bugs which they would prefer to handle directly upstream and at the same time reporters and downstream packagers are faced with the same problem but in their case they need to have several upstream accounts in addition to their downstream one which causes a lot of running around moving back and fourth an general overhead for all parties involved. 

Instead of implementing some huge monster like launchpad and all the noise it brings or trying to unite distribution to use one central bug reporting location
we would instead do the exact opposite we would add the ability to bugzilla to tie together bugzilla instances.

If upstream has bugzilla and downstream has bugzilla as their bug tracker the ability for those bugzilla instances to directly communicate to each other would be added as an example an option could be added to forward the report directly upstream ( from downstream ) when it has reached "Verified" state and the ability for upstream to directly reply downstream ( from upstream ) to request either additional information from downstream or pass information like commit $foo in git fix for downstream maintainers/packagers to pickup and build

Downstream QA or maintainer/packager would handle all the interact with the reporter and after verifying the bug they would simply click upstream which would forward that bug report to the upstream bugzilla instance where upstream maintainers would pick it up and start working in the bug. 

Of course this is just a rough idea but what do you think? 

Undoable of the chart throw to > /dev/null?