Have some way of notifying users that a bug report is actually being worked on

[052008cooljp (CoolJP)]

So recently I bumped this bug report because I have felt hasn’t been worked.

CoreGui freaks out when doing a Local Server test on a local file not published to Roblox

When running a Local Server test (where the UserIds are 1, 2, 3, etc), a majority of the CoreGui will often break, with some of the CoreGui occasionally still working, however it will fail to work a large majority of the time. [image] Expected behavior CoreGui should function normally.

You know I posted something like this Bump! This is still an issue and it is really annoying to say the least! It did get removed though and I got a PM about it. Appearently we aren’t allowed to bump it unless we have significant new information to add to the discussion.

This bug in particular above me has been around for years now and I believe multiple other people have file similar bug reports to this, however I can’t find those anymore but this one will do. It seems like this bug just isn’t being worked on at all by staff.

I am just using this bug report as an example, there have been plenty of other bugs over the years that have been made and quite a few of them are reproducible, but they just end up in the old bug report bin and they never get attention that they need.

Double clicking/tapping log button in games you haven't created opens up the Command Bar

Reproduction Steps: Go into a game that you haven’t created and double click the log button on mobile and it shows the Command Bar Expected behavior Double clicking the log button in the Developer Console should not make the command bar appear Actual Behavior Double clicking the log button in the Developer Console makes the command bar show Last Occured 10/23/2024 Side notes: This can also occur on Mobile if you double tap the log button by opening up the Developer Console …

Here is my bug report for an example that did get a response and they say file a ticket in their internal database, but ever since that reply it’s just been laying there for a while and seemingly looks like it isn’t being worked on. This might be asking for too much but as someone who reports bugs sometimes, I feel like it would be really appreciated if we could actually know if our bug reports are actually being worked on.

I know there is lot’s of bugs out there and it’s really hard to keep track of all the thousands and thousands that get filed but I really wish there was some way of notifying users that if they’re bug report is actually being worked on. Because then when our bug reports just stay there and get left with no reply of any sorts nothing. It gets us thinking that our Bug Reports aren’t being worked and it just get’s lost there.

I am sure there is lot’s of old Bug Reports older than these one’s even that just get left there to rot, and clearly bumping the Bug Reports isn’t the solution so what can we even do?

[Proven_Right]

I agree with this, and I have some info that I’d like to share here. In March 2024, Hooksmith mentioned that an “Acknowledged” status and automated update messages will be implemented for reports in the future. It’s been awhile since I last spoke to him about this topic, so maybe he can provide us with an update if he sees this. For more information, feel free to read this feature request.

@Hooksmith

In the near future we’re going to add an “Acknowledged” state to let you know it has been assigned to someone.

@Hooksmith

We’re going to show automated status change messages in the near future for the rest of the transitions.

[LuauEditor]

Engineers will state they acknowledged the issue, they will then ask you for further information ( if needed ) if not they will state they’ve assigned it to a team and give a follow-up afterwards.