, without any kind of indication from Staff as to why. Here are 3 of them that I’ve remembered to bookmark:
(Even if you can gather the last one was closed due to being a duplicate, clearly the lack of communication can lead to people waiting for a response anyway.)
The bug report you linked that I created was closed fairly. The reason was given within the private message that was associated within the bug report, and the issue was resolved.
Regarding the bug within that post, I think it was noted it down.
It would be interesting if Bug Authors would receive a notification if the thing changed from “Open” to “Closed”, along with anyone that may be watching that thread perhaps?
These forum bug reports may be tied to a system internally? So, when someone fixes it internally and closes the ticket internally, it syncs on the forum as well?
For transparency on the ones you linked: there’s sometimes oddities from the fact that the statuses you see are representing states in our internal ticketing system.
The first one you linked is “Closed” because the ticket it was associated with has two internal tickets associated with it due to some bug, and one of them was marked as a duplicate.
The second was closed because it was a bug report of an intentionally unreleased feature, and as HealthyKarl said, the conversation of that happened in the private message. Perhaps it should not have been, because it does look odd to outside observers.
The third was closed as a duplicate, bvetterdays posted the earlier report. I have marked it as the solution.
The fourth was also marked as a duplicate, though we forgot to actually link what we considered it a duplicate of. I went ahead and did that.
No funny business going on, I think just people forgetting that the internal statuses are public-ish