Feature #12066
open
Don't show issues for closed projects in all issues list
Added by Oregon State University Central Web Services over 11 years ago.
Updated over 5 years ago.
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.
Files
Here are the changes we made to get this to work
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.
- Has duplicate Defect #19462: Dont show Issues from closed projects added
- 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
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
+1 for an additional filter criteria
- Related to Feature #20081: Filter issues and time entries by project status added
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?
- 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.
- 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.
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
Updated by 
Updated by Toshi MARUYAMA 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by