Admin Support PR review tracking issues in netwrix/docs are triggering codeowner team mentions and product label application via the issue labeler workflow.
What's happening
When auto-create-pr-tracking-issues.yml creates a tracking issue for an admin PR review, claude-issue-labeler.yml fires on issue open. Step 4 reads the CODEOWNERS for all files changed in the linked PR and applies those product labels + notifies the corresponding codeowner teams on the tracking issue. This is incorrect — admin tracking issues are internal workflow artifacts, not content issues for product teams to act on.
Example
Issue #1035 (admin review of training PR #1034) received labels 1secure, access-analyzer, identity-manager, pingcastle, AI:docs, AI:site and triggered codeowner notifications to all four product teams — none of whom needed to be involved.
Current fix (kb/review)
Step 4 already has an early exit when kb/review label is present (added in PR #945, tracked in netwrix-corp/data-export-staging#49). Admin Support tracking issues need the same treatment.
Fix needed
In claude-issue-labeler.yml Step 4, add an early exit condition for Admin Support tracking issues. Options:
- Check for an
admin label (requires auto-create-pr-tracking-issues.yml to set it on the admin path)
- Check if issue title matches the pattern
Admin: PR review —
Recommended: title-pattern check is simpler and requires no changes to Workflow 1. Add alongside the existing kb/review check:
if echo "$ISSUE_TITLE" | grep -q "^Admin: PR review"; then
echo "Admin Support tracking issue — skipping codeowner notification"
exit 0
fi
Also evaluate whether Step 3 (label assignment) should similarly skip admin tracking issues to avoid applying product labels at all.
Admin Support PR review tracking issues in
netwrix/docsare triggering codeowner team mentions and product label application via the issue labeler workflow.What's happening
When
auto-create-pr-tracking-issues.ymlcreates a tracking issue for an admin PR review,claude-issue-labeler.ymlfires on issue open. Step 4 reads the CODEOWNERS for all files changed in the linked PR and applies those product labels + notifies the corresponding codeowner teams on the tracking issue. This is incorrect — admin tracking issues are internal workflow artifacts, not content issues for product teams to act on.Example
Issue #1035 (admin review of training PR #1034) received labels
1secure,access-analyzer,identity-manager,pingcastle,AI:docs,AI:siteand triggered codeowner notifications to all four product teams — none of whom needed to be involved.Current fix (kb/review)
Step 4 already has an early exit when
kb/reviewlabel is present (added in PR #945, tracked innetwrix-corp/data-export-staging#49). Admin Support tracking issues need the same treatment.Fix needed
In
claude-issue-labeler.ymlStep 4, add an early exit condition for Admin Support tracking issues. Options:adminlabel (requiresauto-create-pr-tracking-issues.ymlto set it on the admin path)Admin: PR review —Recommended: title-pattern check is simpler and requires no changes to Workflow 1. Add alongside the existing
kb/reviewcheck:Also evaluate whether Step 3 (label assignment) should similarly skip admin tracking issues to avoid applying product labels at all.