-
Notifications
You must be signed in to change notification settings - Fork 67
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
Don't nag to set severity when severity is explicitly set to N/A
#2298
Comments
N/A is actually prohibited according to the triage rules: https://firefox-source-docs.mozilla.org/bug-mgmt/policies/triage-bugzilla.html#multiple-times-weekly. |
Aha, thanks. In the meantime (if it's complex to rip out N/A from bugzilla), it might be better to have BugBot swap to a custom message for this case. So no change in what-bugs-to-nag-about, but instead: when we're about to report a "The severity field is not set" nag, check whether we actually have (The bot could maybe even suggest that such bugs are often best reclassified as either Severity:S4 or Type:Task.) |
@dklawren wdyt? |
We have ~1640 bugs current marked with that severity so I cannot just delete without moving to something else. I can disable the value so that it cannot be used for new bugs or for bugs that are not currently set to it. Should I do that for now? |
In this context, the goal is to prevent setting the Severity to It would be useful to prevent having new ones. We could achieve that by disabling it from the UI for defect bugs only. Also, it would be great if we could add a post hook to the |
Totally doable. Please file a bug report for tracking and I will take a look. |
In https://bugzilla.mozilla.org/show_bug.cgi?id=1866692#c1 , the severity had been previously set to
N/A
but BugBot still nagged and said "The severity field is not set for this bug."Probably we should have BugBot consider
Severity:N/A
bugs as "triaged" & not needing further severity modifications. (Or if we want to explicitly prohibitN/A
severity, we should perhaps encode that in bugzilla somehow.)The text was updated successfully, but these errors were encountered: