All Collections
Change governance
End user feedback
Review and act on feedback from Salesforce end-users
Review and act on feedback from Salesforce end-users

Feedback grid; Feedback table; Manage feedback; See all feedback; Comments; Report on comments; Review comments;

Ksawery Lisinski avatar
Written by Ksawery Lisinski
Updated over a week ago

You can use the feedback grid to review and analyze all feedback left by the Salesforce end-users and quickly take action.

Article outline


To manage feedback records, you need:

Reviewing all captured feedback

In the main application, click on 'changes' in the navigation menu and then choose 'feedback'. This is a list of feedback captured against Salesforce metadata as well as against your process diagrams.

Feedback record attributes

Every feedback record has the following attributes:

  • Feedback left by: user who left the feedback

  • User groups: Elements user groups the user belongs to

  • Feedback: Text of the feedback left by the user

  • Location: The name of the Org model where feedback was left

  • Source item: Name of the metadata component against which feedback was left

  • Record type: when an end-user leaves feedback in Salesforce, we capture the record type of the page on which it was left

  • Priority: the priority set by the end-user when they left the feedback

  • Source URL: the URL link to the exact Salesforce page where feedback was left

  • Created on: the date when feedback was created

  • Replies count: number of replies/comments under the original feedback

  • Change response: binary value that specifies if a story or requirement has been raised from feedback or not

Acting on feedback

Some feedback may be easy and quick to resolve without needing to document change request. Open the right panel for the selected feedback, review the comment, the attached image (if there is one), and let the user know how you will proceed.

If the feedback is a bigger feature request, right-click on the feedback and raise either a business requirement (big request) or a story (smaller request) to put it in your backlog.

Did this answer your question?