Hi Quim, Thanks. Just wondering, do we have a graph somewhere that shows trends? 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? Thanks, Pine On Feb 1, 2015 11:49 AM, "Quim Gil" <qgil(a)wikimedia.org> wrote:

It would be interesting to compare our trends to those of other open source projects with open bug or task trackers. Pine On Feb 1, 2015 7:47 PM, "James Forrester" <jforrester(a)wikimedia.org> wrote:

On Sun, Feb 1, 2015 at 2:16 PM, Pine W <wiki.pine(a)gmail.com> wrote: Also keep in mind that it is used by many people to track feature-requests (long and short-term, planned and wishlist), as well as bugs, so some growth is both inevitable and desired. (I believe this is what James is saying). But I agree that an increase of old-bug triage and resolving, would be welcomed.

On Sun, Mar 1, 2015 at 4:50 PM, Nuria Ruiz <nuria(a)wikimedia.org> wrote: It could be more interesting, although probably on the team level rather than globally, is the number of open tasks for a given priority. If, for example, the number of tasks with normal priority is growing continuously, that does signal some sort of problem with the planning.

Hi, On Sun, Feb 1, 2015 at 11:16 PM, Pine W <wiki.pine(a)gmail.com> wrote: 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 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

On Mon, Feb 2, 2015 at 10:03 PM, Gergo Tisza &lt;gtisza(a)wikimedia.org&gt; wrote: So far Phabricator has 100-150 more monthly users then Bugzilla. See the <graph> at https://www.mediawiki.org/wiki/Community_metrics#Reports -- Quim Gil Engineering Community Manager @ Wikimedia Foundation http://www.mediawiki.org/wiki/User:Qgil