Date range aggregation with Group other values produces different labels and colours for other values

[walrusVision]

Kibana version: 6.7.1

Elasticsearch version: 6.7.1

Server OS version: Ubuntu 16.04

Browser version: Chrome 72.0.3626.81

Browser OS version: Ubuntu 18.04

Original install method (e.g. download page, yum, from source, etc.): debian

Describe the bug: If you ask for Group other values on a graph which is using an aggregation from a date range with now in the date format, then it will generate a separate set of labels for Other and Non-Other results, which also results in different colours for the Other data. As far as I can tell this effects any graph type using now in a date range aggregation.

Steps to reproduce:

1. Make a bar chart graph against data with a time range
2. For the bucket make a date range aggregation (or sub aggregation) with something like From = now-1w and To = now
3. Select Group other values to enabled
4. Save
5. Refresh

Expected behavior: I would except column for the 'Other' data have the same labels and colours as the non-other data.

Screenshots (if relevant):

Errors in browser console (if relevant):

Provide logs and/or server output (if relevant):

Any additional context: This is similar to the bug I reported in #13682, in which using date range aggregation causes unexpected behaviors due to relative time queries.

[walrusVision]

Here is a screenshot of the behavior I am seeing. The Other column is on the right.

[timroes]

Hi,

could you please look over the steps to reproduce again and give the complete aggregation configuration there. It seems you jumped to enabled "Group other values", which is a setting only available on the terms aggregation, which is according to the rest of the steps not in your chart at all.

Could you please also share a full screenshot of the chart including the axes on both sides, since that would make it easier to understand what the buckets actually are.

Thanks,
Tim

[elasticmachine]

Pinging @elastic/kibana-app

[timroes]

Closing this issue due to inactivity.

We are trying to keep our issues to a manageable amount, which means we are trying to close issues we cannot reproduce or gather required information for some time. Please feel free to still provide the requested information in case the issue still persists on an up-to-date Kibana version. We will gladly reopen this issue again.