Filter on subproject does not work
|Resolution:||Wont fix||Affected version:||1.2.1|
filtering an issue list based on subproject does not work.Steps to Reproduce:
- Go to the Issues list for a project that has sub-projects
- Add a filter for "Subproject"
- set "Subproject" is subproject name
Notice that results are not filtered.
This bug was found on our own Redmine server running 1.0.1. It was upgraded to 1.2.1 but the bug still exists.
I then tried on the Redmine Demo site. It is still an issue there.
I saved a query for sample.
#2 Updated by Jens Krämer over 9 years ago
- File subprojects_query_filter_fix.patch added
Attached is a patch against 1.3-stable that fixes the issue by only finding issues from the selected sub projects, but excluding issues from the parent project.
The patch also fixes the german translation of
field_subproject (which until now was more like 'subproject of' which is wrong given the way the query works).
#6 Updated by Ilya Popov over 4 years ago
Problem still exists in 3.3.1 and 3.3.0. When filtering based on subproject also getting issues from the parent project.
Redmine version 3.3.1.stable
Ruby version 2.3.0-p0 (2015-12-25) [x86_64-linux]
Rails version 220.127.116.11
Database adapter Mysql2
#10 Updated by Mischa The Evil over 4 years ago
Go MAEDA wrote:
Jean-Phillipe Lang said that "this is not a bug but a design choice" in #2512#note-3.
FWIW and FTR: Jean-Phillipe Lang also expressed (in #5388-1: "Maybe we should change this behaviour.") that it might be a good time to change the current behaviour to omit the current project's issues; as was achieved by the, meanwhile, outdated patch by Jens. Therefor I'd recommend to continue discussion about this change in the current issue, tracking the proposal to change the current behaviour, which is #3952. I also recommend to transfer Jens's patch to it, so that it can be updated/refined through that issue.