Add a table and a Graphql endpoint for soliciting users feedback
What does this MR do and why?
Related issue: Iteration 2: Collecting prompt and user satisfa... (#404272 - closed)
We plan to roll out multiple features related to AI, but we want to collect user satisfaction about the feature to identify whether we're moving in the right direction.
As a result:
- A database table is added
project_feature_feedback
to store the feedback given by a user about a particular feature - GraphQL endpoint is added to handle the response from frontend
Example of usage the endpoint
mutation featureFeedback {
createProjectFeatureFeedback(input: {projectPath:"gitlab-org/gitlab-test", featureType: SOURCE_CODE_EXPLAIN_CODE, feedbackType: UNSATISFIED}) {
errors
}
}
Screenshot
Here's an example of the feature represented in UI: