please mention the source package in bug mails

Bug #36586 reported by Matthias Klose
60
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

please mention the source package in bug mails, so you have a context without visiting the bug page.

Tags: email lp-bugs
Revision history for this message
Christian Reis (kiko) wrote :

The package name is listed when the bug is first filed, and it is also listed in the X-Launchpad-Bug header. Perhaps you could set your mail client to display that header by default?

If this works for you, could you please close this bug as Rejected? Thanks.

Revision history for this message
Matthias Klose (doko) wrote : Re: [Bug 36586] Re: please mention the source package in bug mails

Christian Reis schrieb:
> The package name is listed when the bug is first filed, and it is also listed in the X-Launchpad-Bug header. Perhaps you could set your mail client to display that header by default?
>
> If this works for you, could you please close this bug as Rejected? Thanks.

I see that evolution has such a configuration option, but thunderbird
(in main as well) has only an option to show all headers. yes, maybe a
bug, but the emacs vm mode doesn't have such an option either.

Simon Law (sfllaw)
Changed in malone:
status: Unconfirmed → Confirmed
Revision history for this message
Rocco Stanzione (trappist) wrote :

I'd like to +1 this request. I often make it a point to put the package name in the summary field because I know it may not otherwise be readily apparent to potential subscribers, and I often recieve emails on bugs with no idea what package is involved.

In my opinion this could be satisfied by changing the link from
https://launchpad.net/bugs/bugnumber
to, say
https://launchpad.net/distros/ubuntu/+source/srcpkg/+bug/bugnumber

Revision history for this message
Michael Bienia (geser) wrote :

Current bug mails contain the title of a bug in the Subject: header and also in the signature.
Could the signature be changed to specify the source package instead or prefix the bug title in the signature with the source package?

Revision history for this message
Diogo Matsubara (matsubara) wrote :

Although this report mentions only the source package, I guess it would also cover projects and distribution only bugs.

Revision history for this message
Christian Reis (kiko) wrote :

This means we would need to include N rows in the signature, one for each task the bug has (or N URLs, but I would not consider doing that). This is not an issue for single-task bugs. Are we sure we want to do this?

Christian Reis (kiko)
Changed in malone:
importance: Medium → Low
Revision history for this message
William Grant (wgrant) wrote :

You can get this today using the "Include bug descriptions" option on <https://launchpad.net/~/+edit>, but it's not possible to get target details without the bug description as well.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.