Closed
Bug 1163160
Opened 10 years ago
Closed 9 years ago
release history revision count incorrect in UI
Categories
(Release Engineering Graveyard :: Applications: Balrog (backend), defect)
Release Engineering Graveyard
Applications: Balrog (backend)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: hwine, Assigned: njirap)
References
()
Details
Attachments
(2 files)
See attached screenshot - highest (current) release is 93, section header claims 100.
Comment 2•9 years ago
|
||
This affects rules and releases, updating summary. I also added some rule history to the sample data, so this bug can now be reproduced with a local docker image.
Summary: release history revision count incorrect in UI → history revision count incorrect in UI
Assignee: nobody → njirap
Summary: history revision count incorrect in UI → release history revision count incorrect in UI
This is a backend problem. The api returns a default limit of 100 revisions and a default count of 1024.
(In reply to Njira from comment #3)
> This is a backend problem. The api returns a default limit of 100 revisions
> and a default count of 1024.
The default count is actually total_count of the revisions..
Comment 5•9 years ago
|
||
Unfortunately, I had to back this out because it broke pagination on the non-history views (ie: http://localhost:8080/rules). I found two problems:
1) The pagination controls disappeared.
2) When I managed to get them re-added (by adjusting the ng-show), the items didn't change as I changed pages, probably due to the dropping of the startFrom filter.
If there's a quick fix for it, that would be great. In the longer term, it might be worth looking at separating the history and non-history templates/controllers, as they are diverging a lot now.
Can we have the rules/releases views also paginated server-side..?
Comment 7•9 years ago
|
||
Thanks for fixing this Njira!
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Updated•5 years ago
|
Product: Release Engineering → Release Engineering Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•