Evaluate the current approch for unanswered bugs thresholds
After getting some questions from XWiki regarding their score in quality metric we did some investigation. 2 queries (see JiraHandler.java for the exact query definition) are executed on XWiki issue tracker:
- To get the total number of opened issues:
Type=Bug AND Status=Open AND project = XWIKI
: https://jira.xwiki.org/browse/XWIKI-19127?jql=Type%3DBug%20AND%20Status%3DOpen%20AND%20project%20%3D%20XWIKI%20ORDER%20BY%20created%20DESC - To get the total number of issues with comments:
Type=Bug AND Status=Open AND comment!~'\"M"' AND Project=XWIKI
https://jira.xwiki.org/browse/XWIKI-19126?jql=Type%3DBug%20AND%20Status%3DOpen%20AND%20comment!~%27%5C%22M%22%27%20AND%20Project%3DXWIKI%20ORDER%20BY%20created%20DESC
In our test today we add 1022 opened issue and 673 of them have comments leading to a remaining of 349 issue without comments so flagged as "unanswered".
Value of the metric is defined by threshold get using REST API call on https://projects.ow2.org/get/ow2/Project_metrics_thresholds
The different thresholds for unanswered bugs are currently defined with absolute numbers of bugs without comments: UnansweredBugs,15.0,50.0,100.0,150.0,300.0,1
As we have a value (349
) higher than the threshold 300.0
the metric value is set to 0.
@gibello I suggest that we discuss together to validate that having absolute values for threshold is the best option we currently have. We might use percentage of opened bugs or maybe use a coefficient depending on project "popularity".