launchpad help|
⇤ ← Revision 1 as of 2008-03-19 17:51:41
Size: 4977
Comment:
|
Size: 4662
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 72: | Line 72: |
| You can unsubscribe from bug notifications at any time. If you've subscribed | You can unsubscribe from bug notifications at any time. |
| Line 74: | Line 74: |
| '''Individual bugs:''' visit the bug report and click ```Unsubscribe``` in the ```Actions``` menu. '''All bugs in a particular context:''' visit the context's overview page - such as a project's overview page - and select ```Subscribe to bug mail```. Follow this if you're a bug contact but no longer want to receive the associated bug notifications. {i} '''Note:''' if you receive bug mail because you're in a team that is a bug contact, reporter, commenter or assignee, you must leave that team to stop receiving the notifications. |
|
| Line 77: | Line 81: |
| ||<tablestyle="float:right; font-size: 0.8em; width:30%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;">attachment:google-reader-bugs-feed3.png|| ||<style="text-align: center;">'''A bugs feed in Google Reader'''|| |
|
| Line 78: | Line 84: |
| Use the first two paragraphs to summarise all the important points about this article. | You can subscribe to a feed of the bugs that affect a person, team, project or distribution. You can also subscribe to individual bugs. |
| Line 80: | Line 86: |
| Tell the reader if this is the information they need as soon as possible. | Most feed readers will automatically discover the bug feed if you give them the URL of the bug report or the person, team, project or distribution overview page. The bug feeds takes the format: |
| Line 82: | Line 88: |
| = Instructional text = | '''Individual bugs:''' ```http://feeds.launchpad.net/bugs/<number>/bug.atom``` |
| Line 84: | Line 90: |
| Where appropriate, use step by step instructions: | Replace <number> with the bug number. |
| Line 86: | Line 92: |
| '''Step 1:''' Give concise and unambiguous instructions. | For example: http://feeds.launchpad.net/bugs/1/bug.atom |
| Line 88: | Line 94: |
| '''Step 2:''' Try not to state the obvious, unless you're writing for a novice user. | '''Projects and distributions:''' ```http://feeds.launchpad.net/<project or distro name>/latest-bugs.atom``` |
| Line 90: | Line 96: |
| {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. attachment:screen-shot.png {i} '''Warning:''' If you're about to tell the reader to delete or otherwise change something that would be hard to restore, warn them. |
Replace <project or distro name> accordingly. |
| Line 99: | Line 99: |
| == Full screen shots == | |
| Line 101: | Line 100: |
| ||<tablestyle="float:right; font-size: 0.8em; width:30%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;">attachment:proj-announce.png|| ||<style="text-align: center;">'''Describe the screen shot here'''|| |
For example: http://feeds.launchpad.net/ubuntu/latest-bugs.atom |
| Line 104: | Line 102: |
| 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. | '''People and teams:''' ```http://feeds.launchpad.net/~<person or team name>/latest-bugs.atom``` |
| Line 106: | Line 104: |
| 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. | Replace <person or team name> accordingly. |
| Line 108: | Line 106: |
| 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. |
http://feeds.launchpad.net/~bzr/latest-bugs.atom |
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.
ContentsBRTableOfContents |
Overview
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:
- subscribe to a bug
- subscribe to a milestone, project, package or distribution
- take a role that results in bug mail:
- bug reporter
- assignee
- commenter
project or package [:Bugs/BugContactRole:bug contact].
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:
- a new bug is reported
- someone makes a comment on a bug
- a bug's status or importance changes
- a bug is assigned to someone
- a bug is targeted to a milestone
- a bug is marked as affecting a new series, package or project.
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;
- importance=Low; assignee=None;
X-Launchpad-Bug-Private: no X-Launchpad-Bug-Security-Vulnerability: no X-Launchpad-Message-Rationale: Subscriber (Exaile)
- @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.
Project:
product: the project's Launchpad name
status
importance
assignee
Distribution package:
distribution
sourcepackage
component
status
importance
assignee
Unsubscribing
You can unsubscribe from bug notifications at any time.
Individual bugs: visit the bug report and click Unsubscribe in the Actions menu. All bugs in a particular context: visit the context's overview page - such as a project's overview page - and select Subscribe to bug mail. Follow this if you're a bug contact but no longer want to receive the associated bug notifications.
Note: if you receive bug mail because you're in a team that is a bug contact, reporter, commenter or assignee, you must leave that team to stop receiving the notifications.
Atom feeds
attachment:google-reader-bugs-feed3.png |
A bugs feed in Google Reader |
You can subscribe to a feed of the bugs that affect a person, team, project or distribution. You can also subscribe to individual bugs.
Most feed readers will automatically discover the bug feed if you give them the URL of the bug report or the person, team, project or distribution overview page. The bug feeds takes the format:
Individual bugs: http://feeds.launchpad.net/bugs/<number>/bug.atom
Replace <number> with the bug number.
For example: http://feeds.launchpad.net/bugs/1/bug.atom
Projects and distributions: http://feeds.launchpad.net/<project or distro name>/latest-bugs.atom
Replace <project or distro name> accordingly.
For example: http://feeds.launchpad.net/ubuntu/latest-bugs.atom
People and teams: http://feeds.launchpad.net/~<person or team name>/latest-bugs.atom
Replace <person or team name> accordingly.
