Draft: Bugzilla Work Flow

Jeroen van Meeuwen (Kolab Systems) vanmeeuwen at kolabsys.com
Mon Sep 13 07:16:40 EDT 2010

Bron Gondwana wrote:
> That looks really good actually.  I guess the side question is "Is Bugzilla
> the ideal tool for this?"  I've seen setups where commit messages in the
> change management tool can be tied directly to tickets.  It's probably
> not essential though - if we have a process and we all know how to follow
> it.

There's git-bugzilla for this purpose. I haven't actually worked with it 
though. There's also a python-bugzilla CLI client, which we could (possibly) 
use as a commit hook to update any tickets referred to in the commit message.

> Speaking of which - the auto bugzilla reminder emails are great :) 
> Occasional annoyances that go away when you do the right thing are very
> useful.

Yeah, so is the "automagically" put someone in CC: on bug update, having 
someone as a QA contact, or workflow enhancements (somebody patches some bug, 
"closes" the bug and release engineering looks to forward/backporting it).

Kind regards,

Jeroen van Meeuwen
Senior Engineer, Kolab Systems AG

e: vanmeeuwen at kolabsys.com
t: +316 42 801 403
w: http://www.kolabsys.com

pgp: 9342 BF08

More information about the Cyrus-devel mailing list