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.
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:/ /pad.lv/ 123] I say".