Defect #33499
closed
Issue filter "Subproject" does not work
Added by Sebastian Paluch over 5 years ago.
Updated over 5 years ago.
Description
Issue filter "Subproject" does not work. Looks like whatever is set, is ignored and issues from all subprojects are shown.
Environment:
Redmine version 4.1.0.stable
Ruby version 2.5.7-p206 (2019-10-01) [x64-mingw32]
Rails version 5.2.4.1
Environment production
Database adapter Mysql2
Mailer queue ActiveJob::QueueAdapters::AsyncAdapter
Mailer delivery smtp
SCM:
Subversion 1.11.1
Git 2.19.1
Filesystem
Redmine plugins:
no plugin installed
- Status changed from New to Needs feedback
Jean-Phillipe Lang said that "this is not a bug but a design choice" in #2512#note-3.
OK, but this is very very intuitive and actually not useful behavior. If I would like to see issues that are from the project and a sub-project then I should have a possibility to use multi-select - select with Ctrl current project and desired sub-project. Currently the list holds only sub-projects and by default adds all issues from the project.
Imagine situation that the project has 1000 issues, then I have 10 sub-project. I would like to see issues only from two sub-project - I cannot - because issues from the two sub-projects will be overwhelmed by a 1000 issues from the project...
Since this is "desired" behavior", it seems that my issue should be changed to feature request.
- Status changed from Needs feedback to Closed
- Resolution set to Invalid
If you want to display issues from only a specifically named subset of your projects, you can navigate to the global issue list at Projects -> Issues. There, you can select the projects you want to see issues from by using the Project filter.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by