Re: adding dups reporters to recipients
- From: Luis Villa <louie ximian com>
- To: Elijah P Newren <newren math utah edu>
- Cc: paolo borelli <pborelli katamail com>, bugsquad <gnome-bugsquad gnome org>
- Subject: Re: adding dups reporters to recipients
- Date: 23 Jul 2003 11:34:28 -0400
On Wed, 2003-07-23 at 11:31, Elijah P Newren wrote:
> On Wed, 2003-07-23 at 06:54, paolo borelli wrote:
> > Hi!
> >
> > I was wondering if it would be possible to configure bugzilla so that
> > when a bug A is marked as duplicate of bug B the reporter of bug A could
> > be added to the list of recipents that are mailed when a modification to
> > bug B occurs.
This happens in upstream mozilla. We'll do it whenever the cycles to
upgrade the system happen. :/
Note that this won't /entirely/ solve our problem, because of cc:s from
bug-buddy bugs, which won't get copied over (presumably.)
Luis
> > I think that when someone reports a bug he would be interested in any
> > comments/modification that are added in bugzilla about that bug even if
> > his report has been closed as duplicate.
> > With the current behaviour when a bug is marked as dup the reporter is
> > put out of the loop (unless he manually subscribe to the new bug)
> > preventing not only to see how the bug evolves but also to add useful
> > information/feedback that may not be present in the original bug.
>
> It sounds like a good idea, but there are a number of complications that
> I believe will prevent it from happening:
> 1) The majority of people who submit bugs to bugzilla (around 90-95%
> or so) never follow up on the bugs they submit--we know because we
> often need and ask for extra information, and very few people
> respond to such requests. Thus, making your change would probably
> be an inconvenience or annoyance to most bugzilla users. So, even
> though this would be beneficial to the more helpful bugzilla users
> such as yourself, we don't want to irritate the majority of the
> bugzilla users out there.
> 2) Most people who can make changes to bugzilla are overloaded with
> things to do and they take a long time to even finish the high
> priority stuff.
> 3) We want to upgrade to a newer version of bugzilla. As far
> as I can tell (I'm not one of those that can or has modified
> bugzilla itself), that requires a lot of database manipulation.
> Because of this and also because of reason #2 listed above, this
> has been in the works for a long time. Any changes to bugzilla
> might complicate this and make it take longer.
>
> But, then again, maybe someone else on the bugsquad list will tell me
> that I'm crazy and that the above reasons are irrelevant. If not, I
> hope it's not to difficult for you to load up the bug report(s) in
> bugzilla which your bug(s) have been marked as a duplicate of, read
> them, and then add yourself to the cc list.
>
> Thanks for submitting bugs and feel free to email any other ideas that
> you think of.
>
> Elijah
>
> _______________________________________________
> Gnome-bugsquad mailing list
> Gnome-bugsquad gnome org
> http://mail.gnome.org/mailman/listinfo/gnome-bugsquad
>
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]