Colors are indeed stored separately between vis and dashboard, or more clearly: The colors when being in vis editor will be stored with the visualization. If you place it now on a dashboard the chart should have the same colors. If you change the colors on the dashboard and save the dashboard, those colors are now stored with the dashboard, and overwrite the colors of the vis. So making further changes to the vis colors won't update the colors used on THIS dashboard. I am still not 100% convinced by that behavior and we have an ongoing discussion about what we actually want that behavior to be, to be the least confusing (and still fulfill the wishes users were asking for).
Colors should never be automagically reseted actually, but we are aware that there is a bug in the color selection, that seems to be specific to pie charts: https://github.com/elastic/kibana/issues/13653
Yeah the text that will be shown in the legend, so changing that text will always change the colors.
I hope that answers could clarify a bit on the behavior of colors.
Thanks for the clarification. That explains some of what I am seeing though I do suspect a bug somewhere due to "magical" changes.
For my part I would prefer to globally map certain texts to colors. I always want category: ERROR to be red, category: WARNING to be orange etc. I always want type: customer to be blue and type: user to be light blue.
So maybe that's an idea for some sort of global dictionary of palette colors.
Please feel free to file a feature request in our repositories for a global color dictionary. I have looked shortly and it seems we don't have a feature request for that yet.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.