Bug 134828 - blank change notification for bug B sent when bug A, depending on B, changes; or, when tracker state closes, dependencies get empty bugspam
Summary: blank change notification for bug B sent when bug A, depending on B, changes;...
Alias: None
Product: Bugzilla
Classification: Community
Component: Bugzilla General
Version: 3.2
Hardware: All
OS: Linux
medium vote
Target Milestone: ---
Assignee: PnT DevOps Devs
QA Contact: David Lawrence
Depends On:
TreeView+ depends on / blocked
Reported: 2004-10-06 15:42 UTC by Daniel Reed
Modified: 2013-06-24 02:58 UTC (History)
0 users

Clone Of:
Last Closed: 2008-12-01 19:46:47 UTC

Attachments (Terms of Use)

Description Daniel Reed 2004-10-06 15:42:10 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20040929

Description of problem:
In a dependency tree where bug A blocks on bug B (and bug C, bug D,
etc.), such as:

 `+- B
  +- C
  `- D

If C is removed from the dependency tree, bugspam is sent to people
watching bug A notifying them of the change. This is is correct.

However, if C is removed from the dependency tree under A, bugspam is
*also* sent to people watching bugs B and D with nothing in the
"changed" section.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
I was able to reproduce this by removing bugs 131461 and 131466 from
131451's dependencies at the same time as I closed 131451 RAWHIDE. I
am not sure which change causes the empty bugspam to be sent to me for
each of 131451's continuing dependencies.

Additional info:

Comment 1 David Lawrence 2006-04-08 17:54:11 UTC
Red Hat's current Bugzilla version is 2.18. I am moving all older open bugs to
this version. Any bugs against the older versions will need to be verified that
they are still bugs. This will help me also to sort them better.

Comment 2 David Lawrence 2008-09-16 16:51:17 UTC
Red Hat Bugzilla is now using version 3.2 of the Bugzilla codebase and therefore this bug will need to be re-verified against the new release. With the updated code this bug may no longer be relevant or may have been fixed in the new code.
Updating bug version to 3.2.

Comment 3 David Lawrence 2008-12-01 19:46:47 UTC
Please reopen this issue if it is still occurring in the latest release of Bugzilla.

Note You need to log in before you can comment on or make changes to this bug.