Allow users to provide feedback on the response generated from the RCA feature

Release notes

Problem(s) to solve

Problem

We cannot improve our model for Troubleshoot unless we know what's not working well today. Metrics and direct feedback by users is the way to learn about it.

We have a generic feedback form for users within Duo Chat. We don't have a way for users to give context that the feedback is about the RCA feature. With increasing adoption of the feature, the number of feedback by the users is not increasing.

The aim is to capture a proof of value metric for RCA. We don't have a way to learn from the users if the response suggested was helpful or not. There are some lagging indicators we could measure at a project level but it would be great for users to have a way to give feedback immediately.

Proposal

1. After integration with Duo, ensure the form input for feedback happens in relation to RCA feature. Propose mentioning in the form which feature (e.g. Troubleshoot) users are providing feedback for.
   1. Ongoing work by the AI team to capture category for prompts/questions, a need highlighted in conversation in an MR with Katie: Issue
   2. Experiment plan by the PE team to test the hypothesis: A strategically placed mechanism that allows users to provide quick feedback for response generated by RCA will increase the number of feedback received for RCA
2. Set up tracking for Time to successful pipeline and Time saved by using RCA to triangulate with direct feedback for a more rounded and credible inference in future.
   1. Issue: #480070

Implementation Notes

We also need to figure out how the user reactions will be stored and can be viewed as reports later.

Intended users

Feature Usage Metrics

Does this feature require an audit event?

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.