AND/OR condition on multiple control filters

[SunithaE]

Describe the feature: AND/OR condition on multiple control filters.
For now, there is a parental control but when there are two control filters i dont want one to be locked until the other control filter is unlocked.
For example, in the attached image,
If filter is applied on 'Account Number', then the filter should be applied on the other control 'Account Name' too. Is there a chance to bring in this capability ?

[elasticmachine]

Pinging @elastic/kibana-app (Team:KibanaApp)

[elkargig]

I'm looking for something similar.

I have 2 document fields and I'd like to have a control that searches for a specific value (MYVALUE) in either fieldA OR fieldB. I can't create 2 separate controls/filters as they are AND-ed together.

The control filter currently creates this:

{
  "query": {
    "match": {
      "fieldA.keyword": {
        "query": "MYVALUE",
        "type": "phrase"
      }
    }
  }
}

what I'd like to create is the following:

{
  "query": {
    "bool": {
      "should": [
        {
          "match_phrase": {
            "fieldA.keyword": "MYVALUE"
          }
        },
        {
          "match_phrase": {
            "fieldB.keyword": "MYVALUE"
          }
        }
      ],
      "minimum_should_match": 1
    }
  }
}

are there any plans to support something like this ?

[ThomThomson]

The first portion of this issue is already solved with the New Controls, which are GA in 8.3. In the new controls, the left to right hierarchy is set without the child controls being disabled until a parent is set. If you had two controls set up, one for Account Number, and one for Account Name, you could select either first.

For the second request, made by @elkargig, we are approaching that as part of the unified search project. @stratoula is there another issue in place for AND/OR relating to Unified Search? If so, we should close this issue in favour of that one.

[stratoula]

@ThomThomson yes we have this one #127247 It doesn't mention the integration with controls, it is mostly focused on the unified search changes (the filter bar UI and the backend)
Maybe we need a separate issue for tracking the integration with controls, wdyt?

[ThomThomson]

I think that we could potentially use only that issue. If we implement ORs after or during the unification of Controls and unified search, we could architect #127247 as a control type, rather than having two separate user experiences.

[stratoula]

Sounds fair, we can close this!