Redmine

+1. This would be useful for some filters I have tried to make as well.

+1 I would love it if Redmine had this functionality. Perhaps the easiest/most powerful way to implement this would be to make a way for users to create filters out of combinations of other filters. In other words, if I could define filters A, B, and C, and then say something like "Give me all the issues that are in A OR B, but not in C", I could get any issue list I could ever want. And that would be awesome.

Jeremy Walker wrote:

+1 I would love it if Redmine had this functionality. Perhaps the easiest/most powerful way to implement this would be to make a way for users to create filter sets out of combinations of other filter sets. In other words, if I could define filter sets A, B, and C, and then say something like "Give me all the issues that are in A OR B, but not in C", I could get any issue list I could ever want. And that would be awesome.

Any progress on this subject guys? ;o)

+1
Thats nearly what I ment with #7641, but I'd like to combine AND and OR freely.

e.g. A AND B OR C AND D

should list all issues which fullfill both, A and B

plus the issue which fillfill both, C and D

Basically it should be read like disjunctive normal form

also this could be interesting when one wants to list all issues
assigned to me, and also all which aren't assigned yet.

for this feature a filtercriteria must be usable more than one time

or other solution: the list of possible assignees contains a special element "Not assigned" at the top of the list, so one can select (by multiple selection) me and "Not assigned"

It looks like it is implemented in "Trac": http://trac.edgewall.org/query, see the "OR" at the bottom right of the filters box

Gurvan Le Dromaguet wrote:

It looks like it is implemented in "Trac": http://trac.edgewall.org/query, see the "OR" at the bottom right of the filters box

I like it

Yes this would be a good improvement. It won't be easy but a really cool addition to the current filter-system.

+1

any workaround here? we need a filter like "is autor or observer"

+1

Need Assignee or Watcher.

+1

Thanks for your patch! i look forward to implement that in our redmine!!

+1

+1

+1 (thanks for your excellent work)

+1

Matthias Neubert wrote:

+1
Thats nearly what I ment with #7641, but I'd like to combine AND and OR freely.

e.g. A AND B OR C AND D

should list all issues which fullfill both, A and B

plus the issue which fillfill both, C and D

Basically it should be read like disjunctive normal form

+1

so important feature and no progress for 5 years :(

so important feature and no progress for 5 years :(

We only have 2 programmers working in their spare time, plus contributions from a few other volunteers.

If you send patches that apply cleanly against current trunk (together with tests) we'd happily test and apply those.

+1

I have made this patch into a plugins here (with some improvement). It works with redmine 2.6.x and 3.1.1 or less. Please use the plugin instead of this patch

http://www.redmine.org/plugins/zquery

+1

What is the difference between zquery and _query?

Did someone tested one with Redmine 2.4?

Fred B wrote:

What is the difference between zquery and _query?

Did someone tested one with Redmine 2.4?

Dear Fred
1. They are the same but I renamed zquery to _query so it is loaded first. _query is now the "official" version :-) (I have replace zquery attachment with _query but the name is still in the link)
2. I think it should work with 2.3 upward since I developed it based on 2.3 version
Quan

+1

+1

+1

+1

+1

So is there any chance that the _query plugin getting updated to function with Redmine 3.4? I tried to figure out how to update it, but it's not clear to me what needs to be changed to make it compatible.

It gives me the following error in 3.4 as is:

Showing /opt/redmine/app/views/queries/_filters.html.erb where line #4 raised:

undefined method `remote' for #<Hash:0x007fe319fa1de8>
Extracted source (around line #464):
462
463
464
465
466
467

    available_filters.each do |field, filter|
      options = {:type => filter[:type], :name => filter[:name]}
      options[:remote] = true if filter.remote

      if has_filter?(field) || !filter.remote
        options[:values] = filter.values

Trace of template inclusion: app/views/queries/_query_form.html.erb, app/views/issues/index.html.erb

Rails.root: /Users/noysh/projects/farview/farview-devlink-3.4-stable

Application Trace | Framework Trace | Full Trace
app/models/query.rb:464:in `block in available_filters_as_json'
app/models/query.rb:462:in `each'
app/models/query.rb:462:in `available_filters_as_json'
app/views/queries/_filters.html.erb:4:in `block in _app_views_queries__filters_html_erb__941875204378063440_70306769152520'
app/views/queries/_filters.html.erb:1:in `_app_views_queries__filters_html_erb__941875204378063440_70306769152520'
app/views/queries/_query_form.html.erb:10:in `_app_views_queries__query_form_html_erb___1924681068357817272_70306752298920'
app/views/issues/index.html.erb:11:in `block in _app_views_issues_index_html_erb___4300101081652184242_70306752230600'
app/views/issues/index.html.erb:10:in `_app_views_issues_index_html_erb___4300101081652184242_70306752230600'
app/controllers/issues_controller.rb:51:in `block (2 levels) in index'
app/controllers/issues_controller.rb:46:in `index'
lib/redmine/sudo_mode.rb:63:in `sudo_mode'
Request

Parameters:

{"project_id"=>"project_name"}
Toggle session dump
Toggle env dump
Response

Headers:

None

Shaun Gilroy wrote:

So is there any chance that the _query plugin getting updated to function with Redmine 3.4? I tried to figure out how to update it, but it's not clear to me what needs to be changed to make it compatible.

It gives me the following error in 3.4 as is:
[...]

Dear Shaun
I am sorry. This version of plugin is too old. I create a separate entry for this plugin and put the update here and it works with redmine 3.4
https://www.redmine.org/plugins/boolean_query
Unfortunately I cannot find way to delete this old attachment
Quan

Quan VN wrote:

For redmine 3.4, please use the version at
https://www.redmine.org/plugins/boolean_query
Or use new version attached here _query.0.0.3.rm34.zip

Excellent! Thank you!

+1

It could be great to allow filters with multiple conditions by same field (e.g. status is "open" AND status is not feedback) also.

+1 :}

Would it be possible to select the same field twice, so I can query "Due in the next 14 days or due date none" ?
Seems like the field is greyed out once it is selected.

+1

Hi, I have developed this feature in my company, I will try to bring it as a plugin.

is there an plugin version for 4.0? On the plugin site itself it tells me an 404?

Both https://www.redmine.org/plugins/boolean_query
and https://www.redmine.org/plugins/_query deliver 404

As far as I know there is no version for 4.0 available. But you could keep an eye on mbideau/redmine_zquery. There even is an issue for redmine 4.xx support.

Andreas Michel wrote:

is there an plugin version for 4.0?

Tobias Schmidt wrote:

As far as I know there is no version for 4.0 available. But you could keep an eye on mbideau/redmine_zquery. There even is an issue for redmine 4.xx support.

Andreas Michel wrote:

is there an plugin version for 4.0?

But mbideau/redmine_zquery is an older version and does not suppport Redmine 3.4 as _query version 0.0.3 posted in #42 by Quan VN.

Thanks for Your work.

Unfortunately the two methods match and not match introduce the logical operators inside the string fields. For example, if I want to search for a more then a string in a field in OR:

Description match string1 ~ string2 ~ string3 ~ string4

I obtain as result all issues that contain at least one of the four strings in field Description

giorgio rossi wrote:

Thanks for Your work.

Unfortunately the two methods match and not match introduce the logical operators inside the string fields. For example, if I want to search for a more then a string in a field in OR:

Description match string1 ~ string2 ~ string3 ~ string4

I obtain as result all issues that contain at least one of the four strings in field Description

I've read the readme and now understand what the operators match and not match do.
They have nothing to do with the or filters but are useful extensions for the queries. But I still don't know how to implement the new operators in the _query plugin. Sorry.

Fantastic job!!
Thanks You

Is anybody in contact with Jean-Philippe Lang so this has a change to get merged?

The filter options need to be much more poerfull...

Hi,

Can you put some screen captures to be able to see how it works and how it changes the native behavior ?

Thanks Emanuel

+1

I second that, JPL (or someone with equivalent competency) should review and merge.
This is extremely useful!

Thanks for useful patch.
http://www.redmine.org/issues/4939#note-56

I hope a lot of people have confirmed that this feature works and get it incorporated into RedmineCore as soon as possible.

However, the latest trunk rev19405 could not apply this patch.
To make it easier to try, I created a branch on my repository and patched it.

https://github.com/y503unavailable/redmine/tree/feature-patch4939

https://github.com/redmine/redmine/compare/master...y503unavailable:feature-patch4939.patch

In this code, I checked the operation of the or-filter function.

I added a Japanese term file patch.
But,created Tentatively.

The following branch publishes the 4.2-stable with this issue and the patch of issue 5358 applied.
I update every month for the latest trunk.

https://github.com/y503unavailable/redmine/tree/feature-unofficialcooking

Share Issues Categories for sub-projects
https://www.redmine.org/issues/5358

+1 for this feature

+1 for this feature (to create a simple filter: assignee OR watcher)

Yes, yes, yes +1 :-) ;-)

Being able to set the boolean operators would be very useful
+1 for this feature

Johannes Heymann wrote:

Being able to set the boolean operators would be very useful
+1 for this feature

+1 for this feature

+1 too

+1

+1

+1, I want this feature too!

2021-02-04:
I merge the patch into latest Redmine 4.x with a branch called logical-filters, check it out here
https://github.com/sweihub/redmine/tree/logical-filters

But still pity for each filter can only be used once.

https://www.redmine.org/issues/4939#note-56
for this patch really need ability to use the same column more than once
for be able to use simple filter like
Target OR Target

And espessially for OR in Tags - really can't use this feature for full without deep filtration

+1

Not clear to me whether this feature have been incorporated into the RedmineCore or not (?)

+1
+1
+1

+1

+1 for this but more logical operators for filters in general also multiple conditions for the same field.

How can this basic functionality not have been prioritized after all these years (11 years!)?

I'm trying to create filters to create a simple Eisenhower Matrix: [[https://todoist.com/productivity-methods/eisenhower-matrix]] with the help of

tags

tag is "Important" AND tag is "Urgent"

Please prioritize!

+1
+1

+1

+1

+1

+1

+1

+1

Hi everyone,

Tried/tested an upgrade to redmine 5.0.1.

The _query.0.0* plugins does not seem to work on redmine 5.0.X (at least for me) :

/usr/local/bundle/gems/zeitwerk-2.5.4/lib/zeitwerk/loader/callbacks.rb:25:in `on_file_autoloaded': expected file /usr/src/redmine/plugins/_query/lib/query_patch4.rb to define constant QueryPatch4, but didn't (Zeitwerk::NameError)

      raise Zeitwerk::NameError.new("expected file #{file} to define constant #{cpath}, but didn't", cref.last)
      ^^^^^
        from /usr/local/bundle/gems/zeitwerk-2.5.4/lib/zeitwerk/kernel.rb:28:in `require'
        from /usr/local/bundle/gems/zeitwerk-2.5.4/lib/zeitwerk/loader/helpers.rb:95:in `const_get'
        from /usr/local/bundle/gems/zeitwerk-2.5.4/lib/zeitwerk/loader/helpers.rb:95:in `cget'
        from /usr/local/bundle/gems/zeitwerk-2.5.4/lib/zeitwerk/loader.rb:237:in `block (2 levels) in eager_load'
        from /usr/local/bundle/gems/zeitwerk-2.5.4/lib/zeitwerk/loader/helpers.rb:26:in `block in ls'
        from /usr/local/bundle/gems/zeitwerk-2.5.4/lib/zeitwerk/loader/helpers.rb:18:in `each_child'
        from /usr/local/bundle/gems/zeitwerk-2.5.4/lib/zeitwerk/loader/helpers.rb:18:in `ls'
        from /usr/local/bundle/gems/zeitwerk-2.5.4/lib/zeitwerk/loader.rb:232:in `block in eager_load'
        from /usr/local/bundle/gems/zeitwerk-2.5.4/lib/zeitwerk/loader.rb:217:in `synchronize'
        from /usr/local/bundle/gems/zeitwerk-2.5.4/lib/zeitwerk/loader.rb:217:in `eager_load'
        from /usr/local/bundle/gems/zeitwerk-2.5.4/lib/zeitwerk/loader.rb:317:in `each'
        from /usr/local/bundle/gems/zeitwerk-2.5.4/lib/zeitwerk/loader.rb:317:in `eager_load_all'
        from /usr/local/bundle/gems/railties-6.1.6/lib/rails/application/finisher.rb:133:in `block in <module:Finisher>'
        from /usr/local/bundle/gems/railties-6.1.6/lib/rails/initializable.rb:32:in `instance_exec'
        from /usr/local/bundle/gems/railties-6.1.6/lib/rails/initializable.rb:32:in `run'
        from /usr/local/bundle/gems/railties-6.1.6/lib/rails/initializable.rb:61:in `block in run_initializers'
        from /usr/local/lib/ruby/3.1.0/tsort.rb:228:in `block in tsort_each'
        from /usr/local/lib/ruby/3.1.0/tsort.rb:350:in `block (2 levels) in each_strongly_connected_component'
        from /usr/local/lib/ruby/3.1.0/tsort.rb:431:in `each_strongly_connected_component_from'
        from /usr/local/lib/ruby/3.1.0/tsort.rb:349:in `block in each_strongly_connected_component'
        from /usr/local/lib/ruby/3.1.0/tsort.rb:347:in `each'
        from /usr/local/lib/ruby/3.1.0/tsort.rb:347:in `call'
        from /usr/local/lib/ruby/3.1.0/tsort.rb:347:in `each_strongly_connected_component'
        from /usr/local/lib/ruby/3.1.0/tsort.rb:226:in `tsort_each'
        from /usr/local/lib/ruby/3.1.0/tsort.rb:205:in `tsort_each'
        from /usr/local/bundle/gems/railties-6.1.6/lib/rails/initializable.rb:60:in `run_initializers'
        from /usr/local/bundle/gems/railties-6.1.6/lib/rails/application.rb:391:in `initialize!'
        from /usr/src/redmine/config/environment.rb:16:in `<top (required)>'
        from /usr/local/bundle/gems/zeitwerk-2.5.4/lib/zeitwerk/kernel.rb:35:in `require'
        from /usr/local/bundle/gems/zeitwerk-2.5.4/lib/zeitwerk/kernel.rb:35:in `require'
        from /usr/local/bundle/gems/activesupport-6.1.6/lib/active_support/dependencies.rb:332:in `block in require'
        from /usr/local/bundle/gems/activesupport-6.1.6/lib/active_support/dependencies.rb:299:in `load_dependency'
        from /usr/local/bundle/gems/activesupport-6.1.6/lib/active_support/dependencies.rb:332:in `require'
        from config.ru:3:in `block in <main>'
        from /usr/local/bundle/gems/rack-2.2.3/lib/rack/builder.rb:116:in `eval'
        from /usr/local/bundle/gems/rack-2.2.3/lib/rack/builder.rb:116:in `new_from_string'
        from /usr/local/bundle/gems/rack-2.2.3/lib/rack/builder.rb:105:in `load_file'
        from /usr/local/bundle/gems/rack-2.2.3/lib/rack/builder.rb:66:in `parse_file'
        from /usr/local/bundle/gems/rack-2.2.3/lib/rack/server.rb:349:in `build_app_and_options_from_config'
        from /usr/local/bundle/gems/rack-2.2.3/lib/rack/server.rb:249:in `app'
        from /usr/local/bundle/gems/rack-2.2.3/lib/rack/server.rb:422:in `wrapped_app'
        from /usr/local/bundle/gems/rack-2.2.3/lib/rack/server.rb:312:in `block in start'
        from /usr/local/bundle/gems/rack-2.2.3/lib/rack/server.rb:379:in `handle_profiling'
        from /usr/local/bundle/gems/rack-2.2.3/lib/rack/server.rb:311:in `start'
        from /usr/local/bundle/gems/railties-6.1.6/lib/rails/commands/server/server_command.rb:39:in `start'
        from /usr/local/bundle/gems/railties-6.1.6/lib/rails/commands/server/server_command.rb:144:in `block in perform'
        from <internal:kernel>:90:in `tap'
        from /usr/local/bundle/gems/railties-6.1.6/lib/rails/commands/server/server_command.rb:135:in `perform'
        from /usr/local/bundle/gems/thor-1.2.1/lib/thor/command.rb:27:in `run'
        from /usr/local/bundle/gems/thor-1.2.1/lib/thor/invocation.rb:127:in `invoke_command'
        from /usr/local/bundle/gems/thor-1.2.1/lib/thor.rb:392:in `dispatch'
        from /usr/local/bundle/gems/railties-6.1.6/lib/rails/command/base.rb:69:in `perform'
        from /usr/local/bundle/gems/railties-6.1.6/lib/rails/command.rb:48:in `invoke'
        from /usr/local/bundle/gems/railties-6.1.6/lib/rails/commands.rb:18:in `<top (required)>'
        from bin/rails:4:in `require'
        from bin/rails:4:in `<main>'

Any chance to create/point to an updated version of the plugin ?

Thanks in advance.

Hi , thanks for the info.

If i understand you correctly , the patch is "fixing" redmine to work with old redmine version of the plugin ?

While this might be usable for others , for me at least , I cant use patches on redmine itself and need to wait for an updated plugin version.

hagay go wrote:

If i understand you correctly , the patch is "fixing" redmine to work with old redmine version of the plugin ?

The patch inserts the functionality of the older plugin right into Redmine, no plugin needed at all afterwards.

While this might be usable for others , for me at least , I cant use patches on redmine itself and need to wait for an updated plugin version.

I’m afraid I can’t help on this one. But maybe someone else can chime in and help.

+1

I need it sooo much.

+1 ! Redmine has some glaringly missing functionalities, and this is one of them.

See for example https://github.com/jamerst/o-data-grid

Could you please clarify if this feature is now integrated in redmine-core ? If yes which version ?
In the contrary, could you please indicate what is the procedure to follow ?

Cécile Ichard wrote in #note-96:

Could you please clarify if this feature is now integrated in redmine-core ? If yes which version ?
In the contrary, could you please indicate what is the procedure to follow ?

This feature is not integrated with the core installation.

I was able to get it working on version 5.1.2 by doing the following:

1. Downloading and untar _query.0.0.4.redmine4x.tar.gz attachment into redmine/plugins
2. Download the patch file or-query-patch-for-Redmine-5.1.0.patch
3. Patch the plugin using the following command while remaining in the redmine directory

patch -p1 < or-query-patch-for-Redmine-5.1.0.patch 

Also you may have to migrate your db for the menu to show correctly as in the image from the original post. I used the following 2 commands for the development instance (not production), not sure entirely why/what it does do it at your own risk I am not a Rails or Redmine professional.

RAILS_ENV=development rake db:migrate
bundle exec rake redmine:plugins:migrate

More info here:
https://www.redmine.org/projects/redmine/wiki/Plugins

Allowing users to use the OR logical operator will let them filter issues under more varied conditions.
I respect the code proposals and discussions in this issue.
To support this goal, I’ve proposed a patch in a new issue, #41214,
that directly addresses the OR condition written in this issue's description ( filter1=value1 OR filter2=value2 OR filter3=value3 ).
Please take a look if you're interested.

Filters without the `OR` operator are inherently limited. Every logical formula can be expressed in Disjunctive Normal Form (DNF), which means combining multiple conditions using `OR`.

For instance, a logical expression like (A ^ B ^ C) V (D ^ E ^ F ^ G) V (H ...)\) showcases how `OR` is used to combine various statements.

Without `OR`, you can’t represent such combinations. Imagine you need a filter that passes items if Condition A, Condition B, or Condition C is true. This is expressed as (A V B V C). Without the `OR` operator, it’s impossible to create this filter, severely limiting the complexity and effectiveness of the filtering mechanisms.

I think this should be implemented in Base Redmine just because of that.