MCM-22 — Enforce the 50-Resource Cap in the Bulk Tag Update UI
Prevent selecting more than 50 resources for a single tag update, matching the limit already enforced by the API.
MCM-22 — Enforce the 50-Resource Cap in the Bulk Tag Update UI
← Back to Custom Tag Improvements overview
As a Platform User,
I want the tag-update screen to stop me from selecting more than 50 resources,
so that I find out about the limit before I try to apply tags, not after a failed request.
Acceptance Criteria
- The resource-selection UI used for bulk tag updates (the Custom Tag Detail page's Resources tab) prevents selecting a 51st resource once 50 are already selected.
- "Select all" on a page/result set that would exceed 50 resources selects only the first 50 and informs the user why, rather than silently selecting everything or failing at submit time.
- The selection count is visibly shown against the 50 maximum (e.g. "37 / 50 selected") while selecting.
- Submitting with 50 or fewer resources behaves exactly as it does today (no change to the underlying bulk tag-update call or its per-resource result handling).
- This is a UI-side guard only — the existing server-side 50-resource limit (enforced by the tagging system) is unchanged and remains the authoritative enforcement point.
Technical Design
This closes a gap between an already-enforced backend rule and an unaware frontend — no new business rule is introduced, only earlier, clearer enforcement of the existing one. The bulk tag-update resource-selection screen gains a selection-count guard around its row/select-all checkboxes, disabling further selection once 50 is reached and clamping "select all" to the first 50 matching resources. No backend change is needed: the tag-update request already rejects more than 50 resources — this story only stops the UI from constructing a request that would hit that rejection.
UI / Frontend Changes
- Custom Tag Detail page's Resources tab: row checkboxes disable once 50 resources are selected.
- Live selection counter shown against the cap (e.g. "37 / 50 selected") near the selection controls.
- "Select all" clamps to the first 50 matches and shows an inline message explaining why the rest weren't selected.
- No change to the submit button or post-submit result handling — only the selection controls above the existing bulk-update action.
MCM-21 — Reconcile Tag Values Outside the Allowed List
Surface tag values that exist on resources but aren't in a tag's allowed list, and let an Admin migrate or allow-list them.
MCM-25 — Add, Update, and Delete Tags from the Resource Detail View
Add, edit, or remove a resource's tags directly from its own detail page, not only from a Custom Tag's Resources tab.