-
Notifications
You must be signed in to change notification settings - Fork 187
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Potential changes to Rules for AI Triage Service #9964
base: main
Are you sure you want to change the base?
Conversation
"suggestion" : string | null, | ||
"solution" : string | null |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"suggestion" : string | null, | |
"solution" : string | null | |
"suggestion" : null, | |
"solution" : null |
@@ -70,10 +70,12 @@ _**Predictions made**_ | |||
|
|||
```json | |||
{ | |||
"labels": [ | |||
"labels" : [ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd suggest that we break this out into the 4 possible states with examples for each:
- Manual triage needed. (empty labels, no suggestions, no solution)
- Label prediction made for triage. (labels populated, no suggestion, no solution)
- Label prediction with suggestion (labels populated, suggestion populated, no solution)
- Label prediction with solution (labels populated, no suggestion, solution populated)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For suggestion/solution example I just provided the first bit. Not sure if you would want a complete example.
Using this PR to discuss changes to the AI Label Service to include AI comments. Changes mainly surround the response structure, and how we react to the new fields.