Project

General

Profile

Actions

Defect #16395

open

Subproject filter is not saved in query if "For all project" is checked

Added by Ofer Nave about 10 years ago. Updated almost 8 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Issues
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Affected version:

Description

When looking at the list of issues in a project that contains sub-projects, I can add a filter for "Subproject" with the value "none" which filters out all the sub-project issues, leaving just the issues that are directly in the parent project. This is very useful.

However, when I click "Save" and give it a name and then save it, the Subproject filter gets dropped.

Environment:
Redmine version 2.5.0.stable.12980
Ruby version 1.9.3-p484 (2013-11-22) [x86_64-linux]
Rails version 3.2.17
Environment production
Database adapter Mysql2
Redmine plugins:
redmine_dmsf 1.4.8 devel
redmine_time_tracker 0.4

Actions #1

Updated by Ofer Nave about 10 years ago

  • Status changed from New to Resolved

Seems to be working now, though I'm not sure how -- I didn't change anything. In fact, I had deleted it, then it showed up again today, this time working correctly.

If I learn more, I'll reopen/update this.

Actions #2

Updated by Jean-Philippe Lang about 10 years ago

  • Status changed from Resolved to Needs feedback

I guess you're checking "For all project" when saving your query? The subproject filter is not available for cross-project queries, that's why the filter is dropped.

Actions #3

Updated by Ofer Nave about 10 years ago

Yes, I did. I found it very useful, and so wanted to share. :)

Good to know why it didn't work, thanks.

Actions #4

Updated by Toshi MARUYAMA about 10 years ago

  • Subject changed from Subproject filter not saved in query to Subproject filter not saved in query if "For all project" checked
  • Status changed from Needs feedback to New
Actions #5

Updated by Toshi MARUYAMA about 10 years ago

  • Subject changed from Subproject filter not saved in query if "For all project" checked to Subproject filter not saved in query if "For all project" is checked
Actions #6

Updated by Сергей Нерволь about 10 years ago

Jean-Philippe Lang wrote:

The subproject filter is not available for cross-project queries, that's why the filter is dropped.

Too bad. This was wery usefull functionality for me...
for example i have this project structure:
Company1
-- Project1
--- Subproject1
--- Subproject2
-- Project2
Company2
-- Project1
--- Subproject1
-- Project2
Company3
-- Project1
--- Subproject1
--- Subproject2
-- Project2

and there are about 50+ companies wich must use similar querries to use.
Now I must make 150+ similar querries instead 3.

Actions #7

Updated by Toshi MARUYAMA almost 10 years ago

  • Subject changed from Subproject filter not saved in query if "For all project" is checked to Subproject filter is not saved in query if "For all project" is checked
Actions #8

Updated by Chi Song Tao almost 8 years ago

I want to add a custom query for every project to list issues with subprojects'. How can I edit the query?

Actions

Also available in: Atom PDF