The reliability of "status: resolved publicly"

[ChillyBeanBAM]

The titular status means that tagged issue is "Resolved by a merged pull request and currently available for testing on the develop branch." However, when I check the 0.8.2 milestone, a huge chunk of them don't have any pull requests attached, nor I was able to find any pull requests for them.

Proof:

Is there an explantation for this, or have I missed something?

[KoloInDaCrib]

Charting issues are resolved internally by a charter on the team, hence why there aren't any Pull Requests for them.
Another reason for there being a lack of Pull Requests to fix charting issues is because the team would prefer to do what is essentially level design themselves, as they understand the principles of their own game the most.

[Hundrec]

Kolo is correct about charting issues.
I also want to clarify that "publicly" refers to the accessibility of the commit in the public develop branch, not the visibility of the Pull Request in a public or private repository.
Many of the fixes we make are only viewable through the commit history of develop, and will eventually be included in the release Changelog.
Then, all the tags will be converted to status: resolved.

[ChillyBeanBAM]

Ah, gotcha. I would, however, like to see status: resolved publicly's description being tweaked to be more clear about this.

[Hundrec]

Sure, though GitHub doesn't seem to want me to do so!

[ChillyBeanBAM]

Huh, that's weird...