feat(issue-priority): Check flag before calculating issue severity #74823
Conversation
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
github-actions
bot
added
the
Scope: Backend
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #74823 +/- ##
==========================================
+ Coverage 76.26% 78.17% +1.90%
==========================================
Files 6740 6741 +1
Lines 300666 300692 +26
Branches 51707 51700 -7
==========================================
+ Hits 229301 235064 +5763
+ Misses 64737 59299 -5438
+ Partials 6628 6329 -299 |
jangjodi
approved these changes
Jul 25, 2024
Christinarlong
pushed a commit
that referenced
this pull request
Jul 26, 2024
…74823) Check the seer-based-priority flag to determine if we need to calculate first-event severity for incoming events. If the flag is not set, we default to the current behavior which determines severity for python and javascript projects. Once the flag is GA, we should remove this platform check and only calculate the severity if the flag (subscription-based) is enabled for an org. Fixes #74757
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Check the seer-based-priority flag to determine if we need to calculate first-event severity for incoming events. If the flag is not set, we default to the current behavior which determines severity for python and javascript projects.
Once the flag is GA, we should remove this platform check and only calculate the severity if the flag (subscription-based) is enabled for an org.
Fixes #74757