Clear the severity for bugs with old-style severity values #1639
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
marco-c
reviewed
Sep 7, 2022
This comment was marked as outdated.
This comment was marked as outdated.
|
New numbers after 4f49920:
Updated dry-runClick to expand the dry-run output!The following bugs were using the old severity system. The severity now is dropped to let teams retriage them:
|
Numbers after this commit: | Team Name | Number of bugs | | ----------------------- | :------------: | | Frontend | 250 | | Security Engineering | 13 | | Layout | 76 | | Desktop Integrations | 12 | | DOM Core | 123 | | Other | 25 | | Networking | 33 | | OS Integration | 48 | | GFX | 103 | | Crypto | 58 | | Low Level | 9 | | DevTools | 5 | | Credential Management | 8 | | Search and New Tab | 58 | | Accessibility | 16 | | DOM LWS | 12 | | Performance | 4 | | Services | 5 | | Javascript | 32 | | Web Extensions | 6 | | Media | 22 | | Privacy Engineering | 9 | | Mobile | 10 | | Mozilla | 5 | | CI and Quality Tools | 14 | | RelEng | 2 | | Pocket and User Journey | 1 |
marco-c
added
the
to-be-announced
marco-c
approved these changes
Sep 9, 2022
This was referenced Sep 13, 2022
suhaibmujahid
added
announced
and removed
to-be-announced
|
Hi @suhaibmujahid -- do you have bugzilla search links (or bug number lists) that you could share for the per-component bug categories discussed above? I've started several times (but haven't yet finished) going through the list of "old-style-severity" Layout bugs, to reduce the noise in the migrated bugs here. I've lost the link that I was initially using for this, and in any case it'd be good to be sure I'm looking at the same list that you're using. If possible, I'd like to capture a bugzilla bug-list of the bugs in question, so that I can easily find & triage them when time allows (even after their severity has been auto-migrated). (I see you linked some of the bugs in the initial comment here, but that's capped to 10 per component I think.) |
|
@dholbert, here is the bugzilla search query for bugs that need to be retriaged: https://mzl.la/3eW4F69 Click to expand the list of bugs per team (without the 10 bugs per team limit)!
The list and query above do not cover the cases where the severity will be automatically converted. For that, @dklawren posted the queries here: https://bugzilla.mozilla.org/show_bug.cgi?id=1789259#c13 In summary, the mapping will be as follows:
The migration will affect open bugs only. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Resolves #1484
Dry-run
Click to expand the dry-run output!
The following bugs were using the old severity system. The severity now is dropped to let teams retriage them:
Statistics
The number of bugs per team (will be limited to 10 per week):
Checklist
to-be-announcedtag added if this is worth announcing