Bug 998875

Summary:	Give summary and URL of bugs added or removed from dependencies in bugmail
Product:	[Community] Bugzilla	Reporter:	Daniel Berrangé <berrange>
Component:	Email Notifications	Assignee:	PnT DevOps Devs <hss-ied-bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:	tools-bugs <tools-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.4	CC:	jmcdonal, rjoost
Target Milestone:	4.4
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	4.4.0009	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-10-04 00:46:17 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Daniel Berrangé 2013-08-20 09:28:07 UTC

Description of problem:
I recently received an email notification about changes in a bug dependancy

The content of the email was

[quote]
https://bugzilla.redhat.com/show_bug.cgi?id=910269

Richard W.M. Jones <rjones> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Depends On|                            |998692
[/quote]


While I could switch out of my email client and go to BZ web UI and open up bug '998692', it occurred to me that it would be quite nice if the BZ email notification could tell me a little more directly, ie include the bug title, product and component.

Perhaps the notification could be structured like this:

   Depends On:
      [Add|Remove] BUGNUM [PRODUCT] [COMPONENT]  TITLE
      [Add|Remove] BUGNUM [PRODUCT] [COMPONENT]  TITLE
      [Add|Remove] BUGNUM [PRODUCT] [COMPONENT]  TITLE
      [Add|Remove] BUGNUM [PRODUCT] [COMPONENT]  TITLE
      ....

So this bug I received above would have said:

[quote]
https://bugzilla.redhat.com/show_bug.cgi?id=910269

Richard W.M. Jones <rjones> changed:

Depends On
     Add: 998692 [Fedora] [libvirt] unsupported configuration: This QEMU doesn't support virtio scsi controller [code=67 domain=10]
[/quote]


This would provide the person viewing the email alert with enough info, that they can probably avoid having to switch to the web browser to look up the bug in most cases.


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

How reproducible:
Always

Steps to Reproduce:
1. Add or remove one or more bugs from 'Depends' field
2. Wait for email alerts
3.

Actual results:
Email alert only tells you the bug number

Expected results:
Email alert tells you bug number, title, product & component

Additional info:

Comment 1 Simon Green 2013-08-20 23:36:52 UTC

If we did this, we would use the code that BMO uses. Currently they have hacked B/BugMail.pm and the template. We would do the same and then submit the changes upstream.

Here is an example of the e-mail that is sent from BMO. For those with HTML e-mail enabled, the referenced bug doesn't contain the URL. Rather, the bug number is a link to the bug.

https://bugzilla.mozilla.org/show_bug.cgi?id=3D569177

Byron Jones <glob> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Blocks|                            |905948

Referenced Bugs:

https://bugzilla.mozilla.org/show_bug.cgi?id=905948
[Bug 905948] under mod_perl, HTTP/200 is returned when etags match
If-None-Match

Comment 2 Daniel Berrangé 2013-08-21 09:14:25 UTC

That sounds like a reasonable way to address this from my POV.

Comment 5 Simon Green 2013-10-04 00:46:17 UTC

This change is now live. If there are any issues, do not reopen this bug.
Instead, you should create a new bug and reference this bug.

  -- simon

Comment 7 Simon Green 2013-11-17 23:23:59 UTC

Made some minor changes from the upstream code.