https://www.redmine.org/
https://www.redmine.org/favicon.ico?1679302129
2009-02-26T21:21:35Z
Redmine
Redmine - Feature #2850: Add next/previous navigation to issue
https://www.redmine.org/issues/2850?journal_id=7686
2009-02-26T21:21:35Z
Mischa The Evil
<ul></ul><p>Just my first thoughts on this FR:</p>
<p><strong>Christian Zagrodnick wrote:</strong></p>
<blockquote>
<p>...there should be next/previous links on the ticket to navigate the list.</p>
</blockquote>
This could become a bit difficult and can lead to some confusion considering the fact that this could be understood as:
<ol>
<li>The next issue in the list (as in: <code>#2</code> is the next behind <code>#1</code>)</li>
<li>The next issue in the list (as in: <code>#10#</code> is the next behind <code>#1</code> respecting the current issue-query (filters) state)</li>
</ol>
<p>What do you think?</p>
Redmine - Feature #2850: Add next/previous navigation to issue
https://www.redmine.org/issues/2850?journal_id=7694
2009-02-27T07:10:26Z
Christian Zagrodnick
<ul></ul><p>The second is what I was thinking about.</p>
<p>Actually I'm a long time Bugzilla user, so I may be a little biased. Let me describe what's happening there as I find this quite handy:</p>
<ul>
<li>When you do a search and open a ticket from this search, you'll get those first/next/prev/last links.</li>
<li>There is also a link "show list" which takes you back to the list.</li>
<li> The list stays stable. That is that the search tickets h is only done once and Bugzilla stores the ticket ids for the list. This is probably the major trick because it really avoids confusion: say you list your open and fix a few. Going back to the list shows the fixed as fixed although the initial search filters for open onces.</li>
</ul>
<p>Another thing is that when updating a ticket Bugzilla it doesn't display the updated ticket but the next one in the list.</p>
<p>Just my two cents :)</p>
Redmine - Feature #2850: Add next/previous navigation to issue
https://www.redmine.org/issues/2850?journal_id=7695
2009-02-27T08:08:57Z
Jens Goldhammer
<ul></ul><p>Sounds really good. Trac does the same...<br />As you both mentioned, there are different contexts:<br />1. If you browse the tickets without a search-> it should provide you a next and previous button for browsing to the ticket one number after the current or one before the current.</p>
<p>2. If you make a search or work in a custom report, the links should take you through the list as described by Christian.</p>
<p>I would like to see both things implemented! To make the difference understandable by the users, there should be good button labels ("next ticket" for normal browsing, "next ticket in search" for searching) and maybe tooltips.</p>
<p>Thanks,<br />Jens</p>
Redmine - Feature #2850: Add next/previous navigation to issue
https://www.redmine.org/issues/2850?journal_id=7703
2009-02-27T15:06:33Z
Christian Zagrodnick
<ul></ul><p>Jens Goldhammer wrote:</p>
<blockquote>
<p>1. If you browse the tickets without a search-> it should provide you a next and previous button for browsing to the ticket one number after the current or one before the current.</p>
</blockquote>
<p>Frankly, I don't see a use in that. Ticket numbers are basically random in regard to the ticket contents. Subsequent numbers usualy relate to totally unrelated tickets. Why would one want to navigate that?</p>
<p>I think when you navigate to a ticket without having a search (or if the ticket is not in the search list) those links should just be disabled until you get to a ticket which is in the list again.</p>
Redmine - Feature #2850: Add next/previous navigation to issue
https://www.redmine.org/issues/2850?journal_id=7716
2009-02-27T20:36:43Z
Enderson Maia
<ul></ul><p>Christian Zagrodnick wrote:</p>
<blockquote>
<p>Frankly, I don't see a use in that. Ticket numbers are basically random in regard to the ticket contents. Subsequent numbers usualy relate to totally unrelated tickets. Why would one want to navigate that?</p>
</blockquote>
<p>I agree. This ticket navbar just should be shown when you are in a filter/report result.</p>
Redmine - Feature #2850: Add next/previous navigation to issue
https://www.redmine.org/issues/2850?journal_id=9827
2009-06-18T17:39:57Z
Tom Burke
<ul></ul><p>+1 to this ticket.</p>
<p>I don't agree with Christian and Enderson's recent conversation about this not being useful. I've wanted this feature for a while because often as I'm creating new tickets, related tickets end up adjacent to one another in the project's list. Then later, when updating or closing, it would be useful to navigate to the next one, recalling that they fell next to each other.</p>
<p>I agree with the above that search context should be retained. And I like the stipulation that if the user closes a ticket, it still appears when he scrolls through his search results via next/previous, even if it was open when he searched for it.</p>
<p>Here's how I view the details of this feature:</p>
<ul>
<li>By default, the First button navigates to the ticket whose ID is numerically the smallest, WITHIN THE PROJECT CURRENTLY BEING VIEWED.</li>
<li>By default, the Last button navigates to the ticket whose ID is numerically the greatest, WITHIN THE PROJECT CURRENTLY BEING VIEWED.</li>
<li>By default, the Next button navigates to the next greatest ID WITHIN THE CURRENT PROJECT.</li>
<li>By default, the Previous button navigates to the next least ID WITHIN THE CURRENT PROJECT.</li>
<li>Several navigational scopes should be identified, to determine how Next/Previous/First/Last will behave:
<ul>
<li>A "default" scope, where the user is navigating among all open tickets. This is the state reached when clicking on "Issues" for the first time.</li>
<li>A "search" scope, where the user is navigating among tickets resulting from his last search.</li>
<li>A "filter" scope, where the user is navigating among tickets resulting from his last filter via the Issues screen.</li>
<li>An "all" scope, where the user is navigating among all tickets throughout the system.</li>
</ul>
</li>
<li>The search scope should be retained even if ticket statuses change, e.g., from open to Closed (see Christian's suggestion above:)</li>
</ul>
<blockquote>
<p>The list stays stable. That is that the search tickets h is only done once and Bugzilla stores the ticket ids for the list. This is probably the major trick because it really avoids confusion: say you list your open and fix a few. Going back to the list shows the fixed as fixed although the initial search filters for open onces.</p>
</blockquote>
Redmine - Feature #2850: Add next/previous navigation to issue
https://www.redmine.org/issues/2850?journal_id=9963
2009-06-30T03:11:41Z
Cyber Sprocket
<ul></ul><p>+1</p>
<p>This would be a great feature. I've been wanting a "next issue" button since the 2nd day we've been on Redmine. It is very useful as a project manager to go through and bump dates, re-assign people,or change priorites as the issues for new projects/features tend to fall next to each other on the list.</p>
<p>Even more useful if it goes from the list you were looking at including any filters that were set.</p>
Redmine - Feature #2850: Add next/previous navigation to issue
https://www.redmine.org/issues/2850?journal_id=10902
2009-09-10T14:12:48Z
Philippe Lafoucrière
<ul></ul><p>+1 !</p>
Redmine - Feature #2850: Add next/previous navigation to issue
https://www.redmine.org/issues/2850?journal_id=10908
2009-09-10T19:16:59Z
Nanda P
<ul></ul><p>+1</p>
Redmine - Feature #2850: Add next/previous navigation to issue
https://www.redmine.org/issues/2850?journal_id=13544
2010-01-12T21:38:39Z
Alex Last
<ul></ul><p>+1. <br />btw, can we have "votes" to avoid adding this stupid "+1"?</p>
Redmine - Feature #2850: Add next/previous navigation to issue
https://www.redmine.org/issues/2850?journal_id=14561
2010-02-20T20:48:01Z
Eric Wasylishen
<ul></ul><p>+1.<br />It would make reading through a list of issues a lot easier.</p>
Redmine - Feature #2850: Add next/previous navigation to issue
https://www.redmine.org/issues/2850?journal_id=14971
2010-03-08T14:56:53Z
Alexander Stehlik
<ul></ul><p>+1</p>
Redmine - Feature #2850: Add next/previous navigation to issue
https://www.redmine.org/issues/2850?journal_id=15579
2010-03-31T18:33:33Z
Christian Hausleitner
<ul></ul><p>+1</p>
Redmine - Feature #2850: Add next/previous navigation to issue
https://www.redmine.org/issues/2850?journal_id=16059
2010-04-21T17:56:01Z
Aron Rotteveel
<ul></ul><p>+1</p>
Redmine - Feature #2850: Add next/previous navigation to issue
https://www.redmine.org/issues/2850?journal_id=16064
2010-04-21T19:44:39Z
minkbear minkbear
<ul></ul><p>+1</p>
Redmine - Feature #2850: Add next/previous navigation to issue
https://www.redmine.org/issues/2850?journal_id=16127
2010-04-23T17:15:25Z
Andrew Sherman
<ul></ul><p>+1</p>
<p>At my business we recently moved from Bugzilla to Redmine and the <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Defect: permissions if not admin (Closed)" href="https://www.redmine.org/issues/1">#1</a> questions I get from everyone is "there a next/prev link when you are going through your issues?"</p>
Redmine - Feature #2850: Add next/previous navigation to issue
https://www.redmine.org/issues/2850?journal_id=16655
2010-05-11T20:56:37Z
Kioma Aldecoa
<ul></ul><p>+1 we also are moving from bugzilla, and the one thing everybody misses is the next/prev links</p>
Redmine - Feature #2850: Add next/previous navigation to issue
https://www.redmine.org/issues/2850?journal_id=16912
2010-05-21T11:12:11Z
Ivo Abadjiev
<ul></ul><p>+ 1 we moved from JIRA and all the team is missing this feature</p>
Redmine - Feature #2850: Add next/previous navigation to issue
https://www.redmine.org/issues/2850?journal_id=17603
2010-06-21T20:22:53Z
David Parker
<ul></ul><p>+1</p>
Redmine - Feature #2850: Add next/previous navigation to issue
https://www.redmine.org/issues/2850?journal_id=17910
2010-07-01T22:31:55Z
Eric Peterson
<ul></ul><p>+1</p>
Redmine - Feature #2850: Add next/previous navigation to issue
https://www.redmine.org/issues/2850?journal_id=17914
2010-07-02T03:01:00Z
xt zhang
<ul></ul><p>+1</p>
Redmine - Feature #2850: Add next/previous navigation to issue
https://www.redmine.org/issues/2850?journal_id=21179
2010-10-08T19:51:24Z
Jean-Jacques Mérillon
<ul></ul><p>+1</p>
Redmine - Feature #2850: Add next/previous navigation to issue
https://www.redmine.org/issues/2850?journal_id=22477
2010-11-16T18:58:54Z
John Bart
<ul></ul><p>+1</p>
Redmine - Feature #2850: Add next/previous navigation to issue
https://www.redmine.org/issues/2850?journal_id=23025
2010-12-05T08:17:23Z
Emidio Stani
<ul></ul><p>+1</p>
Redmine - Feature #2850: Add next/previous navigation to issue
https://www.redmine.org/issues/2850?journal_id=24027
2011-01-13T18:13:29Z
loic Le Gallou
<ul></ul><p>+1</p>
Redmine - Feature #2850: Add next/previous navigation to issue
https://www.redmine.org/issues/2850?journal_id=24727
2011-02-01T11:40:47Z
Anonymous
<ul></ul><p>+1</p>
Redmine - Feature #2850: Add next/previous navigation to issue
https://www.redmine.org/issues/2850?journal_id=27853
2011-04-13T09:27:41Z
Sam Garnham
<ul></ul><p>+1</p>
Redmine - Feature #2850: Add next/previous navigation to issue
https://www.redmine.org/issues/2850?journal_id=27856
2011-04-13T09:52:18Z
Albert M
<ul></ul><p>+1</p>
Redmine - Feature #2850: Add next/previous navigation to issue
https://www.redmine.org/issues/2850?journal_id=28043
2011-04-18T07:29:27Z
Anton Lukashev
<ul></ul><p>+1</p>
Redmine - Feature #2850: Add next/previous navigation to issue
https://www.redmine.org/issues/2850?journal_id=30859
2011-07-19T10:10:24Z
Andrea Colleoni
<ul></ul><p>+1</p>
Redmine - Feature #2850: Add next/previous navigation to issue
https://www.redmine.org/issues/2850?journal_id=30893
2011-07-20T08:32:29Z
Andrew Lansdowne
<ul></ul><p>+1 this is a real issue for me moving from JIRA, I really don't mind how it is implemented (whether it updates the list when issues are amended or whether the list is static from your results) but just having to go back using the browser between viewing each issue just doubles the amount of clicking/waiting when you are trying to look through your issues.</p>
Redmine - Feature #2850: Add next/previous navigation to issue
https://www.redmine.org/issues/2850?journal_id=30894
2011-07-20T08:53:04Z
Etienne Massip
<ul><li><strong>Target version</strong> set to <i>Candidate for next major release</i></li></ul>
Redmine - Feature #2850: Add next/previous navigation to issue
https://www.redmine.org/issues/2850?journal_id=35098
2012-01-03T10:24:58Z
Marcel Ritter
<ul></ul><p>+1</p>
Redmine - Feature #2850: Add next/previous navigation to issue
https://www.redmine.org/issues/2850?journal_id=35108
2012-01-03T20:22:50Z
Jean-Philippe Lang
jp_lang@yahoo.fr
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Closed</i></li><li><strong>Target version</strong> changed from <i>Candidate for next major release</i> to <i>1.4.0</i></li><li><strong>Resolution</strong> set to <i>Fixed</i></li></ul><p>Feature added in <a class="changeset" title="Adds previous/next links to issue (#2850)." href="https://www.redmine.org/projects/redmine/repository/svn/revisions/8488">r8488</a> in its simplest form. The links show the previous and next issues as listed on the issue list without storing the query results.</p>
Redmine - Feature #2850: Add next/previous navigation to issue
https://www.redmine.org/issues/2850?journal_id=36441
2012-03-01T21:33:59Z
Maciej Maczynski
<ul></ul><p>I applied changes from <a class="changeset" title="Adds previous/next links to issue (#2850)." href="https://www.redmine.org/projects/redmine/repository/svn/revisions/8488">r8488</a> over 1.3.0 installation (installed from tarball) hoping it would be enough to change only files mentioned in this release.<br />Looks it is not: I have the following error in log when clicking on issue from the list:</p>
<pre>
Rendering /var/www/redmine/public/500.html (500 Internal Server Error)
Processing IssuesController#show (for 192.168.115.8 at 2012-03-01 22:05:22) [GET]
Parameters: {"action"=>"show", "id"=>"24", "controller"=>"issues"}
NoMethodError (undefined method `issue_ids' for #<Query:0xb560f1d4>):
app/controllers/issues_controller.rb:289:in `retrieve_previous_and_next_issue_ids'
app/controllers/issues_controller.rb:124:in `show'
...
</pre>
<p>The issue is not mentioned in 1.3.1 Changelog, so it is not included there, right?<br />Is there some kind of minimal-manual-changes to make it work with 1.3.0?</p>
Redmine - Feature #2850: Add next/previous navigation to issue
https://www.redmine.org/issues/2850?journal_id=36442
2012-03-02T07:54:49Z
Etienne Massip
<ul></ul><p>See <a class="changeset" title="Faster query." href="https://www.redmine.org/projects/redmine/repository/svn/revisions/8487">r8487</a>.</p>
Redmine - Feature #2850: Add next/previous navigation to issue
https://www.redmine.org/issues/2850?journal_id=36457
2012-03-02T21:39:36Z
Maciej Maczynski
<ul></ul><p>Yes you're right - it was necessary. But one more change was needed:<br />In <a class="changeset" title="Adds previous/next links to issue (#2850)." href="https://www.redmine.org/projects/redmine/repository/svn/revisions/8488">r8488</a>, show.html.erb line 42 is:</p>
<pre><code><code><td class="spent-time"><%= @issue.total_spent_hours > 0 ? (link_to l_hours(@issue.total_spent_hours), {:controller => 'timelog', :action => 'index', :project_id => @project, :issue_id => @issue}) : "-" %></td></code></code></pre>
<p>I changed it to original 1.3.0 version (not using "total_spent_hours":</p>
<pre><code><code><td class="spent-time"><%= @issue.total_spent_hours > 0 ? (link_to l_hours(@issue.total_spent_hours), {:controller => 'timelog', :action => 'index', :project_id => @project, :issue_id => @issue}) : "-" %></td></code></code></pre>
<p>Now it works!!! Thanks a lot for your help. After ten years using Bugzilla I missed this functionality VERY much.</p>
Redmine - Feature #2850: Add next/previous navigation to issue
https://www.redmine.org/issues/2850?journal_id=36945
2012-03-21T10:35:01Z
Sanjay Kashalkar
<ul></ul><p>After adding <a class="changeset" title="Faster query." href="https://www.redmine.org/projects/redmine/repository/svn/revisions/8487">r8487</a> and <a class="changeset" title="Adds previous/next links to issue (#2850)." href="https://www.redmine.org/projects/redmine/repository/svn/revisions/8488">r8488</a> onto Redmine 1.3.2.stable.6570 I can see the next/prev navigation links. However, deleting an issue fails with the following error.</p>
<pre>
Processing IssuesController#destroy (for 172.23.41.54 at 2012-03-21 11:28:34) [POST]
Parameters: {"back_url"=>"/redmine/projects/opl/issues", "ids"=>["5589"], "action"=>"destroy", "authenticity_token"=>"Oe6ubDyrsKmGc7wRP6Qofw3XjpuUJwTTcWG5am5TF94=", "controller"=>"issues"}
Filter chain halted as [#<Proc:0x05646a98@C:/Program Files/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/actionpack-2.3.14/lib/action_controller/verification.rb:82>] rendered_or_redirected.
Completed in 68ms (View: 6, DB: 31) | 405 Method Not Allowed [http://abcdef/redmine/issues/destroy?back_url=%2Fredmine%2Fprojects%2Fopl%2Fissues&ids%5B%5D=5589]
</pre>
<p>Any ideas why?</p>
<p>To reproduce simply select one or more issues and right click 'delete'.</p>
Redmine - Feature #2850: Add next/previous navigation to issue
https://www.redmine.org/issues/2850?journal_id=36946
2012-03-21T10:45:33Z
Maciej Maczynski
<ul></ul><p>I have exactly same problem: after applying those changes I cannot delete issues any more.<br />I did not report it so far as I had no time to verify 100% if this is really caused by this change or maybe some plug-in I've installed.<br />But your post seems to confirm that the problem is related revisions mentioned hare: I also have this "Method Not Allowed" error now.</p>
Redmine - Feature #2850: Add next/previous navigation to issue
https://www.redmine.org/issues/2850?journal_id=36980
2012-03-23T11:10:40Z
Maciej Maczynski
<ul></ul><p>Solved: you have to apply changes from <a class="changeset" title="Changed IssuesController#destroy to DELETE only." href="https://www.redmine.org/projects/redmine/repository/svn/revisions/8150">r8150</a>.</p>