Defect #3512

can't use 'Target Version' field in custom query when 'For All Projects' checked

Added by Brad Mace about 11 years ago. Updated over 8 years ago.

Status:ClosedStart date:2009-06-18
Priority:NormalDue date:
Assignee:-% Done:


Target version:-
Resolution:Duplicate Affected version:


You can create a custom query using the 'Target Version' field, and it works. You can then edit it and check 'For All Projects', and it still works. But if you edit again, the 'Target Version' filter has disappeared, and there is no option to re-add it in the Add filter box. (r2778)

Related issues

Duplicated by Redmine - Defect #4072: Custom query and "for all projects". Closed 2009-10-21
Duplicated by Redmine - Defect #3490: Unable to add filter for version fields to a custom query Closed 2009-06-12
Duplicates Redmine - Feature #4559: Add a version filter to the global issues view Closed 2010-01-12


#1 Updated by Brad Mace about 11 years ago

Realized I should point out that I'm trying to use the 'All' or 'None' options. Obviously the actual version values are project-specific.

#2 Updated by PC Guy over 9 years ago

It would be nice to at least see all issues that have Target none.
Are there any fixes in progress?

#3 Updated by Colan Schwartz over 9 years ago

+1 for getting this into a bug-fix release.

#4 Updated by Stephen Grant almost 9 years ago

+1 for getting this fixed. Anyone?

#5 Updated by Brandon Liles over 8 years ago

+1 for a fix for this as well. This is especially helpful for us since since we follow a scrum sprint method so all projects share the same version.

#6 Updated by Etienne Massip over 8 years ago

  • Status changed from New to Closed
  • Resolution set to Duplicate

Closed as duplicate (would be fixed with) #4559.

Also available in: Atom PDF