On Wed, Nov 28, 2007 at 12:17:42PM +0100, Maximilian Albert wrote:
Hi all,
sorry if this is a dumb question but how can I change my Launchpad settings so that I do not receive an email each time someone works on one of the bugs? Is this the default behaviour for members of the "Inkscape Bug Team" group? Currently I am sent a notification for each and every change, but I'd prefer not to get my inbox flooded and rather browse the list myself when appropriate. It may be just my infamiliarity with Lauchpad (and lack of time for detailed investigation), but I wasn't able to find out how turn this off. Thanks in advance.
Hi Maximilian,
Yup, one of the outcomes of being on the bug team is being subscribed to the bug traffic. I don't think there's a way to control this individually, but the traditional solution is to set up a filter in your mail program (or with procmail) to put the launchpad mail into its own folder. I suppose you could set up another email account and use it as your primary, to keep it separate from your own email.
I too was pretty irritated by getting all the email from launchpad when I first started using it, but after learning a few tricks I now actually find it extremely useful.
First, one important note - unlike SourceForge, the emails from Launchpad work both ways. You can reply to any launchpad email, and it will automatically get attached to the bug report. :-) It's hard to understate how useful this makes the email notices.
Second, filtering. Every email program is a bit different, so look at your mail software. I use mutt (I like it's threading capabilities), and use procmail for putting the launchpad mail into folders. Here's my recipe:
# .procmailrc :0: * ^X-Generated-By:.*Launchpad launchpad
Of course, if you want to discard all Launchpad emails, just list /dev/null instead of launchpad in the above.
Launchpad puts a lot of info into its headers, which enables you to filter things even more tightly, like doing one thing with emails assigned to you, something else with ones you're directly subbed to, something else for ones that are sent just because you're a bug team member, etc. For more on this, see
https://wiki.ubuntu.com/Bugs/HowToFilter
Third, if you're using a threading mail reader (like mutt), launchpad sets the reply message id's properly, so they show up threaded. One thing I've found useful in mutt is to color code messages:
# .muttrc
color body yellow default "(rejected)" # rejected bug color index red default '~f daniel@fooishbar.org'
# X Bug Triagers color index green default '~f bryce@bryceharrington.org' # me color index brightgreen default '~f unggnu@googlemail.com' color index brightgreen default '~f tepsipakki@ubuntu.com'
# Noteworthy bug state changes color index default white '~b "Status: .+ => Incomplete"' color index default green '~b "Status: .+ => Fix Released"' color index default red '~b "Status: Fix Released =>"'
So see for example:
http://bryceharrington.org/files/mutt_launchpad.png
So looking at bug 168331 for instance, I can see without even reading the bug that ryan set it to state incomplete (probably asking if the issue still exists or something) since it's "white" (which shows up as grey for me), then Marc replied, and as a result ryan closed it as fixed (green). I can also see that ryan's been kicking ass on Inkscape bug triaging. :-) Go ryan!
Finally, I mentioned above that the email interface is interactive, so you can send replies directly. In fact you can do a lot more, if you prefer email interfaces over web interfaces, including updating states, subscribing or assigning people, tagging, marking dupes, and tons more. See this for details:
https://help.launchpad.net/BugTrackerEmailInterface
Bryce