Pro dashboard shows duplicates

[cpaelzer]

Summary

When looking at the pro dashboard I see a contract listed twice.

Steps to reproduce the behavior

1. Go to https://ubuntu.com/pro/dashboard
2. Log on with an account that can see our teams contracts (I'm logged in with the email I have in the directory)
3. See on the left panel listing the contracts. We have a bunch of team use contracts and tokens here for testing
4. See that the contract "server-team-ua-client-ci-uaa" is listed twice (I checked it also is the same token, so it really is a duplicate, not just the same name by accident)

Expected behavior

Every contract to show up exactly once

BTW I also consider it a bug that my personal free account is not shown at all here and only in SF, but that is a different topic. Yet maybe that is part of the riddle why we see a duplicate - hence I mention it.

Screenshot

Browser/device details

• Device: Lenovo Thinkpad T580
• OS: Ubuntu 24.04 Noble
• Browser Chrome
• Version 126.0.6478.114 (Official Build) (64-bit)

[orndorffgrant]

I see the same duplicate from my account.

[mtruj013]

@cpaelzer @orndorffgrant thanks for reporting!

@minkyngkm @abhigyanghosh30 could you take a look please?

[abhigyanghosh30]

@minkyngkm seems to be an error in the frontend for not showing the free subscription. Also the duplicated listing is a problem from build_user_subscriptions function

[alnvdl-work]

I don't think there is a bug here. There is a fundamental difference between the Pro backend representation of contracts and the representation in the Pro dashboard. Due to UX decisions made in the past, the Pro dashboard shows each contract item, instead of grouping them by contract (or "Pro token").

The reason @cpaelzer is seeing two entries for server-team-ua-client-ci-uaa is because there are indeed two contract items in that contract; there should be only one, but since the creation process of these special entitlements is manual, someone likely made a mistake when creating or updating it. This is completely harmless though.

As for why the free token is not displayed, that's a separate issue; IIRC, our internal UX teams are discussing a better solution to this.