Issue4

Title Provide prev/next/show list links when going through a list of bugs
Priority wish Status resolved
Superseder Nosy List ajaksu2, ezio.melotti, forsberg, mephinet, pefu512
Assigned To ajaksu2 Topics

Created on 2006-06-29.20:37:26 by forsberg, last changed 2011-10-21.02:19:25 by ezio.melotti.

Messages
msg4 (view) Author: forsberg Date: 2006-06-29.20:37:25
Bugzilla has a very neat feature - when you select a bug from a list of bugs
found via a search query, the bug has prev/show list/next links, to allow the
user to easily go to the next or previous bug in the list, or to easily get back
to the list of bugs. 

This is implemented using cookies that keep information about the list of bugs,
as well as the search query. I don't know how hard this would be to implement in
roundup, though.
msg23 (view) Author: pefu512 Date: 2006-07-07.16:59:58
The search query in Roundup is kept within the URL.  From the index page
(issue.index.html) it would be a simple template change to transmit 
this further into issue.item.html view.  From there it would be easy 
to put a link back to the search.  Paging back and forth will be more
difficult though, since the result of the query is not kept.  
Im not familar enough with Roundup to implement this.  Maybe it is possible
to restart the query with a certain special template, which renders a 
given item in the list as redirect.  But this would be ugly.

Since I use a tabbed browser I've never missed this feature.
I usually open issues on a new tab.
msg925 (view) Author: loewis Date: 2008-01-21.05:45:19
I just forwarded this upstream, as

http://sourceforge.net/tracker/index.php?func=detail&aid=1876221&group_id=31577&atid=402791
msg1196 (view) Author: ajaksu2 Date: 2009-03-01.17:52:52
I think this one can be implemented mostly in template-land, so I'll give it a try. 

The paging trick would be to store an equivalent pseudo-query (like
id=1,2,3,4,5,6,7&@filter=id, either in a cookie or hidden input) and a
positional pointer in a cookie.
msg1215 (view) Author: mephinet Date: 2009-03-07.14:22:06
> ... and a positional pointer in a cookie.

This would need to be carefully crafted to not break
multiple-searches-in-multiple-tabs.
msg1216 (view) Author: ajaksu2 Date: 2009-03-07.18:21:51
Philipp Gortan wrote:
>This would need to be carefully crafted to not break
>multiple-searches-in-multiple-tabs.

True. I think using a hidden input for the pointer would both avoid
multiple-searches-in-multiple-tabs issues and fit better with the way Roundup
does similar things.

I got the pseudo-query part working (issue 246), during next week I'll polish it
and try to build the prev/next/show feature on top of that.
msg1231 (view) Author: mephinet Date: 2009-03-08.15:57:24
I've tried to come up with a patch for this - you might want to take a look at
it. See upstream tracker:
<http://issues.roundup-tracker.org/issue1876221>
msg2298 (view) Author: ezio.melotti Date: 2011-10-21.02:19:24
Since this has been reported upstream, I think we can close this issue.
Once it gets fixed upstream and we update, the feature will be available.

FWIW when I search for issues I usually pick the ones that interest me and open them in new tabs.  Usually I don't want to go through all the issues, so I don't think I'll find the feature too useful.  Also if I want to e.g. triage the latest issues opened, the link shouldn't break when my triaging changes the order bumping the message to the top.
History
Date User Action Args
2011-10-21 02:19:25ezio.melottisetstatus: deferred -> resolved
nosy: + ezio.melotti
messages: + msg2298
2009-03-08 15:57:25mephinetsetmessages: + msg1231
2009-03-07 18:21:51ajaksu2setmessages: + msg1216
2009-03-07 14:22:07mephinetsetnosy: + mephinet
messages: + msg1215
2009-03-01 17:52:53ajaksu2setassignedto: ajaksu2
messages: + msg1196
nosy: + ajaksu2
2008-01-21 05:45:20loewissetstatus: chatting -> deferred
messages: + msg925
2006-07-07 16:59:58pefu512setstatus: unread -> chatting
nosy: + pefu512
messages: + msg23
2006-06-29 20:37:26forsbergcreate