Skip to content

Conversation

@jgraham
Copy link
Member

@jgraham jgraham commented Sep 16, 2025

Query for user impact score on webcompat core bugs, and add this to the user story, as we do for site reports.

For now we don't set the cf_webcompat_score field for these bugs, as we need to decide if that's useful and whether to use the same score boundaries as for the individual site reports.

Checklist

  • Type annotations added to new functions
  • Docs added to functions touched in main classes
  • Dry-run produced the expected results
  • The to-be-announced tag added if this is worth announcing

Query for user impact score on webcompat core bugs, and add this to
the user story, as we do for site reports.

For now we don't set the cf_webcompat_score field for these bugs, as
we need to decide if that's useful and whether to use the same
score boundaries as for the individual site reports.
@jgraham jgraham force-pushed the webcompat_score_core branch from 712217f to 0426e9d Compare September 16, 2025 16:35
Copy link
Member

@suhaibmujahid suhaibmujahid left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Thank you!

@suhaibmujahid suhaibmujahid merged commit ae70593 into mozilla:master Sep 17, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants