Let's say I search for a certain build of a package, like for fedora-release, which opens:
https://koji.fedoraproject.org/koji/packageinfo?packageID=9
It shows:
Builds 1 through 50 of 306 >>> Page: [ 1 v ] ....... list of packages Tags 1 through 50 of 60 >>> Page: [ 1 v ] ....... list of tags
When I really search for something, then I need to list like 3 pages down to see that the package is not there, then I need to scroll back to the top and switch the page. This makes the searching constant scroll up and down, which is really unintuitive and hard to use, especially when the data rows are organized from top to bottom.
The worst case is that the distinguish between Build and Tags section is basically none, thus one can be fooled by the Web UI that the paging below the list of builds belongs to the builds, where one would logically expect it, but the paging there is for tags, not for builds. And yes, I've been fooled by this several times.
Thus, please, make this intuitive (and as it is in any/many other similar tools, check the Web Search engines) and move the paging elements at the bottom, below the first result. That's where people are looking for it. If you really need it at the top, then make a copy of it at the bottom as well.
Thanks for consideration.
Metadata Update from @tkopecek: - Custom field Size adjusted to small - Issue priority set to: Low (was: Normal) - Issue set to the milestone: 1.19 - Issue tagged with: usability
Fixed with #1676
Metadata Update from @tkopecek: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Metadata Update from @jcupova: - Issue tagged with: testing-done
Metadata Update from @dgregor: - Issue assigned to breilly
When is this supposed to be in the production, please? Opening the URL from the description above doesn't show any improvement. Also, could you verify that the below URL will work as well, please?
https://koji.fedoraproject.org/koji/rpminfo?fileStart=0&rpmID=19213160&fileOrder=name&buildrootOrder=-id&buildrootStart=0#filelist
This fix will be included in the Koji 1.19 release, which will likely finish next week. However, I can't say when Fedora would upgrade its Koji deployment to 1.19. I would look to @kevin for guidance on that.
This issue has been migrated to Fedora Forge: https://forge.fedoraproject.org/koji/koji/issues/1646
Please continue any further discussion there.