This is a user-to-user peer support forum, the but report/features system that goes directly to the engineers is their UserVoice system. That does go directly to the engineer's system, and at least one engineer logs every post directly.
Thank Neil. I've been posting bug reports to Adobe's UserVoice for a number of years now and very rarely do I see Adobe take any action to fix things so I thought I'd try here.
I really think the people at Adobe need to rethink their approach to bug reporting or at the very least provide some guidance as to what information they want see before taking a bug report seriously. UserVoice isn't the right platform - there isn't even a way to categorise posts as bug reports, posts aren't linked to specific releases and we rely on the report being voted on in large numbers for before Adobe takes any notice. It's a complete mess.
You're looking at it quite differently than they do, because 1) you're a user and 2) we can't see the other side of that input site. Because that site is a data input operation.
Everything posted is logged by at least one engineer, and collated data sent up to the higher managers who use metrics to determine budgets. So things don't "stay" there, they just enter the developer's system there. So from their end, it works as expected. Data acquisition. (Engineers, remember, who have metrics-on-the-brain "guidance" from above. Neither are particularly ... um ... normal? ... type humans.)
"We" don't see the aggregated data acquired of course. So yea, it's kinda bizarre until you understand what it is, why it is what it is, and see how the engineers and managers use it.
And they do pop back to users typically privately when they see further data could be useful from that specific user.