Feature #12066

Don't show issues for closed projects in all issues list

Added by Oregon State University Central Web Services about 6 years ago. Updated 15 days ago.

Status:NewStart date:
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Issues
Target version:-
Resolution:

Description

Currently, in version 2.1.2, when you go to all projects, it lets you show closed projects.

When you look at all issues, it by default shows all issues in the project list, including closed projects.

Ideally we would have the same functionality in the all issues, to include issues from closed projects, but not by default.

patch-2.1.2-closed_projects.out - patch for issue (2.41 KB) Oregon State University Central Web Services, 2012-10-19 10:12

project_status_filter.png (254 KB) Marius BALTEANU, 2018-10-22 00:29


Related issues

Related to Redmine - Defect #21210: Issues and Spent Time of closed subprojects are included ... New
Related to Redmine - Feature #20081: Filter issues and time entries by project status Closed
Duplicated by Redmine - Defect #19462: Dont show Issues from closed projects Closed

History

#1 Updated by Oregon State University Central Web Services about 6 years ago

This is related to issues #4202 and #3640

#2 Updated by Toshi MARUYAMA about 6 years ago

  • Category set to Issues

#3 Updated by Oregon State University Central Web Services about 6 years ago

Here are the changes we made to get this to work

#4 Updated by Konstantin Tkachenko almost 4 years ago

I think it could be better to enable filtering by active or closed projects in the issues queries. Just as for the issue status filter criteria (status => open, status => closed).
Currently one have to select all the active projects to be able to hide all the closed ones.

#5 Updated by Go MAEDA over 3 years ago

  • Duplicated by Defect #19462: Dont show Issues from closed projects added

#6 Updated by Jean-Philippe Lang about 3 years ago

  • Related to Defect #21210: Issues and Spent Time of closed subprojects are included on the overview page, but are not included on the issues, gantt or spent time details/report pages added

#7 Updated by zhangzhi liao 3 months ago

Konstantin Tkachenko wrote:

I think it could be better to enable filtering by active or closed projects in the issues queries. Just as for the issue status filter criteria (status => open, status => closed).
Currently one have to select all the active projects to be able to hide all the closed ones.

+1

#8 Updated by Bernhard Rohloff 3 months ago

+1 for an additional filter criteria

#9 Updated by Marius BALTEANU 24 days ago

  • Related to Feature #20081: Filter issues and time entries by project status added

#10 Updated by Marius BALTEANU 24 days ago

I've posted in #20081 two patches that add the possibility to filter issues and time entries after project status.

Moreover, I've worked on a patch that adds the "Project's status" filter to issues and time entries list by default (in the same way as Status filter is added) in two cases:
  • the context is global
  • when the project has subprojects

What do you think?

#11 Updated by Go MAEDA 16 days ago

  • Status changed from New to Closed
  • Assignee set to Go MAEDA
  • Target version set to 4.0.0
  • Resolution set to Fixed

Committed the patch posted by Marius. Thanks.

#12 Updated by Go MAEDA 16 days ago

  • Status changed from Closed to New
  • Assignee deleted (Go MAEDA)
  • Target version deleted (4.0.0)
  • Resolution deleted (Fixed)

Go MAEDA wrote:

Committed the patch posted by Marius. Thanks.

Sorry, I updated the wrong issue.

#13 Updated by Marius BALTEANU 15 days ago

Marius BALTEANU wrote:

[...]
  • when the project has subprojects

This condition is not enough because if the project is disabled and it has suprojects, it will be odd to apply by default the Project’s status is active filter. Maybe it is better to keep the code simpler and apply the filter by default only in the global context.

Waiting for other opinions before posting the patches.

Also available in: Atom PDF