Regress in queries in Graylog 3.0

I think there might be regress in queries in Graylog 3.0.
I updated my Graylog setup from Graylog 2.5.1/Elasticsearch 5.6 to Graylog 3.0/Elasticsearch 6.6 and discovered a problem with queries.

## Expected Behavior

According to help, I can use parentheses in queries to find any of word
http://docs.graylog.org/en/3.0/pages/queries.html#syntax

For example `NOT user:(gitlab-runner jenkins git)`. This worked as expected on Graylog 2.5.1 and doesn't on 3.0.
For now I had to change query to `NOT (user:gitlab-runner OR user:git OR user:jenkins)`

## Current Behavior

Query `NOT user:(gitlab-runner jenkins git)` return all items.

## Possible Solution

Change query to `NOT (user:gitlab-runner OR user:git OR user:jenkins)`

## Steps to Reproduce (for bugs)

1. Run query with `any_field: (value1 value2)`
2. It doesn't work in ver 3.0
3. Change query to `any_field:value1 OR any_field:value2`
4.It works

## Context

I used these queries to filter some events from alerts. I had to change them to more complicated like ``NOT (user:gitlab-runner OR user:git OR user:jenkins)``

## Your Environment

* Graylog Version: 3.0.0-12
* Elasticsearch Version: 6.6.0
* MongoDB Version: 4.0.2
* Operating System: Ubuntu 18.04.1 LTS
* Browser version: Google Chrome 72.0.3626.109

P.S. I haven't found related issues