Actions
Defect #9738
closedSetting of cross-project custom query is not remembered inside project
Start date:
Due date:
% Done:
0%
Estimated time:
Resolution:
Fixed
Affected version:
Description
In previous versions of Redmine, a custom query was remembered when I returned to the issues tab. After I upgraded our redmine to the latest HEAD, this is no longer the case.
Steps to Reproduce:
- Go to the Issues tab
- Click on a custom query
- Note that the organization of the issues has changed (ordering, grouping, etc.)
- Click again on the Issues tab
- Unexpected: note that the custom query is lost
Now:
- Go to the Issues tab
- Click on a custom query
- Note that the organization of the issues has changed (ordering, grouping, etc.)
- Click on the "Apply" button
- Click again on the Issues tab
- Note that the organization of the issues has not changed.
Expected Result:
- It should not be necessary to click "Apply" for the custom query to be recognized.
This seems to work properly on the redmine site running 1.2.2, but it doesn't work for me on my installation running on trunk HEAD.
Related issues
Updated by Etienne Massip almost 13 years ago
- Status changed from New to Confirmed
- Target version set to 1.3.0
Updated by Bruno Medeiros almost 13 years ago
Maybe I found a similar bug #9742... project filter is also being lost.
Updated by Jean-Philippe Lang almost 13 years ago
- Subject changed from Setting of Custom Query is not remembered to Setting of cross-project custom query is not remembered inside project
- Status changed from Confirmed to Resolved
This should be fixed by r8113.
Updated by James Berry almost 13 years ago
With this fix (r8113), this is now once again working for me. Thanks for the fix!
Updated by Jean-Philippe Lang almost 13 years ago
- Status changed from Resolved to Closed
- Resolution set to Fixed
Merged in 1.3-stable.
Actions