Cannot find an issue from a closed subproject when search scope is Project and its subprojects
|Assignee:||Go MAEDA||% Done:|
I have a main project with several closed subprojets. I want to find an issue from one of these closed projects.
Using the search function with 'project with subprojects' Redmine does not list it.
When using 'all projects' or reopening the concerning project Redmine shows the issue.
If this is not a bug, it would be nice to have an option to switch that behavior off.
Include closed projects in search for scope subprojects (#28636).
Patch by Marius BALTEANU.
#2 Updated by Marius BALTEANU over 1 year ago
- Category changed from Issues list to Search engine
- Status changed from New to Confirmed
Confirmed the problem.
Scope 'subprojects' is the only scope that searches only in the active projects. Scopes 'all' and 'my projects' include also closed projects. I think we should be consistent with the behaviour between the search scopes. At the same time, maybe it is a good idea to have an option in the search page to include only active projects in the search (how we have for the issues).
#3 Updated by Go MAEDA over 1 year ago
I agree with Marius' opinion. Jean-Philippe wrote in #6049#note-9 as follows. It is obvious that closed subprojects should be searchable.
I'm closing this request since 2.1.0 adds the ability to close projects. Closed projects are still visible/searchable but read-only.
#5 Updated by Marius BALTEANU over 1 year ago
- File 0001-Include-closed-projects-in-search-for-scope-subproje.patch added
- Target version set to Candidate for next minor release
Attached the patch. I think we can include this fix in 3.4.7 or 3.3.9.
All tests pass: https://gitlab.com/marius-balteanu/redmine/pipelines/39107412
#8 Updated by Go MAEDA over 1 year ago
- Status changed from Confirmed to Closed
- Assignee changed from Marius BALTEANU to Go MAEDA
- Target version changed from 3.3.9 to 3.4.7
- Resolution set to Fixed
Committed the patch. Thank you for catching and fixing this issue.
I didn't commit the fix to 3.3-stable branch because a test failed.
$ ruby test/functional/search_controller_test.rb Run options: --seed 17373 # Running: ...............................F. Finished in 7.689243s, 4.2917 runs/s, 14.1756 assertions/s. 1) Failure: SearchControllerTest#test_search_should_include_closed_projects [test/functional/search_controller_test.rb:302]: Expected at least 1 element matching "#search-results", found 0.. Expected 0 to be >= 1. 33 runs, 109 assertions, 1 failures, 0 errors, 0 skips