Filter out dummy bugs from bug counts

[jluhrsen]

Skip bugs with "(dummy bug)" in the summary when calculating developer workloads and team statistics.

Summary by CodeRabbit

• Bug Fixes
  • Dummy Jira bugs are now excluded from bug statistics and attribution.
  • Issues marked as “(dummy bug)” in their summary are skipped automatically, preventing them from affecting reported counts.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 5ffa4088-1397-49f0-af90-4be737eaa6eb

📥 Commits

Reviewing files that changed from the base of the PR and between 0b53ac3 and 04f8579.

📒 Files selected for processing (1)

• jira-scripts/network_bugs_overview

---

Walkthrough

process_jira_bugs now skips Jira issues whose summary contains "(dummy bug)" case-insensitively before they are counted.

Changes

Dummy bug filtering

Layer / File(s)	Summary
Summary filter guard jira-scripts/network_bugs_overview	Adds a case-insensitive summary check that excludes matching Jira bugs from the accounting flow.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 15

✅ Passed checks (15 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly matches the main change: excluding dummy bugs from bug count calculations.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names	✅ Passed	No test files or Ginkgo titles are present/modified; the PR only changes a Jira script, so the stability check is not applicable.
Test Structure And Quality	✅ Passed	PR only changes jira-scripts/network_bugs_overview; no Ginkgo test files or test code were added/modified, so the test-quality checklist is not applicable.
Microshift Test Compatibility	✅ Passed	PR only changes a Python Jira reporting script; no new Ginkgo e2e tests or MicroShift-sensitive APIs were added.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	No new Ginkgo/e2e tests were added; the PR only changes jira-scripts/network_bugs_overview to skip dummy bugs.
Topology-Aware Scheduling Compatibility	✅ Passed	Only jira-scripts/network_bugs_overview changed; it filters dummy Jira bugs and adds no manifests, controllers, or scheduling constraints.
Ote Binary Stdout Contract	✅ Passed	PASS: The only code change is a summary check in process_jira_bugs; no new stdout writes were added to main/init/TestMain/setup paths.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	No new Ginkgo e2e tests were added; this PR only tweaks a Python Jira script, so IPv4/external-connectivity test checks are not applicable.
No-Weak-Crypto	✅ Passed	PR only adds a dummy-bug summary filter in process_jira_bugs; no weak-cipher, ECB, custom-crypto, or secret-comparison code appears in the changed file.
Container-Privileges	✅ Passed	PR only changes jira-scripts/network_bugs_overview; no container/K8s manifests were modified and the script has no privilege settings.
No-Sensitive-Data-In-Logs	✅ Passed	The PR only adds a dummy-bug skip in process_jira_bugs; it introduces no new logging or sensitive-field output.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands.}

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: jluhrsen
Once this PR has been reviewed and has the lgtm label, please assign knobunc for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

@jluhrsen: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.