Feature #15773
Filtering out specific subprojects (using 'is not' operator)
Status: | Closed | Start date: | ||
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | % Done: | 0% | ||
Category: | Issues filter | |||
Target version: | 3.4.0 | |||
Resolution: | Fixed |
Description
It should be possible to select multiple subproject for which you don't want issues in the list.
That is besides currently existing is, all, none
there also needs to be is not
. This can not be achieved by selecting multiple projects except specific ones with is
filter because new subprojects could be added.
Related issues
Associated revisions
Filtering out specific subprojects (using 'is not' operator) (#15773).
Patch by Marius BALTEANU.
History
#1
Updated by Go MAEDA about 4 years ago
- Category changed from Issues to Issues filter
#2
Updated by Go MAEDA about 4 years ago
- Duplicated by Feature #24677: Include in Subproject's filter a option 'is not' added
#3
Updated by Mischa The Evil about 4 years ago
- Subject changed from Filtering out specific subprojects to Filtering out specific subprojects (using 'is not' operator)
#4
Updated by Marius BALTEANU about 4 years ago
- File is_not_filter_for_subprojects.diff
added
We are interested too in having the "is not" option available for subproject filter. Attached is a patch that implements this.
As a technical note, I changed in the existing implementation the "each(&:to_i)" to "map(&:to_i)" because the each method returns the same initial array (with project ids as strings), while the map method returns a new array (with the project ids casted to integers).
#5
Updated by Go MAEDA about 4 years ago
- Target version set to 3.4.0
It works fine for me and passed all tests. I think it is natural to have this feature.
Setting target version to 3.4.0.
Thank you for writing this patch so fast.
#6
Updated by Jean-Philippe Lang about 4 years ago
- Status changed from New to Closed
- Assignee set to Jean-Philippe Lang
- Resolution set to Fixed
Committed, thanks Marius.