Diff for "FeatureHighlights/BugsByEmail"

Not logged in - Log In / Register

Differences between revisions 3 and 4
Revision 3 as of 2007-03-26 16:12:35
Size: 1729
Editor: 81
Comment:
Revision 4 as of 2007-03-27 09:45:39
Size: 1899
Editor: 217
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
Line 4: Line 3:
Launchpad allows you to manage all the bugs that affect you, entirely through your email client. Using the email interface you can: If you prefer, you can entirely manage bugs using email.

Using the email interface you can:
Line 10: Line 11:
 * record that a bug affects a different community  * record that a bug affects a different community.
Line 12: Line 13:
If you want to be notified by email every time someone reports a bug on a project or package that you are interested in, you can register yourself as a bug contact for that project or package. You will receive for every bug filed, and can respond directly to that mail in order to assign it or change its status. For the details on the email interface, please read about UsingMaloneEmail. === Email notification of new bugs in a project or package ===
Line 14: Line 15:
If you are particularly interested in a specific bug, you can subscribe to that bug and you will be emailed every time someone comments on a bug or changes its status. This is the best way to keep up to date with changes in the bug. You can ask Launchpad to email you every time someone reports a bug against a project or package that interests you, by registering as a bug contact for that project or package.
Line 16: Line 17:
Of particular interest is the combination of email notifications and remote bug watches. When you create a bug watch linking the Launchpad bug to a report in another community's bug tracker, all the subscribers will be notified when the status changes in that remote bug tracker. This is an excellent way to keep track of the big picture of community work on a bug. By replying to the new bug notification email, you can assign the bug to a Launchpad user or change its status. For the details of how to use the email interface, please read our guide UsingMaloneEmail.
Line 18: Line 19:
Sometimes you have a group of people interested in receiving mails for a set of packages, or projects. Launchpad allows you to create a team, and to subscribe the team to the bug or make the team a bug contact - then everyone in the team will get mail when a new bug is filed on the project or package. [:ReviewersGuide/TeamManagement:Understanding Launchpad teams] is the next stop on our tour. === Subscribing to specific bugs ===

If you are particularly interested in a specific bug, you can subscribe to it. Launchpad will email you every time someone comments on the bug or changes its status. This is the best way to keep up to date with the progress of a bug.

Of particular interest is the combination of email notifications and remote bug watches. When you create a bug watch linking the Launchpad bug to a report in another community's bug tracker, Launchpad will notify all subscribers when there is a change to the remote bug's status. This is an excellent way to keep track of the big picture of community work on a bug.

=== Using teams to track bugs ===

Sometimes, a group of people may want to receive email notifications for a set of packages, or projects. With Launchpad, you can create a team and either subscribe that team to the bug or make the team a bug contact.

Launchpad will email everyone in that team every time a new bug is filed against the project or package.

You can find out more about Launchpad teams in the next step on our tour,[ReviewersGuide/TeamManagement Understanding Launchpad teams].

Managing bugs through email

If you prefer, you can entirely manage bugs using email.

Using the email interface you can:

  • file a new bug
  • comment on an existing bug
  • assign a bug to someone
  • change the status of a bug
  • record that a bug affects a different community.

Email notification of new bugs in a project or package

You can ask Launchpad to email you every time someone reports a bug against a project or package that interests you, by registering as a bug contact for that project or package.

By replying to the new bug notification email, you can assign the bug to a Launchpad user or change its status. For the details of how to use the email interface, please read our guide UsingMaloneEmail.

Subscribing to specific bugs

If you are particularly interested in a specific bug, you can subscribe to it. Launchpad will email you every time someone comments on the bug or changes its status. This is the best way to keep up to date with the progress of a bug.

Of particular interest is the combination of email notifications and remote bug watches. When you create a bug watch linking the Launchpad bug to a report in another community's bug tracker, Launchpad will notify all subscribers when there is a change to the remote bug's status. This is an excellent way to keep track of the big picture of community work on a bug.

Using teams to track bugs

Sometimes, a group of people may want to receive email notifications for a set of packages, or projects. With Launchpad, you can create a team and either subscribe that team to the bug or make the team a bug contact.

Launchpad will email everyone in that team every time a new bug is filed against the project or package.

You can find out more about Launchpad teams in the next step on our tour,[ReviewersGuide/TeamManagement Understanding Launchpad teams].

FeatureHighlights/BugsByEmail (last edited 2008-06-17 14:21:19 by localhost)