Puzzle history stat glitch: why is it so hard for Chess.com to fix this?

A couple of months back, I first noticed that the puzzle history stat for "highest achieved" puzzle failed to update correctly after I "reset all progress" in the settings to start from scratch which is how I train, i.e. 0-2000 drills every day or so. I first noticed this bug around the time Chess.com came out with its "stats feature revamp", I believe.

The stat feature always keeps the score I achieved in early December 2020, rather than update to my real highest achieved puzzle rating. For example, I achieved 2090 on February 6th, 2021, and this clearly appeared as the "highest achieved" puzzle rating in the stats until I "reset all progress" and it defaulted back to the early December 2020 value. 

I reported the bug in detail to Chess.com via "bug report" and other channels at least 3 times in the past two months, to no avail. Does anyone have a similar problem or is this bug specific to my account only? Either way, how can something seemingly so simple be so hard to fix? It's inconceivable to me that this requires more than a junior coder take a few minutes to locate the problem and fix it, but I might be wrong. 

Highest achieved February 6, 2021:



Default stat glitch:

I don't know how difficult it might be. I think it is more a matter of priorities.

The stats revamp is still a work in progress, I believe. 

Are you part of the beta group?

Thanks for the interest and prompt reply.

I work in management and understand about priorities as well as how something like this may be low on the totem pole of things to do. 

Having said that, in management, a class of problems do get immediate attention by virtue of the fact they can be quickly and simply resolved and the case closed. This is known as the "5-minute rule".  If you can do it yourself or simply have a competent person fix it quickly, then it makes managerial sense. More concretely, it means "take 5 minutes to fix this for me or tell me why it's not possible so I can put it on a "to do list" and attach an appropriate time-frame (be it 10 days, 10 weeks or 10 months) to its resolution.

Either way, almost 10 weeks have passed since the problem was reported the first time without so much as a peep from customer service, unless I missed something.

I suspect the problem is neither technical nor related to a lack of resources given the volume and complexity of tech issues to deal with. I suspect the problem is a managerial one that produces such issues as launching features without a proper quality-check, not having standard operating procedures for certain issues, etc.

I may be wrong, of course, but my feeling is some issues just get tucked away in a corner and aren't dealt with because there is faulty managerial oversight. 

I'm not part of the beta group, by the way. 

Hope you are well and safe in these strange and dangerous times.

This was posted in December in the beta club:

The time range filter might address your problem. (But if you reset your stats, it might not work.)

/ Nothing takes five minutes when you have 50 million members.  Everything that gets moved into production requires multiple checks and safeguards.

Especially when they are in the process of making major revisions to an area.

Hey, thanks for your input. 
Whether you have 100 members or 100 million members doesn't change a thing concerning something like this: organizational resources grow accordingly. In fact, things usually become much more standardized and efficient than when only a few people wear many hats. 
But I get your point and I trust you get mine so let's just agree to disagree about this particular topic. 
Thanks for your "time-range filter" suggestion. I'll try to find that and have a look to see if I can fix the issue from there. Still don't understand why the stat should default to a date in early December 2020 rather than any other date but I guess I can live with that little mystery. 

Did this ever get resolved? My puzzle stats are glitching in a similar way. C’mon, chess.com!