UI: Subnets page pagination - a group can be displayed on two pages

Bug #1996500 reported by Alberto Donato
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
Low
Unassigned
maas-ui
Fix Committed
Low
Jones Ogolo

Bug Description

I have 17 fabrics listed on the subnets page.

The UI shows 2 pages, but the second page only contains one of the fabrics already listed on the first page.

Tags: ui
Revision history for this message
Alberto Donato (ack) wrote :
tags: added: ui
Revision history for this message
Alberto Donato (ack) wrote :
Revision history for this message
Adam Collard (adam-collard) wrote :

Alberto, the second page in your example is the IPv6 subnet on fabric-35 and doesn't appear on page 1?

Changed in maas:
status: New → Incomplete
Revision history for this message
Alberto Donato (ack) wrote :

Oh, I see, despite the grouping the pagination happens on the subnets.
I still find it a bit confusing, since this way you don't see all subnets for a fabric together, though.

Alberto Donato (ack)
Changed in maas:
status: Incomplete → New
summary: - Subnets page pagination duplicate entries
+ UI: Subnets page pagination duplicate entries
Revision history for this message
Thorsten Merten (thorsten-merten) wrote :

This is coming as separate items from the backend and thus paginated. There is manual grouping done on the frontend which does not work across pages.

summary: - UI: Subnets page pagination duplicate entries
+ UI: Subnets page pagination - a group can be displayed on two pages
Revision history for this message
Thorsten Merten (thorsten-merten) wrote :

If we want to fix this, it seems like we need to change pagination, thus triaging for backend as well.

Changed in maas-ui:
milestone: none → 3.4.0
status: New → Triaged
no longer affects: maas-ui/3.4
Changed in maas-ui:
importance: Undecided → Low
Changed in maas:
status: New → Triaged
importance: Undecided → Low
milestone: none → 3.4.0
Alberto Donato (ack)
Changed in maas:
milestone: 3.4.0 → 3.4.x
Revision history for this message
Peter Makowski (petermakowski) wrote :

Adding a link to a conversation that may be helpful in resolving this: https://github.com/canonical/maas-ui/pull/5149#discussion_r1326902079

Changed in maas-ui:
assignee: nobody → Jones Ogolo (jonesogolo)
Jones Ogolo (jonesogolo)
Changed in maas-ui:
status: Triaged → Fix Committed
Revision history for this message
Jones Ogolo (jonesogolo) wrote :

We implemented a new design that should mitigate this problem, please feel free to reopen and provide more context if this is not the case

Revision history for this message
Thorsten Merten (thorsten-merten) wrote :

As the front-end is showing the information more consistently now, there should be no need to change anything on the API level.

Changed in maas:
status: Triaged → Fix Committed
Changed in maas:
milestone: 3.4.x → 3.4.1
Changed in maas:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.