Hi, On Sun, Feb 1, 2015 at 11:16 PM, Pine W <[email protected]> wrote:
> Thanks. Just wondering, do we have a graph somewhere that shows trends? > For Bugzilla we had http://korma.wmflabs.org/browser/its.html and http://korma.wmflabs.org/browser/bugzilla_response_time.html but now we miss graphs for Maniphest (see https://phabricator.wikimedia.org/T28 ) There is quite a gap between tasks created and tasks closed, and if that's > normal each month then there needs to be some thought about how to fix the > gap, yes? > Andre is the expert here, but he often says that all the free software projects he is aware of have ever-growing lists of open tasks. In our case, we also need to take into account these new factors: * Phabricator is not only for bugs, and many new tasks that didn't have a place in Bugzilla are being created. * Several teams had tasks open in Mingle or Trello, and now they are cloning them in Phabricator. They are not new, but count as new. * Phabricator is not only for software development projects, and this is becoming another source of new tasks. Said that, I think that everybody would benefit from having more discipline * including a % of old yet relevant tasks in current sprints * marking tasks as "Needs Volunteer" if nobody in the current teams plans to work on them * declining tasks that have been around for a long time and are not relevant, or not worth the effort of anybody Your ideas are welcome to "How to address the long tail of low priority tasks" https://phabricator.wikimedia.org/T78639 _______________________________________________ Wikitech-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitech-l
