Not logged in - Log In / Register

Revision 1 as of 2008-03-19 17:51:41

Clear message

DRAFT: this page is a work in progress. Please [:Feedback:seek further help] or check the [:TitleIndex:wiki index] for a complete page on this topic.



Launchpad uses notification emails and Atom feeds to help you stay on top of the bugs that interest you.

Bug mail

There are three ways to get bug notifications by email:

Subscribing to an individual bug is as simple clicking Subscribe on the bug report page. You can also subscribe another individual or a team to a bug. However, you should only do this if you're certain the person or team members are happy for you to do so.

Subscribing to an entire milestone, project, package or distribution

If you're the bug contact for a package or project you'll automatically receive email about updates to any bugs relating to that package or project.

To receive notifications about a milestone in a project, a distribution (e.g. Ubuntu) or a package or project for which you're not a bug contact, click Subscribe to bugmail in the Actions menu on the milestone, project, package or distribution bugs overview page.

What you'll receive

Launchpad sends bug notifications when:

You can filter bug mail based on both the subject and headers. A prefix of [NEW] in the subject lets you distinguish emails about newly reported bugs from updates about previous bugs.

Here's an example of the headers Launchpad added to an email about a bug reported against Exaile:

{{{X-Launchpad-Bug: product=exaile; status=Confirmed;

X-Launchpad-Bug-Private: no X-Launchpad-Bug-Security-Vulnerability: no X-Launchpad-Message-Rationale: Subscriber (Exaile)


They're fairly self-explanatory but the content of X-Launchpad-Bug differs depending on whether the email is about a distribution package or an upstream project.


Distribution package:


You can unsubscribe from bug notifications at any time. If you've subscribed

Atom feeds

Use the first two paragraphs to summarise all the important points about this article.

Tell the reader if this is the information they need as soon as possible.

Instructional text

Where appropriate, use step by step instructions:

Step 1: Give concise and unambiguous instructions.

Step 2: Try not to state the obvious, unless you're writing for a novice user.

{i} Note: Highlight important information with a note.

Step 3: Use a well cropped screen shot if it will help orient the reader. Don't let the screen shot replace instructional text: not everyone can see your screen shot. Don't worry about borders or annotation for small, cropped screen shots such as this.


{i} Warning: If you're about to tell the reader to delete or otherwise change something that would be hard to restore, warn them.

Full screen shots


Describe the screen shot here

Some screen shots will be better placed to the right of your text. As they're not placed directly below the text that they support, use a border and short description.

Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Aliquam sagittis. Aliquam eros dui, scelerisque id, consequat in, accumsan vitae, pede. Suspendisse neque ligula, scelerisque ac, mattis ut, aliquam quis, odio.

Proin nunc nisi, fringilla ac, congue ac, luctus eu, lacus. Maecenas ac purus. Cras felis metus, ultricies non, euismod ac, accumsan eleifend, leo. Quisque imperdiet tempus tellus.

Ut euismod, diam nec adipiscing interdum, tortor orci fringilla nisi, vel blandit erat magna at nisi. Fusce hendrerit odio non metus. Mauris nisl massa, dapibus id, feugiat quis, blandit a, quam. Integer tincidunt feugiat nunc. Curabitur iaculis egestas elit. Nam imperdiet suscipit odio.