[DEFECT] Publishing Queue copy icon polish

Problem Statement

QA of the Angular dot-publishing-queue portlet in the Modernization initiative surfaced two small polish defects on the copy-bundle-id icon:

• The copy icon rendered next to each bundle Id in the Publishing Queue list is visually small and difficult to click accurately.
• After clicking the icon, its hover/active state (tooltip + highlight) sometimes remains visible after the cursor leaves the icon — the tooltip stays pinned to that row until the user hovers a different element or scrolls.

Environment: Chrome, latest main.

Steps to Reproduce

1. Log in as admin and open the Publishing Queue portlet.
2. Locate any bundle row in the list.
3. Observe the size and click target of the copy icon next to the bundle Id — it is small and easy to miss.
4. Click the copy icon.
5. Move the cursor off the icon (without scrolling and without clicking another element).
6. Observe that the tooltip / active highlight sometimes remains visible on the row instead of clearing.

Acceptance Criteria

• Copy icon click target is enlarged (icon and/or padded hit area) so it is comfortable to click at standard admin zoom levels.
• After clicking the copy icon, the tooltip and any active/hover highlight clear as soon as the cursor leaves the icon (no stuck tooltip).
• Tooltip continues to appear on hover and disappears on mouseleave / blur consistently across all rows.
• Copy-to-clipboard still succeeds and the existing "copied" feedback (if any) still triggers.

Design Polish

Design review of the same list requested three further changes:

• Items column — the asset count renders as a passive count chip, so it does not read as clickable. It should be a # items text link, underlined on hover, in the row's normal text color.
• Add Bundle button — relabelled to Bundles (#), carrying the number of existing bundles on the button itself.
• Select Bundle menu row — repeats the same count next to its label, so the menu and the button agree.

Acceptance criteria:

• The Items column renders # items as a text link that underlines on hover and opens the bundle contents on click.
• A bundle with no items renders as plain text — there is nothing to open.
• The toolbar button reads Bundles (#) with the count of existing bundles, and stays a plain Bundles while the count is unavailable rather than showing (0).
• The Select Bundle menu row shows the same count as the button.
• The count reflects unsent (draft) bundles. It is scoped per user by the backend: a regular user sees only their own drafts, a CMS Administrator sees every user's — two accounts showing different numbers is expected.

Status Chip Colour Defect

Found while implementing the design polish above, and fixed in the same change.

The status chips mapped in-flight and warning statuses to a warning severity, but PrimeNG derives its class as p-tag-{severity} and only accepts warn. The mismatch produced no p-tag-* class at all, so those chips fell back to the base solid primary fill and rendered as blue pills that look like buttons.

Five statuses were affected: Bundling, Sending, Publishing, Received and Success (warn). No status changes its meaning or bucket — only the class name is corrected, so all five now render as the amber pill the theme already defines.

• Bundling, Sending, Publishing, Received and Success (warn) render as amber pills, not solid blue.
• Success, Scheduled/Waiting and the failure statuses are unchanged (green, blue and red respectively).

dotCMS Version

Latest from main branch.

Severity

Low - Minor issue or cosmetic

Links

NA

---

Note: the categories delete cascade behavior originally reported alongside this ticket is now tracked separately in #36906.