remove resource counts from monitor deletion modal

[adamsachs]

Ticket ENG-1192 followup

Description Of Changes

Per discussion referenced in the jira comment here, these resources counts ultimately just add confusion for the end user, so we're deciding to hide it.

Code Changes

• don't show resource counts, but add explanatory comment

Steps to Confirm

1. new modal text looks like

Pre-Merge Checklist

• Issue requirements met
• All CI pipelines succeeded
• CHANGELOG.md updated
  • Add a db-migration This indicates that a change includes a database migration label to the entry if your change includes a DB migration
  • Add a high-risk This issue suggests changes that have a high-probability of breaking existing code label to the entry if your change includes a high-risk change (i.e. potential for performance impact or unexpected regression) that should be flagged
  • Updates unreleased work already in Changelog, no new entry necessary
• UX feedback:
  • All UX related changes have been reviewed by a designer
  • No UX review needed
• Followup issues:
  • Followup issues created
  • No followup issues
• Database migrations:
  • Ensure that your downrev is up to date with the latest revision on main
  • Ensure that your downgrade() migration is correct and works
    • If a downgrade migration is not possible for this change, please call this out in the PR description!
  • No migrations
• Documentation:
  • Documentation complete, PR opened in fidesdocs
  • Documentation issue created in fidesdocs
  • If there are any new client scopes created as part of the pull request, remember to update public-facing documentation that references our scope registry
  • No documentation updates required

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
fides-plus-nightly	Ready	Preview, Comment	Feb 13, 2026 5:38pm

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
fides-privacy-center	Ignored		Feb 13, 2026 5:38pm

[greptile-apps]

Greptile Overview

Greptile Summary

Removed the staged_resource_count display from the monitor deletion modal to eliminate user confusion. The count was misleading because it didn't accurately represent all resources being deleted (some approved/ignored staged resources were also being deleted but not included in the count).

Key changes:

• Removed the conditional block showing pending resource count
• Added a comprehensive comment explaining why staged_resource_count was intentionally omitted
• Added clearer messaging: "All action center resources discovered by this monitor will be permanently deleted"
• Backend API still exposes the count for direct inspection if needed

The change improves UX by providing clear, accurate information about deletion impact without potentially confusing numeric details.

Confidence Score: 5/5

• This PR is safe to merge with minimal risk
• The change is a simple UI improvement that removes a confusing metric from a modal. It includes a thorough explanatory comment, improves user messaging, and doesn't affect any core functionality or data operations. The backend API still exposes the data if needed for other purposes.
• No files require special attention

Important Files Changed

Filename	Overview
clients/admin-ui/src/features/integrations/configure-monitor/MonitorConfigActionsCell.tsx	Removed confusing resource count display from monitor deletion modal, added clear explanatory comment and improved messaging about what will be deleted

_{Last reviewed commit: 3864538}

[greptile-apps]

_{1 file reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}

[nrxsmith]

👍