Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't set colours on date range visulation when using now in a date range aggregation #13682

Closed
walrusVision opened this issue Aug 24, 2017 · 2 comments
Labels
bug Fixes for quality problems that affect the customer experience Feature:Visualizations Generic visualization features (in case no more specific feature label is available) impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. Team:Visualizations Visualization editors, elastic-charts and infrastructure

Comments

@walrusVision
Copy link

Kibana version: 5.5.2

Elasticsearch version: 5.5.2

Server OS version: Ubuntu 16

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

Description of the problem including expected versus actual behavior:
If you set custom colours on a graph which are using an aggregation from a date range with now in the date format, then the colours will not stay after refreshing. I would except to be able to keep the colours for the defined series. As far as I can tell this effects any graph type using now in a date range aggregation.

After reading #9219 and #12914 what I believe to be happening is this:

  • The label for a data range such as now-1w to now will be rendered dynamically and will become a label like August 24, 12:00:00.00 to August 17 12:00:00.00
  • The colour will be saved statically against that label e.g "uiStateJSON": "{\"vis\":{\"colors\"{\"August 24, 12:00:00.00 to August 17 12:00:00.00\":\"#BF1CB00\"}}}"
  • When you refresh now now refers to a time in the future and the previously saved label will no longer match.

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. Pick a colour for the range
  4. Save
  5. Refresh
@thomasneirynck thomasneirynck added Feature:Visualizations Generic visualization features (in case no more specific feature label is available) bug Fixes for quality problems that affect the customer experience labels Aug 25, 2017
@timroes timroes added the Team:Visualizations Visualization editors, elastic-charts and infrastructure label Sep 16, 2018
@anthonyscarfe
Copy link

This still exists in 7.10.

I also created two variants of the same visualization with rounding applied to the date range (using now/1d and now/1h).

With rounding applied, the selected colours will persist for the period specified in the rounding. This seems to confirm the theory above, that the issue is caused by static times being used in uiStateJSON.

@stratoula stratoula added the impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. label Jul 26, 2021
@stratoula stratoula added impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. and removed impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. labels Jul 29, 2021
@flash1293
Copy link
Contributor

Closing this issue because this will be supported in Lens visualizations soon (tracked by #101942 )

Since this would require a large development effort to implement in Visualize/TSVB and our efforts are focused on extending the functionality of Lens in easy-to-use and consistent way. We aim to provide the best possible visualization editing experience in Lens and are working to improve that tool and help users migrate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Feature:Visualizations Generic visualization features (in case no more specific feature label is available) impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. Team:Visualizations Visualization editors, elastic-charts and infrastructure
Projects
None yet
Development

No branches or pull requests

6 participants