Bug 679898

Summary: RFE add the option to forward to an upstream bugzilla instance.
Product: [Community] Bugzilla Reporter: Jóhann B. Guðmundsson <johannbg>
Component: Bug Import/Export/MovingAssignee: Simon Green <sgreen>
Status: CLOSED DUPLICATE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: develCC: bruno, ebaak, johannbg
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-09-12 00:50:21 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Jóhann B. Guðmundsson 2011-02-23 19:58:35 UTC 
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?
Comment 1 Jóhann B. Guðmundsson 2011-02-23 21:06:47 UTC 
Just wanted to add that a solution like this is most likely the only one that can reach distro wide acceptance since it allows the distrobution to keep their own independence and act as and upstream/downstream. ...
Comment 2 Jóhann B. Guðmundsson 2011-02-23 21:07:58 UTC 
To clarify a bit what I meant each bugzilla instance effectively becomes upstream/downstream..
Comment 3 Jeff Fearn 🐞 2012-05-30 04:39:08 UTC 
As part of the recent Bugzilla 2.4 upgrade the Bugzilla team are cleaning up bugs opened against old versions of Bugzilla. This bug has been flagged as an old bug and will be CLOSED WONTFIX in 7 days time.

If you believe this bug is an issue in the latest Bugzilla version please comment on this bug within 7 days. Doing so will ensure this bug is not closed automatically.

Thanks, the Bugzilla team.
Comment 4 Jóhann B. Guðmundsson 2012-05-30 06:07:14 UTC 
As far as I know this is still an issue with the latest bugzilla unless you know something that I dont.
Comment 5 Jeff Fearn 🐞 2012-07-19 04:45:12 UTC 
Resetting this to defaults for PM consideration.
Comment 6 Simon Green 2012-09-12 00:50:21 UTC 

*** This bug has been marked as a duplicate of bug 652666 ***