Bug 1295705 - The related stakeholders can't receive the mail notification of status update for dependent bugs
The related stakeholders can't receive the mail notification of status update...
Status: CLOSED NOTABUG
Product: Bugzilla
Classification: Community
Component: Email Notifications (Show other bugs)
4.5
Unspecified Unspecified
low Severity medium (vote)
: ---
: ---
Assigned To: PnT DevOps Devs
tools-bugs
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-01-05 05:12 EST by Hui Wang
Modified: 2016-01-13 19:20 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-01-13 19:18:04 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Hui Wang 2016-01-05 05:12:43 EST
Description of problem:
Bug A depends on bug B.
The related stakeholders(like assignee,qe,cc'd) of Bug A can't receive the mail notification of bug B's status update.

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


How reproducible:
100%

Steps to Reproduce:
1. 
2.
3.

Actual results:
The related stakeholders(like assignee,qe,cc'd) of Bug A can't receive the mail notification of bug B's status update.

Expected results:
The related stakeholders(like assignee,qe,cc'd) of Bug A can receive the mail notification of bug B's status update. The X-Bugzilla-Type of mail header is: changed dependency.

Additional info:
Comment 1 Matt Tyson 2016-01-13 19:18:04 EST
The normal behaviour here is to only email dependent bugs if the bug state is set to CLOSED, or changed from CLOSED to an open state.

Bugzilla won't notify dependent bugs of every state change.  This is intentional and I don't see a reason to change from upstream behaviour.

> # If this bug has changed from opened to closed or vice-versa,
> # then all of the bugs we block need to be notified.

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