Closed Bug 704580 Opened 13 years ago Closed 13 years ago

first last prev next buttons does NOT navigate in good order after the query list is resorted

Categories

(Bugzilla :: Query/Bug List, defect)

defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 644281

People

(Reporter: a.zhao, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20100101 Firefox/8.0
Build ID: 20111104165243

Steps to reproduce:

1) I did a query which resulted, say, 10 bugs in total.
2) I then click on the sortable column, say, Severity, to resort the list
3) I decide to go through the bugs in sequence in detail.
4) Click on the first bug in the list.
5) At the top it might say Bug 4 of 10, even though it is the first bug in the
list and first I clicked on.
6) If I hit "Next" the bug number similarly jumps around.




Actual results:

It looks like the list as queried without sorting is saved, and first | last | prev | last buttons are made against the original list, with regardless what sort order that user prefers.


Expected results:

The first | last | prev | last button when bug is opened from a query list should reflect whatever the sorted order as seen by user.
Assignee: general → query-and-buglist
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Component: Bugzilla-General → Query/Bug List
Resolution: --- → DUPLICATE
I think this may be a different issue that what is in bug 644281 as it seems to be related to the fact that BMO uses javascript to sort the buglist by column. When a user resorts the list the cookie that contains the bug id list is not resorted and has the original order.

dkl
I looked at bug 644281, I am really not sure if this is the same issue.

Note, I do not use any user preference here, only a click in the sorting column (comment #1):
"2) I then click on the sortable column, say, Severity, to resort the list"

Can someone review this again?
Well, that's exactly what bug 644281 is about. And I see nowhere in comment 0 that the problem is about bmo.
You need to log in before you can comment on or make changes to this bug.