I am just giving my guesses on the matter. I suggest you try replying to the thread with more details about your issue popping up and see if that helps resolve anything. If it doesn’t, contact Roblox Support.
I’d suggest creating a new topic instead of bumping. The conditions might’ve changed in the 4 months.
I’d suggest creating a new topic instead of bumping. The conditions might’ve changed in the 4 months.
In the situation that I referenced, there was absolutely no change in conditions. The post was never addressed by the engineering team and the bug continues.
For those cases, I’m providing the feedback that we should have a mechanism as a community to bump these sort of posts, as they explicitly said it is against the rules to repost a bug report
There has to have been a mistake from the staff. I have bumped my old feature requests/bug reports a few times and it doesn’t get flagged.
The rules dont’ say you can’t bump your own posts.
I had a large conversation with @PilotGuy27 and @Pirate_Treasure. They were both firm on this point.
There is also an official message from the Roblox account sent when you bump a topic instructing you “Do not bump topics and do not post duplicate topics either”
/shrug
considering you pinged them they will be notified, perhaps they should shed some light on this because now i am questioning myself whether or not i should do this/how i should do this. seems weird
Bumping posts is a very obscure part of the guidelines. Since you can add more information to a topic without replying, I guess you aren’t allowed to reply to your own topic just to get more views. But adding more information can also be considered as “bumping”, so I’m not sure.
I also made a bug report almost like 7 months ago. It still happening and no one cared about it, so your case isn’t unique.
If you add use case and motivation, that’s not inappropriate bumping. The rule is meant to avoid simple “this is still happening” bump posts. Add a use case or motivation on how it’s blocking your development and you’re totally fine to post to whatever old unresolved topic.
1 Like
To my knowledge of a bug report has not been dealt with in a year or two / is marked as solved and is still occurring it is perfectly valid to still bump and state that the problem is still occurring, as for the first use case I guess this could now be invalid since I have noticed DET checking if bugs still occur.
Regardless if a bug report is marked as solved and still is occurring I believe it is the right thing to do to bump the post in contrast to making a new one so long as you are certain the issue is the same
4 Likes
I think my larger issue with this is that it’s really discouraging to report a bug and have it completely ignored with no responses from the Roblox staff for multiple months. Clearly if I don’t bump the post, it’s literally never going to be addressed, and what that means is that I devoted my time to documenting a bug just for it to be lost.
I think the current system is built around some “luck of the draw” for when you happened to report so that a bug gets fixed or ignored based on the amount of bugs reported in some period of time.
One of two things is happening:
- The engineering team is legitimately tracking some bugs in some invisible backlog
- The engineering team is not tracking these bugs
If they’re doing the former, it’d be nice to have some visibility so that at least I can know the engineering team read my post, acknowledged the bug, and added it to a backlog.
If they’re doing the latter, then it’s a bad policy to be against “this is still happening” bump posts, because there’s also a rule against duplicate posts. This is essentially a rule which instructs us to allow a bug to continue and let the bug report get lost
To my knowledge of a bug report has not been dealt with in a year or two / is marked as solved and is still occurring it is perfectly valid to still bump and state that the problem is still occurring, as for the first use case I guess this could now be invalid since I have noticed DET checking if bugs still occur.
This is what I’m advocating for, but the Roblox Staff is explicitly telling us this is against the rules and deleting bumps to posts like this.
Basically the problem is that staff are notified when a new topic is created, not when you bump it. So while bumping might give some satisfaction that it’s back at the top of the page, it basically does nothing, so unless it adds backing to the bug report / feature request it’s kinda pointless. A staff member would need to happen to see it be bumped and then raise it manually which is rare.
Also it’s hard to define a threshold for what kind of bumps are allowed and not. e.g. if everyone starts spamming up all of the old unresolved bug reports, that would get annoying and lose value really fast.
It’d be better if Roblox just used like count, view count, or some other metric on old posts to see which ones need more attention, rather than relying on post time filtering.
4 Likes
I feel like part of the solution here includes having a staff member respond to each bug report and acknowledge it as valid/invalid and add it to some sort of backlog.
This has two benefits:
- No bug reports are lost, even if they’re less pressing
- Each user reporting a legitimate bug is at least acknowledged, which will encourage users to continue to report even the bugs with lower value
Basically the problem is that staff are notified when a new topic is created, not when you bump it.
With this in mind, it should be valid to recreate a bug report after N months (3, 6, …) if it hasn’t been addressed or acknowledged. I think modifying the policy to allow that sort of repost would be reasonable since I doubt the staff would go along with my suggestion of a public backlog or acknowledgement mechanism
2 Likes
Did bumping get turned on in response to this?
The topic in question: Gif on VectorForce page doesn't play
This seems like it would be really useful for the bug categories and #platform-feedback:developer-hub.
That was just something I did myself to see to also bring attention to the unaddressed DevHub category post.
I decided to bump that post, in particular, because it was made at a time where significantly fewer DevHub topics got responses, and if successful in getting a response, I was considering encouraging DevRel to use it for old topics in the category, and maybe branch out from there.
4 Likes
So it sounds like as a Community Sage, you saw a valid reason for bumping an old bug report that wasn’t addressed.
It’d be nice if we could get some input from Roblox Staff on the problem that we’ve identified in this thread. Without a change in the rules, the “Development Engagement Team” will continue to delete any form of post bumping
If there’s a valid reason to bump a post like bringing up a new blocker I can’t see them deleting a post unless the post is like 3> years old, in which case making a new one would be preferred if possible.
The specific reason I chose to do this in the DevHub category is that the impact is low but responses to threads have been relatively high – if it doesn’t garner a response from staff then it doesn’t work and probably isn’t a good solution.
1 Like
I don’t think your assumptions are a realistic reflection of how the moderation staff for the devforum approach their roles.
When reading through this thread, I believe the conclusion most people would reach is that the staff needs to implement a mechanism for reminding the engineering team of bugs that are being ignored. There are a few different solutions we’ve discussed in the thread.
The current enforcement of the rules by staff prevents the following:
- Bumping old threads with bugs that were never resolved
- Creating a new thread to bring up a bug that was reported in an old thread
As the staff will actively remove these sort of posts since they don’t add new information to the old, ignored bug report, there is currently no mechanism to bring an issue back to light.
I feel like this topic is a little too pedantic on the rule. Valid bumps are fine, as highlighted here:
If staff really didn’t want you bumping your own topics they would have auto-closed them within a week or so.
