Defect #4072

Custom query and "for all projects".

Added by S Reid over 12 years ago. Updated over 12 years ago.

Status:ClosedStart date:2009-10-21
Priority:NormalDue date:
Assignee:-% Done:


Target version:-
Resolution:Duplicate Affected version:0.8.4


If I create a new custom query (e.g. status == open, version != backlog) with "for all projects" ticked, as soon as I save it, the second filter (version != backlog) is lost. It's not applied to the list of issues, and if I edit the custom query, the second filter is missing.

This does not happen if I do it in 2 stages. I.e. create the custom query without ticking "for all projects" and save it. Then edit it, enable "for all projects" and save it again.

Related issues

Duplicates Redmine - Defect #3512: can't use 'Target Version' field in custom query when 'Fo... Closed 2009-06-18


#1 Updated by S Reid over 12 years ago

Also, if I then try to make the custom query public, I then also lose my second filter (target version). If I try to add it back by editing the customer query, I find that "target versino" is not on the filter drop down list. I then have to delete to query and start again.

#2 Updated by Jean-Philippe Lang over 12 years ago

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

See #3512.

Also available in: Atom PDF