feat(automatedQA): integrate AI answer generation api DEV-739#6735
Merged
magicznyleszek merged 9 commits intoFeb 26, 2026
Conversation
Member
|
@pauloamorimbr I tried testing it, but I get |
magicznyleszek
requested changes
Feb 24, 2026
Member
magicznyleszek
left a comment
There was a problem hiding this comment.
Generally works as described. Found two small things
magicznyleszek
approved these changes
Feb 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🗒️ Checklist
#Support Docs Updates, if any<type>(<scope>)<!>: <title> DEV-1234Front endand/orBack endorworkflow📣 Summary
This PR implements the flow for activating the AI response generation feature and calling the actual generation endpoint
💭 Notes
TabAnalysisflow, so we could have access to the automated feature as well.manual_qualfeature is created whenever a question is set and it's still not there. In the common flow it will happen once the first question is added. I chose that path instead of automatically creating the feature whenTabAnalysiswas opened, which i considered another viable option. This way we won´t create the feature unless the user really adds a qaQuestion.Generate with AIenabled since it's not supported for them👀 Preview steps
autoQAEnabledfeature flag enabled (?ff_autoQAEnabled=true)