While Microsoft have improved in terms of using the feedback item comments to communicate information about their actions, there are still cases where items are closed without proper explanation. This can be frustrating, not just for the person who raised and commented on the item, but also for others who find it via search later on. I can provide two examples from my own experience:
A number of possible solutions were proffered to this bug, and when it was closed as fixed, there was no update to inform those persons watching the bug as to which had been implemented.
I discovered this bug report via a search, after encountering the same apparent defect during development. The bug was closed with a 'Won't Fix' status. Closing an apparently confirmed defect with 'won't fix' seems like a prime example of where further feedback is not just desirable, but essential.
In both of these cases, only a little additional effort would have been required to provide further explanation of the item resolution. Making the provision of this explanation a required part of the resolution process will help to avoid these kind of frustrating experiences.