Bugzilla emails to be sent with URL(s) to the bug(s).

[Don Carter]

Version 4.2.3, Red Hat 6 Linux, Apache server. All internal use only.

If I am the assignee for a bug, I get a nice email telling me about the bug.

If the submitter adds a comment, I get another email (better) with the URL of the bug in the html source:

href="http://circe/bugzilla-4.2.3/show_bug.cgi?id=52">bug 52</a>

Is there a way to configure bugzilla to put a URL to the bug(s) in all emails it sends out?

I took a look at the email templates and I can't figure out a way with that mechanism. Perhaps I am missing something?

Any help would be appreciated.

Don

[Thorsten Schöning]

Guten Tag Don Carter,
am Dienstag, 30. April 2013 um 20:19 schrieben Sie:

> I took a look at the email templates and I can't figure out a way
> with that mechanism. Perhaps I am missing something?

Which of your mails don't have links to Bugzilla? I've looked at some
of my last mails and mails for new bugs, for updates status, new
comments etc. all have some kind of link to the bug or comment or
whatever.

Mit freundlichen Grüßen,

Thorsten Schöning

--
Thorsten Schöning E-Mail:Thorsten....@AM-SoFT.de
AM-SoFT IT-Systeme http://www.AM-SoFT.de/

Telefon...........05151- 9468- 55
Fax...............05151- 9468- 88
Mobil..............0178-8 9468- 04

AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow

[Don Carter]

Guten Tag Thorsten
Vielen Dank für Antworten.

For example, in the case of a user reports a bug and it changes states, he gets:
(names changed to protect the innocent)

From: bugzilla-daemon@somehost [mailto:bugzilla-daemon@somehost]
> Sent: Thursday, April 04, 2013 2:08 PM
> To: <User name>
> Subject: [Bug 40855] OpenGL bug something
>
> Priority --- NextRelease Status UNCONFIRMED CONFIRMED Ever confirmed 1
> ________________________________________
> You are receiving this mail because:
> • You reported the bug.


There is a bug number in the Subject of the email so the user can look it up. The suggestion (hope) is that there is a way to put the bug number URL'ed in the body so the user only has to click on it to look at it if he wants.

The trigger for this train of thought is emails like:

> From: bugzilla-daemon@somehost [mailto:bugzilla-daemon@somehost]
> Sent: Thursday, March 28, 2013 12:53 PM
> To: Someone
> Subject: [Bug 36961] <Product> Purify Freeing Mismatched Memory (FMM) errors
>
> Status CONFIRMED RESOLVED Compiler --- Any Resolution --- FIXED
> Comment # 3 on bug 36961 from <default Assignee>
> Memory mismatches have been resolved for 1.2.3 as part of work with customerB.
> ________________________________________
> You are receiving this mail because:
> • You reported the bug.


Where "Comment # 3", "bug 36961" and "<Default Assignee>" are links (URLs) in the email. The user can click on the link to bring up the relevant bugzilla page documenting the bug.

Thanks in advance,
Don

[Thorsten Schöning]

Guten Tag Don Carter,
am Mittwoch, 1. Mai 2013 um 21:13 schrieben Sie:

> From: bugzilla-daemon@somehost [mailto:bugzilla-daemon@somehost]
>> Sent: Thursday, April 04, 2013 2:08 PM
>> To: <User name>
>> Subject: [Bug 40855] OpenGL bug something
>>
>> Priority --- NextRelease Status UNCONFIRMED CONFIRMED Ever confirmed 1
>> ________________________________________
>> You are receiving this mail because:
>> • You reported the bug.

There's content missing, my email looks like the following with
default templates. There's a link to the specific bug on top of each
mail.

http://bugzilla.potsdam.am-soft.de/show_bug.cgi?id=243

Thorsten Schöning <tscho...@am-soft.de> changed:

What |Removed |Added
----------------------------------------------------------------------------
Priority|P1 |P3
Severity|enhancement |normal

--

You are receiving this mail because:

You are the QA Contact for the bug.
You are the assignee for the bug.
You reported the bug.

[Don Carter]

OK. Well I tried a fresh install of 4.2.3 on a fresh database (same testbed) and I get the same behavior so there must be something wrong on my end.

I will just leave it until we migrate to a 4.2.5. Prior to moving the production server I will setup a new testbed on a different machine and see if it also fails.

Thanks for your help.
Don