We also made an attempt at doing a kanban type board to track that not too many bugs were in-progress at once (definitely no more than two per dev and more like 30 or less in-progress for a group of 20 developers).
I feel like my experiments with using Launchpad to support lean development were fairly primitive, but I'm definitely a fan of using bugs, tags, and merge proposals, not so much of using prefixes on bug titles. Probably the hardest part of the experiment was how many clicks it took to register all the bugs once we had a list of 40 branches for a couple weeks of work.
I still crave a simple way to say "here's my plan for the week" and then monitor and visualize planned vs actual in some big visible kanban board type of system. Ditto for a backlog of backlogs/branches as well as work that needs estimating. Right now I'm experimenting with just tracking this manually, but it feel like Launchpad has all the raw data if I can just be disciplined enough about how we use it.
-- Elliot Murphy On Dec 4, 2009, at 7:26 PM, "Charlie Poole" <charlie@xxxxxxxxx> wrote:
Hi All, I recently decided to use the bug tracker for non-bugs for a few of my projects. It would be cool if this were easier to do. I'm currently using 'feature' and 'task' tags and experimenting with a convention that feature requests start with 'Feature:' and tasks with "Task:'. The tag is good when doing a search, but the naming convention gives better visibility in lists of bugs. Are there any plans to support this sort of distinction directly in the bug tracker? Does anyone have other tricks that would work for me? Charlie _______________________________________________ Mailing list: https://launchpad.net/~launchpad-users Post to : launchpad-users@xxxxxxxxxxxxxxxxxxx Unsubscribe : https://launchpad.net/~launchpad-users More help : https://help.launchpad.net/ListHelp
This is the launchpad-users mailing list archive — see also the general help for Launchpad.net mailing lists.
(Formatted by MHonArc.)