Multiple bug reports closed/ghosted without any response

[Arctic_Vibes (Arctic)]

As an active developer, I often struggle to find the time to actually report the bugs I notice. This is mainly due to the headache involved with correctly reporting and monitoring one.

However, when I actually do get around to reporting one that I find particularly annoying, and it ends up getting either silently closed with no reason given, or completely ghosted with no response or acknowledgement that it was even seen, it further discourages me from considering to make one in the future, and instead continue to use workarounds in the interest of time.

To provide a few examples of silently closed reports that I’ve personally made:

• AutomaticCanvasSize ScrollingFrame UIPadding scales off AbsoluteCanvasSize instead of AbsoluteSize - Inconsistent with UILayout padding
• AutomaticCanvasSize ScrollingFrame Frame position only scales off AbsoluteSize on ACS axes - Inconsistent with ACS size scaling behavior

While I can theorize that these reports were closed for already being in the system due to how long they’ve been active for, I was not able to find any related posts when making the original draft, and I was not provided with any information during the closure.

To provide an example of a post that was likely never seen:

• Scaled Wrapped TextLabels with Y AutomaticSizing affect the size of a container GuiObject with X AutomaticSizing

While I can recognize that the sheer volume of reports made on a daily basis may be unprecedented for the current team, opening bug reporting to the public without prerequisites requires sufficient resources to meet that increased volume.

To add to the confusion, this issue was officially acknowledged in similar requests as of April last year, and we’ve even been encouraged to make further requests as recently as yesterday, yet there has been no visible progress.

When a bug report gets marked as closed, make it so that a reason shows

As a Roblox Developer, i find many people sometimes complaining that they got no idea why their ticket got randomly marked as “Closed”. My solution would changing the “Status Tag” to include the reasoning. I have a few examples for this. Currently the closed status looks like this: [image] My suggestion would changing the tag to show statuses like this: [image] If the post doesn’t have enough info and it gets closed then it should show as: [image] If the issue is intentional then it shoul…

Bug reports are "Closed" without a reason being given

Sometimes, bug reports are marked as “Closed”; [image] , without any kind of indication from Staff as to why. Here are 3 of them that I’ve remembered to bookmark: (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:

@Hooksmith

For the issue you’re referring to about bug reports not getting answered it’s probably best to make a new topic in Forum Help > Forum Features if you have multiple specific examples.

If these workflow issues aren’t addressed, it becomes difficult to justify why active developers should continue to invest the time required to submit high-quality reports.

[MetaVars]

We are closing these as duplicates because you posted 4 separates reports all about the same underlying issue and referencing each other.

[Arctic_Vibes (Arctic)]

While the 4 posts are related to the underlying system that is AutomaticCanvasSize, none of them can be logically linked back to a single underlying bug, hence why I distinctly separated them.

The 2 posts that were closed are keenly distinct from eachother, with the first pertaining UIPadding’s lack of respect for ACS in relation to scaling as inconsistent when compared to other padding sources like UILayouts, and the second pertaining to general GUIObject handling of ACS being inconsistent between size and position.

The 2 posts that remain open without a response pertain to UILayouts overriding the aforementioned GUIObject ACS handling behavior for size, and AutomaticCanvasSize failing to account for sources of padding/AspectRatioConstraints.

Nonetheless, the origial topic of this request is in relation to the fact that none of them got any reasoning for their closure without an explicit request, and that this absence of reasoning for closures has been a persistent issue.