Bug 720680 - Tasks Executed doesn't include page info in pagination links
Summary: Tasks Executed doesn't include page info in pagination links
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Beaker
Classification: Retired
Component: web UI
Version: 0.6
Hardware: Unspecified
OS: Unspecified
medium
unspecified vote
Target Milestone: ---
Assignee: Raymond Mancy
QA Contact: tools-bugs
URL:
Whiteboard: UX
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-12 13:22 UTC by Chris Ward
Modified: 2014-12-08 01:08 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-02 23:12:08 UTC


Attachments (Terms of Use)

Description Chris Ward 2011-07-12 13:22:19 UTC
Description of problem:

On executed Tasks page, after doing a search that results in more than "1 page" (?) worth of results, 

1) it's really difficult to notice the '< << >> >' pagination links
2) one has no idea how many results there are, how many results are shown per page, how many pages more they'll be scrolling, or what page they're on.

Expected results:

Pagination would include those items i see missing in 2).

Comment 1 Chris Ward 2011-07-12 13:27:53 UTC
It'd be nice too if 
A) '> >>' was replaced (or complemented by) some plain English words like 'next' and 'last'. It's not always entirely obvious what those little signs mean

B) pagination links where available at the bottom of the list too, so i don't have to scroll all the way back up top to go to the next page.

:)

Comment 3 Chris Ward 2013-07-02 13:41:58 UTC
FYI I don't know if this is a current request anymore; i haven't really used beaker for a while. Feel free to close this if no one else is interested

Comment 4 Raymond Mancy 2013-07-02 23:12:08 UTC
This doesn't seem to be really important to current users, given the length of time its been open without comment.

Closing, as we are trying to not invest too much in beaker's UI going forward, and a small cosmetic change like this is not a priority.


Note You need to log in before you can comment on or make changes to this bug.