Feature #14462
closed
Previous/next links may be lost after editing the issue
0%
Description
1. click on project,
2. click on issues,
3. get. eg. open issues,
4. review them using "prev"/"next" buttons, until found issue which should be closed (but isn't).
5. click update, set it as resolved/closed
RESULT: prev/next buttons disappears, because current issue gets out of query,
SHOULDBE: prev/next buttons should be visible and should point to issues from last running query.
Similar scenario: review list of unassigned tasks one by one and assign appropriately. Impossible using current next/prev implementation.
It works like that in Mantis, I believe that list of issue ids is stored somewhere in session, and prev/next gets data from that list.
Files
Related issues
Updated by zhiguo Zhu over 10 years ago
- File issues_controller.diff issues_controller.diff added
fix it for redmine-2.5.1
Updated by Toshi MARUYAMA over 10 years ago
zhiguo Zhu wrote:
fix it for redmine-2.5.1
Please add tests.
Updated by Toshi MARUYAMA over 10 years ago
- Has duplicate Defect #11006: next previous function not available if issue is closed added
Updated by
Updated by zhiguo Zhu over 9 years ago
- File issues_controller.diff issues_controller.diff added
Rupesh J wrote:
+1
fix for redmine-3.0.3
Updated by Go MAEDA over 9 years ago
- Target version set to Candidate for next major release
Updated by Takenori TAKAKI almost 9 years ago
- File prev_next_button_remember_issues_list_trunk_r15160.patch prev_next_button_remember_issues_list_trunk_r15160.patch added
I do appreciate the work of Łukasz Mach and zhiguo Zhu. I would be very happy if I could see the feature in Redmine 3.3.0.
I have updated the patch:
- Compatible with latest trunk (r15160)
- Added tests
- Changed a little bit, to pass the test
Updated by Go MAEDA almost 9 years ago
- Target version changed from Candidate for next major release to 3.3.0
The patch updated by Takenori TAKAKI includes tests and works fine.
I think we can merge the fix into trunk. Setting target version to 3.3.0.
Updated by Jean-Philippe Lang almost 9 years ago
- Subject changed from prev/next buttons - remember issues list to Previous/next links may be lost after editing the issue
- Category changed from UI to Issues
- Status changed from New to Closed
- Assignee set to Jean-Philippe Lang
- Resolution set to Fixed
Fixed in r15253. I used a slightly different approach to avoiding loading the query before updating the issue, thanks.
Updated by Go MAEDA almost 8 years ago
- Has duplicate Defect #13053: Prev Next button was not display when the query condition was changed added