Just to confirm you understand, that is what we’re shipping here today. This announcement is about that there’s now a group you can request to join and you will see the “Report Bug” button.
We’re keeping the Bug-Support inbox actively for a while as this rolls out at the same time but it’s not necessary to use that anymore.
We give monetary incentives to security-related issues reported via our Hackerone. We don’t currently give out or have plans to give out rewards for bugs reported via devforum, but we do want to make sure we are properly responding to these bugs and giving you transparency on its status, so that your time spent reporting the bug is well respected.
Since this is a significant change, I have a question about what will happen to the Trust Levels.
“Regular” was previously used as a platform for reporting bugs and requesting new features, but with the latest update released today, it looks like its importance will be decreased significantly. Therefore, it raises the question of whether there is still a need for “Regular” going forward.
“Editor” and “Leader” are only available for Roblox employees, despite “Editor” being used for those who contributed within the Post-Approval team.
I feel like a “your topic is similar to” feature (based on title/description) would be really helpful.
Especially newer posters aren’t that known with the search features (and I’m guilty myself as well for not searching thoroughly before reporting whoops)
So wait, I dont need to apply for this because I’m a regular?, wordng here’s confusing me a little.
Regardless of that, hopefully, dehooking this from regular hopefully means we get more bugs reported because there’s probably many bugs that have gone unreported because of this. This is probably a great way to slowly bring back in regular promotions again but I’ll let you decide on how to approach that.
On this note, a lot of my catalog bug reports don’t get responded to for anyone and even if they do they stay dead for several months if not up to a whole year without any response on its status or anything. Sometimes even when a catalog bug report gets responded to, sometimes the problem at hand doesn’t even get dealt with at all. I see other bug reporting categorizes have more transparency but the catalog bug report category remains dead most of the time.
I deleted my old DevForum account because after about 6 months of participating, I wasn’t able to rank up before rankups were removed. They’ve been gone for, what, almost three years now? So here’s hoping that I might still make it eventually.
(I don’t need to be told period of time has nothing to do with the criteria, I just mean that I was legitimately active during that period, making bug reports, community resources, etc. and it was extremely upsetting that instead of ever being promoted or recognized, promotions were instead completely removed.)
Exciting! I have some bug reports pending that’s been awhile now and I’m just not motivated to put them out because it takes sooo long and it’s very very tedious process. I’ve applied, and I can’t wait to process some more bug reports, so hopefully, we can have a bug-free platform!!
Probably just my paranoia, but I’m hoping this doesn’t mean the migration away from Discourse. With how the Talent Hub went, an in-house forum software would probably be awful and I (and probably at least 70% of everybody else given how the talent hub went) would 1000% leave
Yes, goal is to use groups for access instead of trust levels. As you indicated that means we’re going to move away from this weird distinction between “Member” and “Regular” where regulars aren’t actually “regulars”, they don’t really get that trust level by “regularly” using the forum, so it didn’t make much sense. Just reiterating there will be a separate announcement for that.
I’m going to follow up internally and let you know, thanks for raising that.
It should be noted that “response” does not necessarily mean resolution, as resolving a bug can take an extended amount of time for various reasons: (not limited to but including)
it might take a significant investment to fix a particular bug compared to the value that fixing it creates, so that’s why it’s not prioritized;
maybe other projects are taking priority over fixing a low-priority bug because the former brings more value to users;
it’s possible that the team has plans to revamp a feature/system that would automatically fix the bug at a later point.
it could be that the issue is not considered a bug from our point of view and is instead the intended behavior;
That being said, the goal is that you should always have an idea of where your bug report is in this funnel, if it’s being worked on or roughly why it is delayed or rejected. We want to be transparent about this and also give you a chance to discuss with us about the reason for a delay or decision not to address a bug at the moment. So thanks for bringing this up again and will get back to you.