Certain staff members tasked with filing bug reports internally do not do their job correctly. Specifically, @Howimetted marks bug reports that are actually ‘Closed’ as ‘Fixed’ and does not lock them after doing so. This is inconsistent with the expected behavior (followed correctly by others like @thirdtakeonit and @Focia19), which is that reports are locked and changed to the correct status of ‘Closed’.
I don’t know where else to put this, so apologies if it’s not a bug, but I doubt it’d be a feature request either. Behavior should be consistent here.
May want to see if @DevEngagementTeam can look into this matter, or something…not really sure who would be exactly the right people, since this is a Roblox employee.
But I agree this is immature, marking things as fixed should not be exactly an option unless it is entirely stated by a Engineer @ ROBLOX thst it was patched.
Pretty sure @Hooksmith can handle this (or at least pass it along to the right people), but instead of responding to the post, he silently moved it to feature requests. Probably considered low priority at the moment, even with 11 likes!
Right…I really don’t know who this person is… the Howimetted person, nor do I have any clue as to what their job is @ RBLX, so I cannot really give a say…but for crying out loud, why are we marking things as fixed? Its deceiving and confusing cause that should be for the people who do work at roblox as a engineer or what-not, that deals with the engines accordingly. Please do better.
Isn’t there a needs information tag too? It seems odd for them to say it needs information and not use that. (Unless I’m stupid and it never even existed)
I wanted to reply a week ago but i forgot. But yes, there is a “Needs Information” tag but roblox engineers decide to instead close the bug report for them to submit a new one:
This is rarely used, it could be worth a feature request where a bug report could get set into “Needs information” and if there wasn’t a new reply or the topic hasn’t been updated in the last month then it automatically gets marked as closed
I refuse to believe this issue is that hard to resolve. If anything the guy could just check this post and fix up his behavior himself (he’s getting mentioned every time I post a new link here).
In my experience as a software engineer, the company that you work for sets the standards by which you abide. This goes for code/comment formatting guidelines, backlog, etc… A full 1/4 to 1/3 of my job is administrative tasks such as filling out paperwork, reviewing bug reports, writing reports, attending meetings, etc… That’s the way the profession is. It’s not just all coding and nothing else. Here’s a gaming analogy: You have the game that you play, and then you have the metagame that you also play, if you’re familiar with D&D.
Now if you don’t comply with standards, you’re boss will give you a good talking to. If you still don’t comply, then it will move to disciplinary action, up to and including termination. Basically, you can get fired from your job for not following directions.
As much as I’m passionate about the bug reporting process and agree that this is a problem, I don’t think that it’s right to single someone out regardless of how frustrating the situation is. Harassing them by constantly quoting them will only cause them to feel discouraged and be less open to improving their behavior. There might be some context that we’re missing (I learned this the hard way with catalog asset bugs). He didn’t do this in past, so something has recently changed. I suspect that these reports are being incorrectly marked as fixed because the distinction between closed and fixed doesn’t matter internally. Both simply tell the engineers not to look into the report. This is probably the case for two of my old reports (1, 2). I understand this is confusing from a reporter’s perspective and definitely isn’t ideal. Sadly, this might not be prioritized because the process is planned to be automated in the future (1).
Edit: I just realized that he’s a regular instead of being a leader. Even though he’s in the Roblox Staff group, I think he still has to be a leader in order to lock threads. Both Focia19 and thirdtakeonit are leaders. This might be the problem.
For correction here: he’s been doing this since the beginning of time—take a look at this post from two years ago. Music_man had to manually close the post because he didn’t do so himself:
Let’s focus the on-going conversation on example bug reports rather than people where possible, focusing on specific cases is productive. You might not be able to see all the people and steps involved with specific issues from the outside looking in, and our process should be bullet proof regardless of the people working on the tickets, so this is a process gap more than anything. Thank you!