The behavior of the changing page button for the lists(alarm definitions, alarms and notifications) should be improved.
Bug #1486508 reported by
Sayako Kondo
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Monasca |
Fix Released
|
Undecided
|
Shinya Kawabata |
Bug Description
At this moment, the changing page button of Alarm Definitions/
- If there are 10 or more items(Alarm Definitions or Alarms or Notifications) in the list,
the "Next Page" button is displayed.
- We can see next page when clicking the "Next Page" button.
The "Previous Page" button doesn't exist. So we cannot back to the previous page.
The "Previous Page" button should be added.
Additionally, the "Next Page" button appears when the list have just 10 items.
So if clicking the "Next Page" button, there are no items in next page.
The "Next Page" button should be appeared when the list have 11 or more items.
Changed in monasca: | |
status: | New → Triaged |
Changed in monasca: | |
assignee: | nobody → Shinya Kawabata (s-kawabata) |
Changed in monasca: | |
status: | Fix Released → In Progress |
To post a comment you must log in.
I think this is pagination problem. core.paginator but it doesn't use normally. core.paginator and original implementaiton.
Current implementation using django.
It's hybrid that django.
So I think adopting django. core.paginator normally is to solve the problem easily. Alarms/ Notifications) .
But this way has a problem.
Whenever press the next(previous) page button,
It loads the whole Items(Alarm Definitions/
So if items are many, performance problem will occur.
What do you think?