feat(seer): Add user-initiated Seer activities to issue details tool output - #122952
Open
hobzcalvin wants to merge 1 commit into
Open
feat(seer): Add user-initiated Seer activities to issue details tool output#122952hobzcalvin wants to merge 1 commit into
hobzcalvin wants to merge 1 commit into
Conversation
github-actions
Bot
added
the
Scope: Backend
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
1 participant
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.
In addition to
_SEER_EXPLORER_ACTIVITY_TYPES(renamed...ACTOR_OPTIONAL...), include_SEER_EXPLORER_ACTOR_REQUIRED_ACTIVITY_TYPESwhich are Seer activities that we care about, IF a user performed them. This goes into theuser_activitysection of theget_issue_detailstool.This will affect a tool used by many Seer products across the company, so I want to be careful here. But if we include other activities performed by users, these seem valid too.
We've also had some concerns about "punishing" a user who clicks "start RCA" by assigning the issue to them, but in terms of getting issues looked at, they are probably a viable last resort. (And, of course, auto-assignment only happens if it's enabled by the customer.)