Bug: Installed version not appearing on extension card and it's not the selected version on the slide-in panel

[aalves08]

Setup

• Rancher version: 2.14.0
• Rancher UI Extensions: any
• Browser type & version: any

Describe the bug

• Install Kubewarden 4.1.0

• If we look at the "installed" card for Kubewarden, it should be showing the installed version and not the latest (proposed solution: should show 4.1.0 and not 4.1.1)
• When we open the slide-in panel, the selected version should be the installed one and not the latest (proposed solution: should have selected 4.1.0 and not 4.1.1)

To Reproduce

Install Kubewarden 4.1.0. Check card and slide-in panel

Result

As per above bug description

Expected Result

As per above bug description

Screenshots

Additional context

[github-actions]

🤖 Issue grooming analysis

This bug report is well-groomed and ready for triage. Here's the analysis against the checklist:

✅ Clear Problem Statement
The title and description clearly describe the bug: after installing Kubewarden 4.1.0, the extension card shows the latest version (4.1.1) rather than the installed version, and the slide-in panel also defaults to the latest rather than the installed version.

✅ Acceptance Criteria
Clearly defined: the installed version (4.1.0) should be displayed on the extension card, and it should be the pre-selected version in the slide-in panel.

✅ Technical Details
Screenshots are attached showing both the card and the slide-in panel. The specific extension (Kubewarden), affected versions (installed: 4.1.0, incorrectly shown: 4.1.1), and Rancher version (2.14.0) are identified.

✅ Reproducibility
Clear steps: install Kubewarden 4.1.0, then check the card and the slide-in panel. Expected vs. actual behavior is described.

This analysis was generated automatically based on the repository's grooming checklist.

Generated by Daily Issue Grooming · ◷

[aalves08]

Created issue as requested per @nwmac

@oboc-sts do you agree with the proposed solutions? wanted validation from UX

[oboc-sts]

All cards for charts, extensions and cluster tools work the same:

• we show the latest version available on the card
• if the chart / extension / etc.. is installed:
  • we show the installed flag on the card (top right, green checkmark)
    • when hovering the flag, a tooltip appears: "Installed (version no)" or "Installed (multiple)" if there are multiple instances installed
  • if the installed version is not the same as the latest available version, we show the "upgradeable" flag on the card
    • this is to let you know (and filter by it) there's a newer version available and you should upgrade the chart / extension / etc
      • ... which is why the selected by default version is the latest one when you go to a chart / extension / etc details AND the primary CTA is to UPGRADE

Long story short:

• this is NOT a bug, it's by design
• changing this behaviour has wider implications, including but not limited to:
  • for consistency reasons, the chart cards and the cluster tool cards will also be impacted
  • the flows of seeing the details of a chart / extension / etc... will be impacted, increasing the interaction cost = you'll have to find the latest version available on the chart details page / extension details panel / etc... click on it, and then click the "Upgrade..." button
  • ...
• everything I've briefly written here has been thoroughly explained and demo'ed countless times in both written and verbal form - for example:
  • https://confluence.suse.com/spaces/CU/pages/1906933996/Extensions+and+Cluster+Tools+Update
  • https://confluence.suse.com/spaces/CU/pages/1906934058/Chart+flows+-+Upgrade+Edit+Downgrade
  • demos and more...

... IF there is a solid argument agains the initial mechanics and functional design, please set up a call with all the parties involved and let's have a proper chat about everything related to these cards @nwmac

[gaktive]

Pushing out of 2.15.0 in light of current "working as designed". If we need to re-evaluate, we're running out of time.