Skip to content

NO-JIRA: Refresh list of team members#176

Open
maayanf24 wants to merge 2 commits into
openshift:mainfrom
maayanf24:update-members
Open

NO-JIRA: Refresh list of team members#176
maayanf24 wants to merge 2 commits into
openshift:mainfrom
maayanf24:update-members

Conversation

@maayanf24
Copy link
Copy Markdown

@maayanf24 maayanf24 commented May 5, 2026

Refresh members list, and replace bbennett with
core-networking-bot as the new default assignee

Summary by CodeRabbit

  • Chores
    • Changed the default Jira assignee to core-networking-bot and updated unassigned-bug and workload assignment logic accordingly.
    • Updated team/developer allowlist to add sseethar, tasing, shbehera, raprosa and removed deprecated entries.
    • Refreshed account and GitHub-to-Jira user mappings to reflect current team mappings and removed outdated mappings.

Refresh members list, and replace bbennett with
core-networking-bot as the new default assignee

Signed-off-by: Maayan Friedman <maafried@redhat.com>
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 5, 2026

Walkthrough

The PR changes the default Jira assignee from bbennett to core-networking-bot in the network bugs overview script and updates related account mappings, GitHub→Jira user mappings, RH developer allowlist, bug-query assignee usage, skip logic, and summary table generation to include core-networking-bot.

Changes

Default Assignee & Reporting Update

Layer / File(s) Summary
Configuration Constants
jira-scripts/network_bugs_overview (lines ~25, 43–49, 66–75, 92–96)
DEFAULT_JIRA_ASSIGNEE changed to "core-networking-bot". ACCOUNT_ID_TO_USERNAME updated to add core-networking-bot-related account IDs, remove deprecated Ben Bennett and other entries. RH_DEVELOPERS updated to add sseethar, tasing, shbehera, raprosa and remove pliurh, rravaiol. GITHUB_TO_JIRA_USERS mappings adjusted/added (taanyas→tasing, shreyasbe→shbehera, raphaelvrosa→raprosa, tssurya→sseethar) and deprecated mappings removed.
Query Layer
jira-scripts/network_bugs_overview (around line ~537)
Unassigned-bug query and any hardcoded assignee mail now derive the assignee mail from DEFAULT_JIRA_ASSIGNEE (uses core-networking-bot@redhat.com instead of bbennett@redhat.com).
Processing Logic
jira-scripts/network_bugs_overview (around lines ~820–847, ~1056–1069)
Skip/filter logic for default assignee now uses computed default_assignee_mail / core_networking_bot_assignee_mail. Extraction of core_networking_bot_data from developers added.
Reporting Output
jira-scripts/network_bugs_overview (around lines ~1110–1143)
Summary table gains a dedicated core_networking_bot_line, inserted into output lines and included in TOTAL aggregation; total calculation updated to include the new line and preserve separators.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

🚥 Pre-merge checks | ✅ 12
✅ Passed checks (12 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'Refresh list of team members' directly corresponds to the main change: updating developer mappings and team member associations while replacing the default assignee.
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 PR modifies Python scripts and config files, not Go code. No Ginkgo test files exist in the repository. The Ginkgo test name check is not applicable.
Test Structure And Quality ✅ Passed This PR contains no Ginkgo test code. The check for test structure quality is not applicable as the PR only modifies Python scripts, shell scripts, documentation, and build files.
Microshift Test Compatibility ✅ Passed PR adds no Ginkgo e2e tests. Repository contains only Python/Bash scripts and a build tools Go file. MicroShift compatibility check only applies to new Ginkgo tests, which are not present in this PR.
Single Node Openshift (Sno) Test Compatibility ✅ Passed Custom check is not applicable. This PR modifies only a Python Jira script, not Ginkgo e2e tests. The check applies only when new Ginkgo tests are added.
Topology-Aware Scheduling Compatibility ✅ Passed PR modifies only a Jira automation script for team member management. Check applies exclusively to deployment manifests, operator code, and controllers—none of which are modified here.
Ote Binary Stdout Contract ✅ Passed Check not applicable. PR modifies only Python utility script (jira-scripts/network_bugs_overview). OTE Binary Stdout Contract targets Go test binaries, not present here.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed This PR modifies a Python script for Jira issue management and does not add any Ginkgo e2e tests. The custom check for IPv6/disconnected network test compatibility is not applicable.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

  • Generate code and open pull requests
  • Plan features and break down work
  • Investigate incidents and troubleshoot customer tickets together
  • Automate recurring tasks and respond to alerts with triggers
  • Summarize progress and report instantly

Built for teams:

  • Shared memory across your entire org—no repeating context
  • Per-thread sandboxes to safely plan and execute work
  • Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@maayanf24 maayanf24 changed the title Refresh list of team members NO-JIRA: Refresh list of team members May 5, 2026
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label May 5, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@maayanf24: This pull request explicitly references no jira issue.

Details

In response to this:

Refresh members list, and replace bbennett with
core-networking-bot as the new default assignee

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci Bot requested review from jcaamano and kyrtapz May 5, 2026 06:24
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 5, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: maayanf24
Once this PR has been reviewed and has the lgtm label, please assign arghosh93 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:

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

@openshift-ci openshift-ci Bot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label May 5, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 5, 2026

Hi @maayanf24. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

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

🧹 Nitpick comments (1)
jira-scripts/network_bugs_overview (1)

531-539: ⚡ Quick win

Use get_username_and_usermail_from_assignee(DEFAULT_JIRA_ASSIGNEE) instead of hardcoding the email in the JQL query.

"core-networking-bot@redhat.com" is inlined directly into the query string, while every other place in this file that needs the default assignee's email derives it from the helper (e.g. Lines 249–254, 259–264, 820). If DEFAULT_JIRA_ASSIGNEE is renamed again, this string will silently fall out of sync and the query will stop returning the right bugs.

♻️ Proposed refactor
 def retrieve_unassigned_jira_bugs():
     clients = init_clients(jira_=True)
     SDN_OCPBUGS_FILTER = 'project = OCPBUGS AND component in ("Networking / openshift-sdn", "Networking / ovn-kubernetes", "Networking / cloud-network-config-controller", "Networking / ingress-node-firewall", "Networking / cluster-network-operator", "Networking / network-tools")'
+    _, default_assignee_mail = get_username_and_usermail_from_assignee(DEFAULT_JIRA_ASSIGNEE)
     query = (
         f'(({SDN_OCPBUGS_FILTER}) OR project = RHOCPPRIO AND component in ("networking/sdn") '
         "OR project = CORENET AND issuetype = Bug) AND resolution = Unresolved AND ((project = OCPBUGSM OR project = "
-        'OCPBUGS) AND assignee = "core-networking-bot@redhat.com" OR project = RHOCPPRIO AND assignee in ('
+        f'OCPBUGS) AND assignee = "{default_assignee_mail}" OR project = RHOCPPRIO AND assignee in ('
         '"anbhat@redhat.com", "zshi@redhat.com") OR assignee is EMPTY) ORDER BY Rank DESC'
     )
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@jira-scripts/network_bugs_overview` around lines 531 - 539, The JQL in
retrieve_unassigned_jira_bugs() hardcodes "core-networking-bot@redhat.com";
replace that literal with the default assignee email obtained from
get_username_and_usermail_from_assignee(DEFAULT_JIRA_ASSIGNEE) (use the returned
email value) so the query uses the canonical DEFAULT_JIRA_ASSIGNEE source;
update the query construction in retrieve_unassigned_jira_bugs() to interpolate
the helper's email instead of the hardcoded string.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@jira-scripts/network_bugs_overview`:
- Around line 531-539: The JQL in retrieve_unassigned_jira_bugs() hardcodes
"core-networking-bot@redhat.com"; replace that literal with the default assignee
email obtained from
get_username_and_usermail_from_assignee(DEFAULT_JIRA_ASSIGNEE) (use the returned
email value) so the query uses the canonical DEFAULT_JIRA_ASSIGNEE source;
update the query construction in retrieve_unassigned_jira_bugs() to interpolate
the helper's email instead of the hardcoded string.

ℹ️ Review info
⚙️ Run configuration

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

Review profile: CHILL

Plan: Enterprise

Run ID: 54b8851c-2fca-44bc-bb94-7715677bd96c

📥 Commits

Reviewing files that changed from the base of the PR and between 5da4bc2 and a94e8b7.

📒 Files selected for processing (1)
  • jira-scripts/network_bugs_overview

Comment thread jira-scripts/network_bugs_overview
Comment thread jira-scripts/network_bugs_overview Outdated
f'(({SDN_OCPBUGS_FILTER}) OR project = RHOCPPRIO AND component in ("networking/sdn") '
"OR project = CORENET AND issuetype = Bug) AND resolution = Unresolved AND ((project = OCPBUGSM OR project = "
'OCPBUGS) AND assignee = "bbennett@redhat.com" OR project = RHOCPPRIO AND assignee in ('
'OCPBUGS) AND assignee = "core-networking-bot@redhat.com" OR project = RHOCPPRIO AND assignee in ('
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

let's keep both ben bennett and core-net bot for the interim? so assignee is either of them gets printed...

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

I can add bennett email to this query, but the default assignee is used in several other queries as well. It will be easier to re-assign all of them instead of updating the script in multiple places for a temporary situation.

Comment thread jira-scripts/network_bugs_overview Outdated
Comment thread jira-scripts/network_bugs_overview
Signed-off-by: Maayan Friedman <maafried@redhat.com>
Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

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

🧹 Nitpick comments (1)
jira-scripts/network_bugs_overview (1)

538-541: ⚡ Quick win

Derive the default assignee email from DEFAULT_JIRA_ASSIGNEE and mark bbennett as transitional.

Two related observations on this query:

  1. The other unassigned-issue queries (e.g. get_query_for_unassigned_jira_stories_tracking_github_issues, get_query_for_unresolved_jira_stories_tracking_github_issues) compute the default-assignee email via get_username_and_usermail_from_assignee(DEFAULT_JIRA_ASSIGNEE). Hardcoding "core-networking-bot@redhat.com" here breaks that pattern, so a future change to DEFAULT_JIRA_ASSIGNEE will silently miss this query.
  2. "bbennett@redhat.com" was added per the interim-period discussion in the prior review, but there is no TODO/comment anchoring when it should be removed. Once existing OCPBUGS/OCPBUGSM tickets are reassigned, this entry will quietly start matching nothing useful.
♻️ Proposed change
 def retrieve_unassigned_jira_bugs():
     clients = init_clients(jira_=True)
     SDN_OCPBUGS_FILTER = 'project = OCPBUGS AND component in ("Networking / openshift-sdn", "Networking / ovn-kubernetes", "Networking / cloud-network-config-controller", "Networking / ingress-node-firewall", "Networking / cluster-network-operator", "Networking / network-tools")'
+    _, default_assignee_mail = get_username_and_usermail_from_assignee(DEFAULT_JIRA_ASSIGNEE)
+    # TODO: remove "bbennett@redhat.com" once all OCPBUGS/OCPBUGSM tickets are
+    # reassigned away from bbennett to core-networking-bot.
     query = (
         f'(({SDN_OCPBUGS_FILTER}) OR project = RHOCPPRIO AND component in ("networking/sdn")) '
-        " AND resolution = Unresolved AND ((project = OCPBUGSM OR project = "
-        'OCPBUGS) AND assignee in("core-networking-bot@redhat.com","bbennett@redhat.com") OR project = RHOCPPRIO AND assignee in ('
-        '"anbhat@redhat.com", "zshi@redhat.com") OR assignee is EMPTY) ORDER BY Rank DESC'
+        f' AND resolution = Unresolved AND ((project = OCPBUGSM OR project = OCPBUGS) '
+        f'AND assignee in ("{default_assignee_mail}", "bbennett@redhat.com") '
+        f'OR project = RHOCPPRIO AND assignee in ("anbhat@redhat.com", "zshi@redhat.com") '
+        f'OR assignee is EMPTY) ORDER BY Rank DESC'
     )
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@jira-scripts/network_bugs_overview` around lines 538 - 541, The query
hardcodes "core-networking-bot@redhat.com" and permanently includes
"bbennett@redhat.com"; update the clause to derive the default assignee email
using get_username_and_usermail_from_assignee(DEFAULT_JIRA_ASSIGNEE) (same
pattern used by get_query_for_unassigned_jira_stories_tracking_github_issues and
get_query_for_unresolved_jira_stories_tracking_github_issues) instead of the
literal core-networking-bot address, and mark "bbennett@redhat.com" as
transitional by adding a TODO comment with the removal condition/timestamp so
future reassignment won’t silently become stale; adjust the query string
construction around the assignee list in the same block that currently contains
SDN_OCPBUGS_FILTER and the OR project = RHOCPPRIO clause.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@jira-scripts/network_bugs_overview`:
- Around line 538-541: The query hardcodes "core-networking-bot@redhat.com" and
permanently includes "bbennett@redhat.com"; update the clause to derive the
default assignee email using
get_username_and_usermail_from_assignee(DEFAULT_JIRA_ASSIGNEE) (same pattern
used by get_query_for_unassigned_jira_stories_tracking_github_issues and
get_query_for_unresolved_jira_stories_tracking_github_issues) instead of the
literal core-networking-bot address, and mark "bbennett@redhat.com" as
transitional by adding a TODO comment with the removal condition/timestamp so
future reassignment won’t silently become stale; adjust the query string
construction around the assignee list in the same block that currently contains
SDN_OCPBUGS_FILTER and the OR project = RHOCPPRIO clause.

ℹ️ Review info
⚙️ Run configuration

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

Review profile: CHILL

Plan: Enterprise

Run ID: 36b97bff-635e-4fae-975d-63892c18d07e

📥 Commits

Reviewing files that changed from the base of the PR and between a94e8b7 and 1622972.

📒 Files selected for processing (1)
  • jira-scripts/network_bugs_overview

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants