Currently the issue stats reflect the time to closure across all issue "types" (regardless of label: bug, enhancement, question, etc.). However, this presents an inaccurate picture, potentially wildly so, of project responsiveness.
For example, some people use issues to track tasks such as better documentation, the need for a homepage rewrite, etc. These "issues" are very different, potentially, from bugs. And bugs are very different again from feature requests.
I'm all likelihood most users are interested primarily with 'bug' resolution time. However, it is possible for bugs to be resolved, for example, in several hours on average, while at the same time resolution time for a project housekeeping tasks ("homepage rewrite") might be months. The later should not affect the former in terms of metrics.
Currently the issue stats reflect the time to closure across all issue "types" (regardless of label: bug, enhancement, question, etc.). However, this presents an inaccurate picture, potentially wildly so, of project responsiveness.
For example, some people use issues to track tasks such as better documentation, the need for a homepage rewrite, etc. These "issues" are very different, potentially, from bugs. And bugs are very different again from feature requests.
I'm all likelihood most users are interested primarily with 'bug' resolution time. However, it is possible for bugs to be resolved, for example, in several hours on average, while at the same time resolution time for a project housekeeping tasks ("homepage rewrite") might be months. The later should not affect the former in terms of metrics.