MCM-25 — Add, Update, and Delete Tags from the Resource Detail View

← Back to Custom Tag Improvements overview

As a Platform User,
I want to add, change, or remove tags directly on a resource's own detail page,
so that I don't have to leave the resource I'm looking at and go find it again inside a specific Custom Tag's Resources tab just to manage its tags.

Assumption: "resource view" is interpreted here as the individual resource detail page, not the general resource list/table view — both are currently read-only for tags, but the request said "resource view" (singular), which reads more naturally as the single-resource page. Confirm if the list view was also intended.

Acceptance Criteria

• The resource detail page's tags view gains edit affordances for the resource's tags — add a new tag, change an existing tag's value, and remove a tag entirely — in addition to its current read-only searchable table.
• Removing a tag requires a confirmation step, since it's a destructive action with no undo.
• Adding or changing a tag value on this screen is subject to the same allowed-values policy as everywhere else — if the tag key has a configured allowed list, only those values (plus whatever MCM-21 allows) are selectable; free text is only allowed for tags with no configured allowed list. Removing a tag is not subject to the allowed-values policy — any tag on the resource can be removed.
• Saving an add, update, or delete from this screen goes through the same tag-update path as the Custom Tag Detail → Resources tab — a single-resource call, not a new tagging mechanism.
• A resource type that fails to tag shows the same failure clearly on this screen, not a silent no-op — this applies equally to add, update, and delete actions.

---

Technical Design

This reuses the same tagging path the bulk-update screen already uses — the only new work is UI on the resource detail page and constructing a single-resource add/update/delete request. The resource detail page's tags view extends from a read-only table to per-tag edit, remove, and add-new-tag actions, reusing the existing allowed-values-constrained value picker already used for bulk updates. No new tagging mechanism is introduced — the tagging service already accepts per-resource tag changes, so a single-resource add/update/delete is just a smaller instance of what bulk updates already do.

---

UI / Frontend Changes

• Resource detail page's tags view: adds per-tag edit and remove actions, plus an "add new tag" action, to the existing read-only table.
• Remove action requires a confirmation step before the tag is actually deleted.
• Reuses the existing allowed-values-constrained value picker already used for bulk tag updates, falling back to free text only when no allowed list is configured — this applies to add/update, not to delete.
• Save/cancel controls per edited row, or a small inline edit form, rather than a full-page edit mode.
• Error state: a failed single-resource tag change (add, update, or delete) shows a clear inline error on the tab instead of silently no-op'ing.
• Loading state on save while the tag change is in flight, consistent with the existing bulk-update screen's pattern.