Vote #71026
完了Setting of cross-project custom query is not remembered inside project
0%
説明
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.
journals
Redmine 1.3.0.devel.8101 (MySQL)
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Indeed, lost the project filter.
--------------------------------------------------------------------------------
Maybe I found a similar bug #9742... project filter is also being lost.
--------------------------------------------------------------------------------
This should be fixed by r8113.
--------------------------------------------------------------------------------
With this fix (r8113), this is now once again working for me. Thanks for the fix!
--------------------------------------------------------------------------------
Merged in 1.3-stable.
--------------------------------------------------------------------------------
related_issues
relates,Closed,9108,Custom query not saving status filter
duplicates,Closed,9742,Issues from other projects appearing in an specific project