Formal API / SDK / developer bug reporting tool

  • 3
  • Idea
  • Updated 7 months ago
  • Implemented
There should be a proper place to submit repeatable bugs in the Adobe developer tools that gets proper attention and processing. This forum is for aggregating opinions and preferences, not improving quality. As Adobe is taking CC suite further and further into a platform and an ecosystem, it should up the ante on support quality also.
Photo of Matias Kiviniemi

Matias Kiviniemi

  • 8 Posts
  • 0 Reply Likes

Posted 3 years ago

  • 3
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 813 Reply Likes
Yes, this forum is also for bug reports.
Photo of Matias Kiviniemi

Matias Kiviniemi

  • 8 Posts
  • 0 Reply Likes
I know it _is_, but it really should not be :)

Look at it from this perspective, you don't want one line "there's a bug in feature FOO" reports that you'd have to investigate from scrap. You want to know what version, Win/Mac, OS version, 32/64, steps to replicate, sample PSD, right? I don't mind doing that (since solving the issues helps me in my work), but in return I want to know it actually gets processed. I'm not wasting two hours of my work time for that if there is no response .

A proper bug reporting site will
- Help you submit all of above in proper format
- Search reports (using meta data) so you could add to old instead of creating new
- Create trackable tickets with discussion, voting, etc.
- Acknowledge & process all submissions
- Provide status updates (~replicated, more info needed, planned, in development, rejected, etc.)
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 813 Reply Likes
Correct - we want more detail, so we need a forum where we can ask questions.
We'd also like to merge identical complaints, so we need a forum.
We'd like to mark solved, acknowledged and in progress reports - which this forum lets us do.
We would like it to be easily searchable -- which this forum, eh, mostly does.
We like to get votes and comments on how a bug (or feature request) affects users - so we need a forum.
Everything you said a proper bug reporting site should have - already exists here, plus some.

Face it: most users have no earthly idea how to fill out a proper bug report form. Heck, even some developers have trouble with it. And almost zero users would be able to understand all the details in a bug report entry. Plus there are frequently details in bug reports that should not be seen by end users (like discovered but not yet announced security vulnerabilities). Actual bug report database entries are something you want to keep inside the team, not visible to the outside (except in special circumstances, usually shared with specific beta testers or security researchers).

So we have a forum, and related the forum posts to our internal bug report database.
Photo of Rory Jaffe

Rory Jaffe

  • 37 Posts
  • 5 Reply Likes
It would be nice to provide feedback when a bug is reported, so that we know you're going to follow up on the report. I've reported a number of bugs and have heard nothing from Adobe. And the bugs haven't been fixed yet.
Photo of Matthew Tyler

Matthew Tyler

  • 1 Post
  • 0 Reply Likes
I would suggest BugRem tool for Feedback/Suggestion and bug report. it provides many feature of feedback like 'screenshot' feedback to highlight specific part of web page.