This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Created attachment 158279 [details] Screenshot showing ignored P2 bugs limit for Groovy area. It seems like target number set for P2 bugs is ignored and dashboard always expects 0 P2 bugs. See attached screenshots. For example in 8.2 dashboard Groovy has set 3 P2 bugs limit for Code Freeze bug tooltip still keeps showing 0 bugs at Code Freeze.
I need to look at it more carefully (today evening/tomorrow), but yes, the current code does following logic: if(in high resistence) -> set P2 limit to 0 else if (next milestone === code freeze) -> set P2 limit to 0 else -> set P2 limit based on the target number as specified Since next milestone is code freeze, it forces the target number to 0. Should I change this behavior in else block (of "in high resistence") to always respect numbers specified in dashboard settings? I guess there was a reason for this, but I admit I don't remember it :)
Yes, please do that Lado. I guess without the fix after few months mortal dashboard users would stare at ignored P2 target being confused just like I was yesterday. :) Thanks!
Fixed, not it will respect the specified targets.
Excellent. Thanks!