References to other bugs are mysterious in mail notifications
Bug #181013 reported by
Matthew Paul Thomas
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
When a bug description or comment refers to a separate bug report (e.g. "bug 12345"), in the Web UI this reference is auto-linked and has a title= attribute so that people easily can see the summary of the bug report.
In e-mail notifications, however, there is no link and no tooltip, so it may be difficult to understand the reference, especially if you are offline when you're reading the message. This could be fixed by including a citation in the signature section of the mail notification. Something like:
--
The foo doesn't bar
http://
You are subscribed to this bug report directly.
References:
Bug 1234567889 <http://
| Changed in malone: | |
| status: | New → Confirmed |
| Changed in malone: | |
| status: | Confirmed → Triaged |
| importance: | Undecided → Low |
| tags: | added: story-better-bug-notification |
Revision history for this message
| Robert Collins (lifeless) wrote | #1 |
To post a comment you must log in.
As sketched this would require per-user calculations on bug notifications (because not everyone can see every bug). The web page tool tips are done by calling back to LP after the page renders. We could show just a URL to make it easier to click through and ask LP about the bug.
Email is not intended to be the primary notification for users in future (in-app notifications + feeds/twitter etc are desired). These mediums all have the same underlying issue, that 'bug 1234' in prose won't be easy to resolve to a url.
Long notifications will also be tricky: given 2 pages of text and a bug reference at the top, finding the right expanded reference will be slow.
Perhaps we would be better off hyperlinking in-line - translate "In bug 123 I say" -> "In bug 123 [https:/