Project

General

Profile

Actions

Defect #34375

closed

"is not" operator for Subproject filter incorrectly excludes closed subprojects

Added by Go MAEDA about 4 years ago. Updated almost 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Filters
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Fixed
Affected version:

Description

"is not" operator for Subproject is expected to exclude only given projects, however, it actually excludes closed projects as well.

Suppose the following project tree.

parent(status: active) -- issue15
 +-- child1 (status: closed) -- issue16
 +-- child2 (status: active) -- issue17
 +-- child3 (status: active) -- issue18

When you apply the issues filter "[Subproject] [is not] [child3]" on the "parent", issues from "child1" and "child2" should be displayed but you will see issues only from child2.

Applying issues filter "[Subproject] [is not] [child3]" on the "parent":

[Expected result]
issue15, issue16, issue17

[Actual result]
issue15, issue17

The behavior is clearly inconsistent with the "is" and "any" operator, because the "is" operator is can be used for closed projects and displays its issues, and the "any" operator includes closed projects as well as active projects.


Files

34375-test.patch (1.21 KB) 34375-test.patch Go MAEDA, 2020-12-27 13:56

Related issues

Related to Redmine - Defect #34297: Subprojects issues are not displayed on main project when all subprojects are closedClosedGo MAEDA

Actions
Actions

Also available in: Atom PDF