Feature #3952

Filtering by subproject still shows current project's issues

Added by Rahul Vaidya over 8 years ago. Updated about 1 month ago.

Status:NewStart date:2009-10-01
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Issues filter
Target version:-
Resolution:

Description

Set a filter for Subproject is <subprojectname>. The current parent project's issues will still be shown. Issue seen in trunk.


Related issues

Related to Redmine - Defect #5388: Filtering by subproject seems to not work Closed 2010-04-27
Related to Redmine - Defect #8853: Filter on subproject does not work Closed 2011-07-19
Follows Redmine - Defect #2512: Subproject filter do not work Closed 2009-01-15

History

#1 Updated by Ewan Makepeace about 8 years ago

+1

[This has been previously been flagged as by design in #2512 - but I feel is a mistake. Personally I need to be able to view subproject issues and exclude those not assigned to any subproject. This is currently impossible - moreover the current behavior is extremely counter intuitive since the filter field clearly says you should only be seeing subproject issues, and so this will continue to be reported as a bug I suspect...]

#2 Updated by Mischa The Evil about 8 years ago

  • Tracker changed from Defect to Feature

#3 Updated by Mischa The Evil about 8 years ago

I've changed this to be a feature request instead of being a defect (a new design-change is requested).

#4 Updated by Nigel Jones almost 8 years ago

+1
I ran into this bug immediately after adding a subproject to an existing project - it makes subprojects less useful

#5 Updated by Gerry Hawkins over 7 years ago

(running 1.0.1)
+1
I disagree with the 'this is not a bug, but by design' response.
If you read the from the filter UI: "Show issues where the status is open and the subproject is B", where B is a subproject of A and I am doing this filter in A, I expect to see issues that are open and only in subproject B.

I appreciate the comment that if I want to filter to see just issues in the sub project I should go there, but I feel that the UI as it exists misrepresents what is probably a more common expectation. "is" implies equals. If you changed the all/none/is pull down to be all/none/including/excluding then I would say the UI and workflow would be OK. But still not what I would like. ;-)

#6 Updated by Terence Mill over 7 years ago

In general you sould be able to search and filter all tickets in the current project you are at the moment and its subprojects.

There are 3 search type one would use in this context.

  1. Search in current project and its siblings
  2. Search only in current project without its siblings
  3. Search in a specific subproject (of current project and) its siblings > this excludes all tickets above the subproject till this project going upwards the tree
  4. Search in a specific subproject (which belongs to current project) without its siblings

1. is possible by default and 3. can be achived by junping to subproject and doing as in 1.

How can 3. and 4. be achieved at the moment?

#7 Updated by Kevin Palm about 2 years ago

+1

#8 Updated by Go MAEDA about 1 year ago

  • Category changed from Issues to Issues filter

#9 Updated by Mischa The Evil about 1 year ago

  • Related to Defect #8853: Filter on subproject does not work added

#10 Updated by Phil Valentine about 1 month ago

+1

I too was bemused when my filter did not do as I expected.
Filter say show me things that are:
Staus=Open
SubProject=SubprojectA

With this setup I did not expect to see issues that were related to the parent project.

Also available in: Atom PDF