Version Naming Convention needs updating/fixing

[emarion1]

What happened?

The program Hygiene Report under Releases->Reports (https://team-tracker.apps.int.spoke.prod.us-west-2.aws.paas.redhat.com/#/releases/reports?tab=outcomes&report=program-hygiene) has incorrect and obsolete in the high level filter panel.

Expected behavior

It should use current version naming conventions

Steps to reproduce

No response

Affected area

Other

Diagnostics

[claude]

Claude finished @emarion1's task in 10m 12s —— View job • claude/issue-1259-20260721-1534 • Create PR ➔

---

Fixed version naming in Program Hygiene Report

• Gather context and understand the issue
• Find and fix the root cause in the program-report endpoint
• Add fallback display name formatting for unregistered versions
• Add tests (8 new unit tests)
• Run tests and lint
• Push changes and create PR

Root cause: The program-report endpoint (modules/releases/server/hygiene/routes.js:612-628) matched hygiene file version IDs against registry entries using only id and displayName. But hygiene data files can be stored with Jira fixVersion-style names (e.g., RHAII-3.5.EA1, rhoai-3.5.z.EA2). These values exist in the registry's fixVersions array but weren't checked, so raw file names were displayed instead of proper display names.

Changes:

1. Extended registry matching in the program-report endpoint to also check the fixVersions array — versions like RHOAI-2.14 now resolve to display name RHOAI 2.14
2. Added formatVersionId() fallback that converts raw IDs to readable names (e.g., rhoai-3.5.EA1 → RHOAI 3.5.EA1) when no registry match exists
3. Added 8 unit tests covering all matching paths (id, displayName, fixVersions, fallback formatting)

|

[accorvin]

Working on a fix for this.

[accorvin]

This should be resolved on the next deploy.