719725 - Bugzilla should be able to inform users about changes in a remote bugzilla

Status: NEW

(Bugzilla :: Bugzilla-General, enhancement)

Description

[Matěj Cepl]

Filing the bug per bug 123130 comment 20:

As I have described in XXX I would love a Linux distribution bugzilla (for example) to support this scenario:

1) You as a reporter file a bug in a distribution bugzilla and that would 
   be mostly end of the story for you (barring some NEEDINFOs) --    
   then you should just sit, relax and watch programmers to fix 
   the bug.
2) Bug triager and/or developer finds out that this is not a bug 
   in the distro packaging, configuration, etc., and in the same 
   time it is not time-sensitive, security, super-important bug, 
   so that it should be fixed upstream.
   She clicks the button "UPSTREAM" and that is for some time the 
   end of the story for her (unless, which is quite often the 
   case, she is also working at upstream, so she can deal with the 
   bug there).
3) Our bugzilla collects all information from the bug itself, and 
   from other sources (fixing backtraces with our debuginfos, 
   providing versions of the packages in question, default 
   configuration, etc.) and files (via XML-RPC or something like 
   that) a bug in the upstream database.
4) Upstream bug triagers/developers check that the bug is not 
   duplicate, and do other necessary diaper-changing for the new 
   bug.
   Upstream developers when working on the resolving the issue, 
   could file a NEEDINFO, which would be automagically sent to 
   our bugzilla, and from that to you as a NEEDINFO from our 
   bugzilla. Your reply would go other way around, of course. You 
   are not logged in to the upstream bugzilla, nor you have an 
   account there.
   On every step (or every comment?) the upstream bugzilla sends 
   some information to our bugzilla, so we (you as a reporter and 
   our developers) can follow the progress of the bug.
5) Finally, when the bug is closed upstream, our package 
   maintainer (or all package maintainers of distributions 
   collaboratin with that particular upstream?) get a message 
   (through our bugzilla of course, so that it is logged) that 
   the issue was resolved and she should make an updated package 
   for our distro.
6) When it is done, our bug closes (with possible QA, Errata 
   process, etc. as usual).

Unfortunately, so far this is just a pipedream and from point 2) 
to 5) it doesn't exist at all.

Comment 1

[Matěj Cepl]

Actually, sed -e 's!XXX!article.gmane.org/gmane.linux.redhat.fedora.devel/79936/!'

Comment 2

[Matěj Cepl]

(In reply to Matěj Cepl from comment #1)

Actually, sed -e
's!XXX!article.gmane.org/gmane.linux.redhat.fedora.devel/79936/!'

One more change of unstable email lists archives: https://lists.fedoraproject.org/archives/list/[e-mail]/message/BEXBNJSNPZ7CQPPEFQUHV3J4G4O4D7BK/