Give us a proper bug reporting tool.
If I am posting a bug report, I am not giving Adobe an "idea." Everything about this reporting page indicates that anything posted here will be completely ignored. Honestly, it's insulting that a subscriber giving Adobe almost $60 a month should be treated this disrespectfully. Put in a proper bug reporting mechanism that prioritizes bug reports and offers some kind of feedback to indicate whether the bug has been addressed or deemed invalid.
What additional features would you like to see in a bug reporting tool?
The UserVoice platform is a new tool (as of 2018) that Adobe DVA product teams are using to track user feedback, and allow public voting and commenting on suggestions. Prior to this, reports were not visible to the public, so no voting or discussion could occur on a given report.
Submissions to this site are reviewed by the Adobe DVA product teams. Not every submission will receive a response, but we are reading the submission and using the feedback in our planning process for future updates to After Effects, Premiere Pro, and our sibling applications. We’ve closed many submissions to this site as completed after a new update has been released, when the submission was addressed by the update. Other submissions are closed as not actionable, or declined, if the request does not align with our development plans.
I agree that there can be some improvement to how bug reports are submitted through UserVoice, and we are evolving our use of this platform as we go. But instead of my opinion, I would like to know more about what improvements you would like to see. What would make you more likely to submit bugs via this site, and have confidence that your submissions have been received by us?
Graham Austin commented
Mixing bug reports and 'hot' ideas is confusing. Just make a separate heading in the dropdown box called 'Bug Report'
Felix Dames commented
A bug is not an idea or feature request!
Discussing bugs in public could throw a bad light on your company...
But if Adobe wants to use UserVoice for bug reports at least give us a category called "Bugs", "Issues" or "Defects" where we can directly post it as a bug or with an Hashtag #Bug so that it does not get burried under all feature requests. It would also help to find already reported bugs and constribute to them by confirming these or adding additional Information.
Another thing you could include on a bug report is whether the application crashes with an error message, closes without warning, or just doesn't do something expected (or does something unexpected). Then there's the usual OS, OS version, & related information so the developers can see whether the bug is platform or hardware specific (or not). This information would be inappropriate on a feature request, but, imho, a requirement on a bug report. Big difference between running Windows 7 and Windows 10! Right now, I'm trying to figure out where to report that AE version 16.0.0. keeps closing unexpectedly, and I'm pretty clueless as to what's causing it or even if it's a broad-based problem or maybe just my own installation. I haven't used the application in a couple of years, so I don't even know if it's the recent upgrade or not.
Thanks for the additional detail, Mike.
In general, I agree with your assessment. Information like reproducibility, system information, and priority/severity are all important to a well-written bug. Having spent a decade in software QA, such detail is critical to a well-written bug report.
That said, in my experience, well-written bug reports are not often received via public forms. There are a people like yourself that understand what information to supply in a bug report, and I always appreciate that, but most of the time bug reports require a little imagination from the QA or developer receiving them. Even when we've provided templates or fields that require such details to be filled out, they're often blank or incorrect.
Regardless, as I mention above, I hope to make some improvements to how we use UserVoice to track bug reports. We don't want any feedback to be considered insignificant.
Thanks for your attention. Please keep the suggestions coming.
Michael Foran commented
Thanks for the follow up Tim. From my perspective, it seems inappropriate to combine bug reporting with feature suggestions. The former should be promptly reviewed for their validity and importance, while the latter are generally less pressing affairs. Additionally, I would think it is easy for a bug report to be lost in the deluge of suggestions users give, and may be missed. By tagging everything as an "idea" it gives the impression that all submissions have an equally insignificant importance. Other Bug reporting systems I have used allow the submitter to give the bug a priority rating, note whether it is reproducible, and areas for the dev team to follow up on whether it has been reviewed and addressed. While I wouldn't expect every bug to be addressed directly, a system like this would help separate the wheat from the chaff, so to speak.