View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0001466 | mantisbt | bugtracker | public | 2002-01-24 13:34 | 2004-11-06 06:50 |
Reporter | Luebbe | Assigned To | grangeway | ||
Priority | normal | Severity | feature | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Platform | All Browsers / Win98 | OS | Suse Linux / Apache | OS Version | 0.17.0 |
Product Version | 0.17.0 | ||||
Fixed in Version | 0.19.1 | ||||
Summary | 0001466: How about having [prev] / [next] bugs buttons in the view_* pages as well? | ||||
Description | This way you wouldn't have to go back to the list to browse through ten consecutive new bugs. This is really bugging me :-) | ||||
Tags | No tags attached. | ||||
has duplicate | 0003423 | closed | vboctor | Add next and previous buttons |
has duplicate | 0001633 | closed | grangeway | getting some posiblity to navigate within the bug detail view. |
has duplicate | 0003695 | closed | grangeway | Link to next/previous bug in detailed view bug screen |
has duplicate | 0003860 | closed | grangeway | Navigation links in bugs view |
has duplicate | 0003355 | closed | prescience | improve navigation between bugs |
I would also like to see this. Except in "bug_view_page.php", I'd want to see [next by ID][prev by ID] |
|
I'm not sure that this exact functionality is possible or desireable, if you think about it. When there are multiple private projects in the database, there is no guarantee that the previous or next ID is visible to the current user. Really, moving next or previous only makes sense within the context of what you were viewing on the main view all bug page. Filters only exacerbate this UI difficulty. |
|
Barnabas - Even if this was enabled only for a "super user", this would be a great tool. As far as worrying about which filters were active, It would be way okay with me if filters were ignored. |
|
since mantis knows what project you're in, and has a cookie with your filter settings, it is not impossible to browse the list of bugs in your view query. But maybe querying each time is ineffecient and the query needs to be cached? |
|
I raised 0003423 which is essentially barnabus point. It is equally inefficient to go to n+1 from n when there are more than 1 projects in mantis. The only benefit in my opinion is to reference the filtered list so that you can cycle through the list in a next and previous manner. This feature would be invaluable for me as I have the unenviable task of managing priority within my project which means I am constantly going through each submitted defect. The next and previous button would cut the number of steps in half. |
|
The following patch, provides some support for this http://slacker.com/~paulr/patches/1.txt (against CVS Head / 0.19rc1) |
|