Project

General

Profile

Actions

Defect #34375

closed

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

Defect #34375: "is not" operator for Subproject filter incorrectly excludes closed subprojects

Added by Go MAEDA almost 6 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Filters
Target version:
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 1 (0 open — 1 closed)

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

Updated by Go MAEDA almost 6 years ago Actions #1

  • Related to Defect #34297: Subprojects issues are not displayed on main project when all subprojects are closed added

Updated by Go MAEDA almost 6 years ago Actions #2

The issue is caused at source:branches/4.1-stable/app/models/query.rb#L886

Updated by Go MAEDA almost 6 years ago Actions #3

This issue has been fixed in r20693. The attached test code makes sure that.

Updated by Go MAEDA almost 6 years ago Actions #4

  • Status changed from New to Resolved
  • Assignee set to Go MAEDA
  • Resolution set to Fixed

Committed the test code.

Updated by Go MAEDA almost 6 years ago Actions #5

  • Status changed from Resolved to Closed
Actions

Also available in: PDF Atom