It's good to know there are at least internal discussions happening but I'll still reiterate the fact w1f1n00b raised the problem here 2 years ago. Maybe a section in the release notes with "unverified" CFDs so we can review and help you guys out if we're seeing the same problem.
It appears to me that the team doesn't have a production sized test environment to recreate and monitor bugs, so many of these CFDs will always be unverified.
Since 7525 is the example being used I had noted it in my comment since an engineer had spotted the issue on my 650s/510s, I don't believe I was the originator for that CFD so wouldn't multiple environments justify it as being verified?
I still have multiple issues being looked at, most of which I would expect to be "verified" and nothing is in the latest release notes. On 10.4.3 SDR killed our network, the CFD-7332 that may be related was addressed in 10.4.4. I have been advised to review WIPs prior to putting the new release into testing for Extreme, but there's nothing identified in the release notes for this new problem. I'm fairly sure I shouldn't be getting special treatment and it should be common knowledge in the release notes so why hasn't it been added?
Engineer notes for this SDR example;

I'll add my current cases for reference to others that may see similar issues, I can see a few client tracking problems in the release notes but I have a couple more, including CFD-7604 "hostname not appear on client page" which was created after being verified by the engineer to keep it separate from another issue in the original ticket.

CFD-7619 has an old article being addressed here https://extremeportal.force.com/ExtrArticleDetail?an=000102165 with the fix being implemented mid-Feb but doesn't appear in either release notes (firmware or cloud IQ).
Client tracking was one of the primary reasons I chose Extreme for our site and it hasn't worked this year. My most recent update on it is;

Others will be seeing the same problem but there are no updates anywhere on why basic functionality isn't reliable.
I don't enjoy spending my time troubleshooting and addressing issues that should be addressed within a vendor (I've had smaller but similar issues with Fortinet recently), I would prefer to spend my time improving our systems so if these "internal discussions" can help sort out your teams processes let us know what you want from us.