Sorry, I didn't catch that :) The tool doesn't use "patch_available" flag, it just check resolution field for "unresolved" value. Thus, if an issue has resolution field "unresolved", it will be counted as unresolved, even if issue has "patch_available" flag set.
Alexei Zakharov wrote: > >I mean does the tool itself uses the value of "Patch info" JIRA >property (every JIRA has it) during generation of reports? Does the >final report contain patch_available info? > >Thanks, > >2006/12/6, Ivaschenko, Aleksei V <[EMAIL PROTECTED]>: >> It doesn't, because there is no patch available :) >> the contribution is not committed yet. >> >> Alexei Zakharov wrote: >> > >> >Does it make use of "patch_available"? It seems to be a very important >> >field for committers :) >> > >> >Regards, >> > >> >2006/12/6, Ivaschenko, Aleksei V <[EMAIL PROTECTED]>: >> >> Thanks! >> >> It's a good idea to classify classlib bugs by module names. >> >> I'll do that in next update. >> >> >> >> Tony Wu wrote: >> >> >Good job! >> >> >So many unresloved bugs. Seems there is a long way to go. >> >> >I have a suggestion but not the requirement. What about classify the >> >> >classlib related issuses by module name, accoding to the JIRA title. >> >> >You know, the title follows the format >> [classlib][modulename]Content. >> >> > >> >> >On 12/6/06, Ivaschenko, Aleksei V <[EMAIL PROTECTED]> >> >> wrote: >> >> >> Hi! >> >> >> >> >> >> I've updated scripts for generating indicators of unresolved >> Harmony >> >> >> bugs: >> >> >> >> >> >> https://issues.apache.org/jira/browse/HARMONY-2359 >> >> >> >> >> >> Now scripts can generate separate indicators for "Classlib", >> "DRLVM", >> >> >> "VM" and "Contributions" Harmony components showing the >> proportions >> >> of >> >> >> their unresolved bugs by priority. Find the examples of indicators >> on >> >> >> wiki page: >> >> >> >> >> >> http://wiki.apache.org/harmony/Unresolved_Bugs_History >> > >> >-- >> >Alexei Zakharov, >> >Intel Enterprise Solutions Software Division >> >> Thanks, >> Aleksei. >> >-- >Alexei Zakharov, >Intel Enterprise Solutions Software Division Thanks, Aleksei.
