Idea Summary

The standard APEX Feedback feature provides a convenient way for users to submit comments and for developers to respond. However, investigating a reported issue often requires additional information and several exchanges outside the application.

I would like to see the existing Feedback feature enhanced with the following capabilities:

1. Screenshot paste and capture
   Allow users to paste screenshots directly from the clipboard with Ctrl+V, drag and drop images, and capture the current application page using a built-in button. Support multiple screenshots and a preview before submission. When capturing the page, exclude the Feedback dialog so developers can see the underlying screen.
2. Optional reproduction prompts
   Provide optional fields such as “What were you trying to do?”, “What steps did you take?”, “What did you expect?”, and “What actually happened?” These would help users describe an issue clearly while keeping simple feedback quick to submit.
3. Relevant error diagnostics
   Allow feedback to include the displayed APEX error message, an available debug reference, and relevant JavaScript errors or failed-request details. Developers should be able to configure what is collected and exclude sensitive information.
4. Feedback classification and impact
   Let users classify feedback as a bug, enhancement request, usability issue, or performance issue. Include a simple impact selection, such as “Blocking my work,” “Workaround available,” or “Minor inconvenience,” to help developers prioritize.
5. Conversation and notifications
   Extend the existing Response field into a conversation thread. Users and developers should be able to ask questions, reply, and add screenshots to the same feedback entry. Notify the submitter when a developer responds or changes the status, and allow the user to confirm whether the issue is resolved.

Use Case

These enhancements would be useful during everyday application use, user acceptance testing, and production support.

For example:

• A user reports an incorrect result or layout problem. A screenshot shows exactly what they see.
• A tester encounters an issue after several actions. Reproduction prompts help document the sequence and expected behavior.
• A user receives an intermittent error. Relevant diagnostics give the developer a starting point even when the issue cannot immediately be reproduced.
• A support team receives multiple reports. Classification and business impact help distinguish urgent problems from improvements.
• A developer needs clarification or wants a user to verify a fix. The conversation remains attached to the original feedback, with notifications keeping both parties informed.

The benefit would be faster investigation, fewer clarification emails, and better communication between users and developers.

Preferred Solution (Optional)

Implement these capabilities as configurable enhancements to the native APEX Feedback feature, available through the Feedback creation wizard and Feedback Settings.

Keep the initial form simple: feedback text, screenshot controls, and classification. Optional reproduction questions and diagnostic details could appear in expandable sections.

Provide declarative settings for developers to enable individual capabilities, configure attachment limits, control diagnostic collection, and set notification preferences. Users should be able to review screenshots and any diagnostic information included before submitting.

Extend the feedback review interface with a conversation history, additional attachments, and a “My Feedback” view where users can track their submissions, reply to questions, and confirm resolution.