Bug reports are "Closed" without a reason being given

[Judgy_Oreo (DisplayName)]

Sometimes, bug reports are marked as “Closed”;

, without any kind of indication from Staff as to why. Here are 3 of them that I’ve remembered to bookmark:

Players.MaxPlayers displayed incorrectly in studio edit mode; corrected in game after some delay

Reproduction Steps This issue currently occurs for Project Frontlines Testing - Roblox. It occurred for one other place pertaining to the same project (although not in the same universe) roughly one year ago. I addressed it with I workaround which I’ve been using until recently. Expected Behavior The max player count of the place in question is set to 20. I expect to see 20 in the properties tab for MaxPlayers, PreferredPlayers. I expect to get a value of 20 whenever I write game.Players.MaxP…

StudioFragmentAutocomplete4 case where autocomplete suggestion doesn't show up

Description Case where the fragment autocomplete breaks. Re-production Steps There are multiple ways this breaks. If there’s one, it’s already a reason to avoid looking for more until one is fixed, because these things have to be connected somehow. for k,v: Player in pairs() do v. -- position carriage here end Create a script with the code above in Studio and follow the inlined comment’s instructions. Write v. in the closure, and you’re supposed to get autocomplete suggestions. See Privat…

Large Number of Friends Causes Older Friends' Profiles to Display Incorrectly

I’ve noted that upon acquiring a large number of friends (close to the new 1,000-friend limit), profiles of older friends seem to be displaying incorrectly. Specifically, the “Unfriend” button does not appear, and instead, an “Add Friend” button is shown despite these individuals being in my friends list. I also have the ability to join my ‘older’ friends in games, as the “Join” button appears once they have entered an experience, as a normal friended account would – Except that it says “Add Fri…

(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.)

EDIT: Here is another one:

Glass being opaque regardless of transparency on Realistic lighting style.

Any part with the glass material will be opaque regardless of the transparency property set, leading to glass parts becoming black the higher the transparency. Note that this only affects “Realistic” LightingStyle, and glass will appear as intended on “Soft” LightingStyle. [Screenshot 2025-03-10 170443] Expected behavior Parts with glass material should properly be affected by their transparency property on Realistic LightingStyle. [Screenshot 2025-03-10 171149]

[HealthyKarl]

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.

 

@Judgy_Oreo

(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.)

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?

[Hooksmith]

Moving to #forum-help:forum-features as this is not a technical issue.

Thanks for the feedback, I’ll let some internal folks know about it.

[Dogekidd2012]

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