You are correct that on further review this one is not fully “fixed”, and there may be others in the same situation. Sometimes solutions to bugs are incremental, and may begin with changes to logging before future fixes occur.
The failure in having it listed as “Fixed” is, as you say, a communication one. The above list comes from a data export of updated tickets from JIRA. Unfortunately JIRA doesn’t have a concept of “partial fixes”, so these get included. Ideally it would be nice to review each code change to verify that an actual fix was made before being added to the list, unfortunately that is not feasible for us when we have some updates as large as this one.
We provide as much information around updates as we can, but that can lead to cases like this. However with the combination of our public JIRA site and access to Github, we have tried to empower our users to access the information that is important to them.
Cheers