Skip to content
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

[no_severity_nag] Exclude security bugs when nagging triage owner #2536

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

benjaminmah
Copy link
Contributor

Resolves #2505.

Excludes any bugs with a security keyword to avoid nagging the triage owner.

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

@benjaminmah
Copy link
Contributor Author

Would it make sense to apply this filter to the other rules that nag the triage owner as well? (p1_no_activity.py, p1_no_assignee.py, etc.)

@marco-c
Copy link
Contributor

marco-c commented Nov 6, 2024

Would it make sense to apply this filter to the other rules that nag the triage owner as well? (p1_no_activity.py, p1_no_assignee.py, etc.)

Which other rules do it? We could ask @mozfreddyb for each of them.

@benjaminmah
Copy link
Contributor Author

Which other rules do it? We could ask @mozfreddyb for each of them.

Looking through the BugBot Wiki, the following are rules that NAG the triage owner:

There are other rules that NEEDINFO the triage owner, however.

@@ -73,6 +74,8 @@ def handle_bug(self, bug, data):
# check if the product::component is in the list
utils.check_product_component(self.components_skiplist, bug)
or utils.get_last_no_bot_comment_date(bug) > self.activity_date
or any(keyword in SECURITY_KEYWORDS for keyword in bug["keywords"])
or bug["groups"]
Copy link
Contributor

Choose a reason for hiding this comment

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

Let's do any("security" in group for group in bug["groups"]) so we only exclude security bugs and not bugs that are confidential

Comment on lines 77 to 78
or any(keyword in SECURITY_KEYWORDS for keyword in bug["keywords"])
or bug["groups"]
Copy link
Contributor

Choose a reason for hiding this comment

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

Maybe we could have this in the query directly

Copy link
Contributor Author

Choose a reason for hiding this comment

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

How does this look? 55a1b1f

Copy link
Member

Choose a reason for hiding this comment

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

You could instead add it as a configuration, and it will be added to the query:

"sec": false

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Can you elaborate on this, I'm a little confused on what you mean. Do you mean adding a new "sec": false configuration under no_severity_nag and then using that as a condition on whether or not to include the security bugs in the params?

Comment on lines +121 to +123
"f34": "bug_group",
"o34": "substring",
"v34": "security",
Copy link
Member

Choose a reason for hiding this comment

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

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.

Stop emailing triage owners about security bugs when they cannot take the next action
3 participants