I do believe it is still hard coded so should be working fine it all depends on what data we get from what pulse itself.. you got any particular user(s) in mind so we can look at this closer.
Thanks
I do believe it is still hard coded so should be working fine it all depends on what data we get from what pulse itself.. you got any particular user(s) in mind so we can look at this closer.
Thanks
Semi-retired from Free-DC...
I have some time to help.....
I need a new laptop,but who needs a laptop when you have a phone...
Now to remember my old computer specs..
No, it's dynamic, based on entries in a table which can be tailored per project if needed. I'd need to know a particular example as Gopher mentioned in order to check it out.
Crude milestone page shows some 10M and the last log certainly showed that it tested for 10M
Bok
I see, actually they've found a bug! And it's been like that forever, perhaps it's just that the exact rounded type numbers from whatpulse have made it more pronounced.
In VG's case on August 1st he dropped 150,000 points to reach EXACTLY 2,500,000 then on the 3rd he dropped another 50,000 to be a 2,550,000
However my sql was checking for new value > 2,500,000 and old value < 2,500,000 which did not match under either condition. It should actually be
new value >= milestone and old value < milestone
WOW, that code has been in place for about 8 years now.. fixed and I manually added those two milestones.
Nice bug!
Thanks for addressing this so quickly.